From owner-freebsd-current Mon Dec 14 18:50:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27725 for freebsd-current-outgoing; Mon, 14 Dec 1998 18:50:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27718 for ; Mon, 14 Dec 1998 18:50:06 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id SAA04762; Mon, 14 Dec 1998 18:49:45 -0800 Date: Mon, 14 Dec 1998 18:49:45 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Greg Lehey cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <19981215131522.G15633@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Down the road a little bit would be: > >> > >>>> untangling the minor device as behaviour selector so that > >> ioctl's would not have to be used to select compression. > > > > This should be controversial :-). Compression is another type of > > behaviour. > > Is this an argument for or against the change? > > I'm for the change, anyway. Currently it's not possible to tell a > backup utility to write in compressed or uncompressed mode. If I have > different devices, I can do this. It's been this way in ever other > UNIX I've used. You *can* enable/disable compression, and we could even make the change persistent across tape mounts, but the issue here is whether or not you also want to go and change the N different backup utilities to use the appropriate ioctl to select compression or not. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message