Remove DIOCWLABEL operation. Doing it destroyed the purpose of having
authorMatthew Dillon <dillon@dragonflybsd.org>
Mon, 21 May 2007 15:53:29 +0000 (15:53 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Mon, 21 May 2007 15:53:29 +0000 (15:53 +0000)
commit62c9529372544db8c1dafff8f9555f2571d81da9
tree12593ff31df73e0517f1343839694713c5eb1201
parent983105c18df18a193ca1a71952ccb6870bb1b61e
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>
bin/dd/dd.c