Date: Sun, 11 Aug 2002 11:11:50 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Bruce Evans <bde@zeta.org.au> Cc: iedowse@maths.tcd.ie, freebsd-current@FreeBSD.ORG Subject: Re: Is anyone else having trouble with dump(8) on -current? Message-ID: <20020811111150.4fc4e70e.Alexander@Leidinger.net> In-Reply-To: <20020811014214.D17412-100000@gamplex.bde.org> References: <200208101504.aa40149@salmon.maths.tcd.ie> <20020811014214.D17412-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Bye,
Alexander.
--
Secret hacker rule #11: hackers read manuals.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020811111150.4fc4e70e.Alexander>