From owner-freebsd-current@FreeBSD.ORG Tue Mar 30 03:38:22 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 DF60116A4CE for ; Tue, 30 Mar 2004 03:38:22 -0800 (PST) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FACF43D2F for ; Tue, 30 Mar 2004 03:38:22 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i2UBcL4u031322; Tue, 30 Mar 2004 21:38:21 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i2UBcJsg007754; Tue, 30 Mar 2004 21:38:20 +1000 Date: Tue, 30 Mar 2004 21:38:18 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Marcel Moolenaar In-Reply-To: <20040330080250.GA69610@dhcp01.pn.xcllnt.net> Message-ID: <20040330212234.B10192@gamplex.bde.org> References: <20040329163926.A38109@xorpc.icir.org> <20040330005013.GA53546@ns1.xcllnt.net> <20040329234212.A72990@xorpc.icir.org> <20040330080250.GA69610@dhcp01.pn.xcllnt.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Luigi Rizzo cc: current@FreeBSD.org Subject: Re: proposed bsdlabel patch 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: Tue, 30 Mar 2004 11:38:23 -0000 On Tue, 30 Mar 2004, Marcel Moolenaar wrote: > On Mon, Mar 29, 2004 at 11:42:12PM -0800, Luigi Rizzo wrote: > > actually, following up to myself: > > > > you do need some way to disambiguate between the case of a device > > ("bsdlabel ad0") and a file in the current directory ("bdslabel > > ad0"). The absolute path hack is a bad way to do this. It depends on the historical brokenness of adding a /dev prefix to the pathname unless the pathname begins with a leading slash. > The file takes precedence, because any filename that does not contain > any directory elements is assumed to live in the current directory. The So should any pathname that doesn't contain a leading slash (e.g., ./foo, or foo/bar). > shorthand for device special files is secundairy to that, because it's > a convenience only. If the device special file is meant, it has to be > specified as /dev/ad0 in the example given. Unfortunately, disklabel never worked like that, and bsdlabel inherited most of disklabel's bugs and added more. %%% Script started on Tue Mar 30 21:37:05 2004 ttyp0:bde@besplex:/tmp> touch foo ttyp0:bde@besplex:/tmp> bsdlabel foo bsdlabel: /dev/foo: No such file or directory ttyp0:bde@besplex:/tmp> bsdlabel ./foo bsdlabel: /dev/./foo: No such file or directory ttyp0:bde@besplex:/tmp> exit Script done on Tue Mar 30 21:37:17 2004 %%% Bruce