| commit | 3011de10c5c6f8db61a9a7b7e481c0a2e1eb4e27 | |
| author | Matthew Dillon <dillon@dragonflybsd.org> | |
| Mon, 21 May 2007 15:53:29 +0000 (21 15:53 +0000) | ||
| committer | Matthew Dillon <dillon@dragonflybsd.org> | |
| Mon, 21 May 2007 15:53:29 +0000 (21 15:53 +0000) | ||
| tree | 4d6f780672689b2bac653d3abc903706e11003d4 | treesnapshot (tar.gz zip) |
| parent | 383cef4a69636d9516afea13ea518f718e76bc07 | commitdiff |
Remove DIOCWLABEL operation. Doing it destroyed the purpose of having
write protected areas in the first place. This also solves an issue
bootstrapping from older versions of DragonFly since the ioctl has moved
to a different header file.
Users can write-enable the label area with disklabel -W/-N if the issue
comes up.
Note: In DragonFly 1.9 and later, the MBR and disklabel areas are only
write protected when accessed via a slice or partition. Access to these
areas via the raw disk (e.g. ad0) is no long write-protected.
Reported-by: Hasso Tepper <hasso@estpak.ee>,
YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
write protected areas in the first place. This also solves an issue
bootstrapping from older versions of DragonFly since the ioctl has moved
to a different header file.
Users can write-enable the label area with disklabel -W/-N if the issue
comes up.
Note: In DragonFly 1.9 and later, the MBR and disklabel areas are only
write protected when accessed via a slice or partition. Access to these
areas via the raw disk (e.g. ad0) is no long write-protected.
Reported-by: Hasso Tepper <hasso@estpak.ee>,
YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
| bin/dd/dd.c | diffblobblamehistory |