In message <alpine.bsf.2.00.1110071236270.2...@wonkity.com>, Warren Block write
s:
>>>> Which is the exactly right question to ask.
>>>>
>>>> The procedure documented is clearly flawed.
>>>
>
>Well, yes. The goal is to unprotect the device, regardless of what may
>already be on it. Then the user can overwrite it with the memory stick
>image.
Unprotect from what ? from being already mounted ?
If you cannot open a geom provider for writing, then it is because
some piece of code in the kernel thinks it already owns the device
and don't want you to muck about with it.
Overriding this check is just asking for panics...
What I usually do in cases like this is:
(umount /dev/${whatever} || true) > /dev/null 2>&1
And if that isn't enough, or not possible, then the user needs
to undo whatever he did to the device...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
