From owner-freebsd-current@FreeBSD.ORG Mon Aug 2 07:04:52 2004 Return-Path: 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 BE01816A4CE; Mon, 2 Aug 2004 07:04:52 +0000 (GMT) Received: from dglawrence.com (c-24-21-223-117.client.comcast.net [24.21.223.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8063743D46; Mon, 2 Aug 2004 07:04:52 +0000 (GMT) (envelope-from dg@nexus.dglawrence.com) Received: from nexus.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.12.10/8.12.6) with ESMTP id i7272c5X074786; Mon, 2 Aug 2004 00:02:38 -0700 (PDT) (envelope-from dg@nexus.dglawrence.com) Received: (from dg@localhost) by nexus.dglawrence.com (8.12.10/8.12.3/Submit) id i7272c0x074785; Mon, 2 Aug 2004 00:02:38 -0700 (PDT) Date: Mon, 2 Aug 2004 00:02:38 -0700 From: "David G. Lawrence" To: Tim Kientzle Message-ID: <20040802070238.GA66505@nexus.dglawrence.com> References: <40F963D8.6010201@freebsd.org> <200407291159.i6TBxKj01347@Mail.NOSPAM.DynDNS.dK> <4109BA1B.7090609@freebsd.org> <20040730080026.GA46093@nexus.dglawrence.com> <410A78B1.4030608@kientzle.com> <20040801221508.GF75481@nexus.dglawrence.com> <410D894D.7000209@freebsd.org> <20040802010910.GA63402@nexus.dglawrence.com> <410D9957.5020308@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <410D9957.5020308@freebsd.org> cc: freebsd-current@freebsd.org Subject: Re: tar -l versus gtar -l X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Aug 2004 07:04:52 -0000 > David G. Lawrence wrote: > > > > Well...the SUSv2 specification for tar may not have been the best > > standard > >to adhere to. The change of behavior for the 'l' option on create is going > >to seriously bite a lot of people because it majorly affects what is > >archived. > > I'm reluctant to contradict the one serious > attempt to standardize tar simply because gtar > ignored that effort. > > I would rather just disable the -l option entirely; > that way, people would get an error message instead > of having the tar program behave unexpectedly. > > Would you be happier with this behavior? > > $ tar -cl /foo > Error: -l is ambiguous > If you want GNU tar -l, use --one-file-system instead. > If you want POSIX tar -l, use --link-warn instead. Yes. That way at least people won't accidently destroy a filesystem (like I did) when they're trying to use tar to copy stuff. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities.