Date: Tue, 30 Mar 2004 11:06:41 +0200 From: Hartmut Brandt <harti@freebsd.org> To: Luigi Rizzo <rizzo@icir.org> Cc: Marcel Moolenaar <marcel@xcllnt.net> Subject: Re: proposed bsdlabel patch Message-ID: <406938A1.9030507@freebsd.org> In-Reply-To: <20040330003408.A75276@xorpc.icir.org> References: <20040329163926.A38109@xorpc.icir.org> <20040330005013.GA53546@ns1.xcllnt.net> <20040329230643.B70930@xorpc.icir.org> <20040329234212.A72990@xorpc.icir.org> <20040330080250.GA69610@dhcp01.pn.xcllnt.net> <40692D02.5090700@freebsd.org> <20040330003408.A75276@xorpc.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Luigi Rizzo wrote: > On Tue, Mar 30, 2004 at 10:17:06AM +0200, Hartmut Brandt wrote: > >>Marcel Moolenaar wrote: > > ... > >>>The file takes precedence, because any filename that does not contain >>>any directory elements is assumed to live in the current directory. The >>>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. > > > it may be secondary, but it has been the historical behaviour for > ages and I don't want to hear people rightly screaming for a change > that broke a huge number of existing scripts. > > >>That makes it very easy to trash a file in the current directory. > > > that is a minor concern. "rm" has the same problem :) Not really. rm has no magic that interpretes da0 as /dev/da0. If you happen to have a file da0 in your current directory (let's say the saved disklabel or so) and specify just da0 to disklabel expecting that it will work on /dev/da0 it will unexpecedly clobber your file. Such automatisms make things not easier, but more complex - you have to remember them. You need to get the habit to do ls -l before you do disklabel da0. I'd say keep the '-f' option, that'll make things clearer. harti
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?406938A1.9030507>