Date: Wed, 10 Dec 1997 20:27:55 -0700 (MST) From: gibbs@narnia.plutotech.com (Justin T. Gibbs) To: scsi@FreeBSD.org Subject: Re: Questions about mt and SCSI subsystem Message-ID: <199712110327.UAA17646@narnia.plutotech.com> In-Reply-To: <19971211005904.40551@uriah.heep.sax.de> References: <199712100037.SAA25972@nospam.hiwaay.net> <199712100243.TAA18226@narnia.plutotech.com> <19971210093732.48185@uriah.heep.sax.de> <348F08D6.63DABEB6@whistle.com> <19971211005904.40551@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <19971211005904.40551@uriah.heep.sax.de>, J Wunsch <j@uriah.heep.sax.de> writes: > > The correct behaviour is that any read or write attempt, upon > encountering EOF (read) or EOM (write) should return a `short' > read/write (i.e., set b_resid accordingly), but shall not flag an > error condition. Are you sure about the behavior for write? > Offhand i'm not sure what should happen if you are exactly at EOF, > and try to read on, but still i think read(2) should just return 0 but > no error. On a tape, you will start reading the next file unless the EOF handling back spaces over the filemark after noticing it. -- Justin T. Gibbs =========================================== FreeBSD - Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712110327.UAA17646>