From owner-freebsd-current Sat Aug 10 9: 3:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B99F37B400; Sat, 10 Aug 2002 09:03:38 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 246D043E84; Sat, 10 Aug 2002 09:03:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g7AG0XDe096923; Sat, 10 Aug 2002 18:00:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Ian Dowse , Alexander Leidinger , bhlewis@wossname.net, freebsd-current@FreeBSD.ORG, bde@FreeBSD.ORG Subject: Re: Is anyone else having trouble with dump(8) on -current? In-Reply-To: Your message of "Sun, 11 Aug 2002 02:03:40 +1000." <20020811014214.D17412-100000@gamplex.bde.org> Date: Sat, 10 Aug 2002 18:00:33 +0200 Message-ID: <96922.1028995233@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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