From owner-freebsd-current  Sun Aug 11  6:11:51 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 14D8537B400
	for <freebsd-current@FreeBSD.ORG>; Sun, 11 Aug 2002 06:11:49 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1CBC343E5E
	for <freebsd-current@FreeBSD.ORG>; Sun, 11 Aug 2002 06:11:48 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA14732;
	Sun, 11 Aug 2002 23:11:36 +1000
Date: Sun, 11 Aug 2002 23:16:34 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
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?
In-Reply-To: <20020811111150.4fc4e70e.Alexander@Leidinger.net>
Message-ID: <20020811230844.E20418-100000@gamplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

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 message