Date: Sun, 13 Nov 2011 16:21:03 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Tim Kientzle <tim@kientzle.com> Cc: Ed Schouten <ed@80386.nl>, arch@freebsd.org Subject: Re: The strangeness called `sbin' Message-ID: <4EC05EEF.5030908@FreeBSD.org> In-Reply-To: <F5AA9108-8715-43B2-AE64-8A0B5E10657C@kientzle.com> References: <20111110123919.GF2164@hoeg.nl> <4EBC4B6E.4060607@FreeBSD.org> <20111111112821.GP2164@hoeg.nl> <4EBDC06F.6020907@FreeBSD.org> <20111112103918.GV2164@hoeg.nl> <4EBF0003.3060401@FreeBSD.org> <20111113091940.GX2164@hoeg.nl> <4EC04B65.4030801@FreeBSD.org> <F5AA9108-8715-43B2-AE64-8A0B5E10657C@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/13/2011 16:08, Tim Kientzle wrote: > On Nov 13, 2011, at 2:57 PM, Doug Barton wrote: >> >> Actually I think a much more interesting, and likely more useful change >> would be to put everything into /bin. > > I'm really confused, Doug. > > You've been vehemently arguing against merging /bin and > /sbin, but here you seem to be claiming that it would be > better to instead merge /bin, /sbin, /usr/bin, and /usr/sbin. > > Care to clarify? Go back and reread the message that you quoted from, and hopefully it will be clear to you. I'm not sure I can say it any better than I did. > Personally, I really like Ed's proposal. Nothing stops you from implementing it locally. :) > In part, that's > from my personal experience of being highly annoyed > whenever I use a Linux system that doesn't put /sbin into > my path. Ed's proposal won't help you on Linux systems. OTOH, we've had */sbin in the default path for many years, which means that relative to the cause of your pain Ed's proposal provides no benefit on a FreeBSD system. > If I always expect both /bin and /sbin to be in my > path, then just combining them into one directory makes > a whale of a lot of sense. > > I agree the transition issues are delicate, but we've > dealt with equally difficult transition issues before. First, I think you are also dramatically underestimating the level of drama that this is going to cause. Second, (and here's a hint to the answer to your first question) given that there is so little (if any) benefit, why create all the pain in the first place? Doug -- "We could put the whole Internet into a book." "Too practical." Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EC05EEF.5030908>