Date: Sat, 10 Aug 2002 18:00:33 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Bruce Evans <bde@zeta.org.au> Cc: Ian Dowse <iedowse@maths.tcd.ie>, Alexander Leidinger <Alexander@Leidinger.net>, bhlewis@wossname.net, freebsd-current@FreeBSD.ORG, bde@FreeBSD.ORG Subject: Re: Is anyone else having trouble with dump(8) on -current? Message-ID: <96922.1028995233@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 11 Aug 2002 02:03:40 %2B1000." <20020811014214.D17412-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020811014214.D17412-100000@gamplex.bde.org>, Bruce Evans writes: >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. Considering that opening a disk-device cannot be guaranteed to succeed in finite time (think SAN, SCSI over IP and generally broken hardware), it should be interruptible. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@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. 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?96922.1028995233>