Date: Sun, 11 Aug 2002 23:16:34 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: iedowse@maths.tcd.ie, <freebsd-current@FreeBSD.ORG> Subject: Re: Is anyone else having trouble with dump(8) on -current? Message-ID: <20020811230844.E20418-100000@gamplex.bde.org> In-Reply-To: <20020811111150.4fc4e70e.Alexander@Leidinger.net>
index | next in thread | previous in thread | raw e-mail
On Sun, 11 Aug 2002, Alexander Leidinger wrote: > On Sun, 11 Aug 2002 02:03:40 +1000 (EST) Bruce Evans <bde@zeta.org.au> > wrote: > > > 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020811230844.E20418-100000>