Thread: Add HD
View Single Post
Old 26th August 2009
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Banned
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Default

Quote:
Originally Posted by jggimi View Post
Securelevel 2 prevents writing to a raw device if the block device is mounted. I hadn't thought of this, but then, fdisk/atactl use of "wd0" gets converted to "/dev/rwd0c". Since there's an MBR on that drive, /dev/wd0c would almost assuredly not be mounted.
That's the behaviour when securelevel is 1, a securelevel of 2 prevents write-access to unmounted devices as well.

Quote:
Originally Posted by securelevel(7)
2 Highly secure mode
- all effects of securelevel 1
- raw disk devices are always read-only whether mounted or not
- settimeofday(2) and clock_settime(2) may not set the time back-
wards or close to overflow
- pf(4) filter and NAT rules may not be altered
Seems as if this user may have been playing around with his configuration files recently.

Quote:
Originally Posted by jggimi
Re: IDE channels -- yes, one may have one or both empty and unused. But, as I understand pciide.c you only get that particular warning message for controllers which are Intel 82371-compatible. That section of the code is from 1999, so it's been that way a long time.
Yes, likely a little bit of debugging noise that got left in.. could be a especially flaky family of IDE controllers.

EDIT: I'm finding that warning message in at least 10 different chipset handlers in pciide.c.. guess the developers find it useful under some circumstances.

Last edited by BSDfan666; 26th August 2009 at 07:22 PM.
Reply With Quote