From owner-freebsd-hackers Wed Nov 1 14:46:44 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA01267 for hackers-outgoing; Wed, 1 Nov 1995 14:46:44 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA01262 for ; Wed, 1 Nov 1995 14:46:41 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id OAA23526; Wed, 1 Nov 1995 14:46:19 -0800 From: Julian Elischer Message-Id: <199511012246.OAA23526@ref.tfs.com> Subject: Re: More nits To: se@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Wed, 1 Nov 1995 14:46:18 -0800 (PST) Cc: hackers@freebsd.org In-Reply-To: <199511012030.AA08173@Sysiphos> from "Stefan Esser" at Nov 1, 95 09:30:39 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1149 Sender: owner-hackers@freebsd.org Precedence: bulk > > Hmm, but if I remember right, an "mt status" > of a rewind tape device WILL rewind after the > status has been printed. as I would expect it to.. > > This was a little surprising, since I was not > used to this kind of behaviour on other BSD > derived systems. you WEREN'T? the rewind device always rewinds on close.. if you don't want it to rewind you should use the non-rewind device.. I have often used a close of a rewind device to rewind it.. > > IMHO, a "mt status" should print information > about the tape, but should NOT CHANGE the > state of the tape at all ... > (Same for /dev/erst0: A "mt status" should not > eject the tape. But I've got to admit that I > did not check whether it does ...) of course it does... I don't make the action on close dependent on whether there has been any IO or not... > > Regards, STefan > > -- > Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 > Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 > ============================================================================== > http://www.zpr.uni-koeln.de/~se >