From owner-freebsd-current Mon Dec 14 16:49:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11509 for freebsd-current-outgoing; Mon, 14 Dec 1998 16:49:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11488 for ; Mon, 14 Dec 1998 16:49:22 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA26526; Tue, 15 Dec 1998 11:18:50 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <98Dec15.081550est.40374@border.alcanet.com.au> Date: Tue, 15 Dec 1998 11:18:40 +1030 (CST) From: "Daniel O'Connor" To: Peter Jeremy Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour Cc: mjacob@feral.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Dec-98 Peter Jeremy wrote: > I also consider this behaviour to be a bug. Unfortunately, the Unix > system call semantics don't provide any mechanism to report why a read > or write terminated early. Actually, general bitch time, they don't provide ANY sort of extended error information which sucks.. errno is fine until you get a function which overloads a single errno value with lots of meanings :( Hmm.. maybe 'errno_callspec' ;) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message