retasting devices on demand

[Poul-Henning Kamp]

In message <44EBAE59.7040003 at centtech.com>, Eric Anderson writes:
>On 08/22/06 18:48, Roman Kurakin wrote:

>> "Busy" more appropriate.
>
># true > /dev/ad0
>-su: /dev/ad0: Operation not permitted
>
>I agree though, that EBUSY is better.

Semantically it is not a EBUSY situation because it is within the
control of whatever code opened the disk first to decide if you
will be allowed to write to it or not.

Shared writes _are_ possible, I just don't think we have any code
which allows it yet.

That's why it is EPERM and not EBUSY

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at 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.