On Sun, 11 Aug 2002, Alexander Leidinger wrote:
> On Sun, 11 Aug 2002 02:03:40 +1000 (EST) Bruce Evans <[EMAIL PROTECTED]>
> > I don't know how open() of a disk device can be interrupted by a
> > signal in practice. Most disk operations don't check for signals.
> How close is our open() to the standards? Does any of them specify EINTR
> as a possible errno and if yes, shouldn't we write programs which
> respect the standards (where applicable) instead of just adapting them
> to our kernel?
open() returning EINTR is normal for some types of devices, so it is
standard. General standards like POSIX.1 shouldn't go into details
enough to specify different EINTR behaviour for disks (or even specify
disks) since this would limit them too much.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message