Date: Thu, 10 Nov 2011 10:12:26 -0800 From: Garrett Cooper <yanegomi@gmail.com> To: Ed Schouten <ed@80386.nl> Cc: arch@freebsd.org Subject: Re: The strangeness called `sbin' Message-ID: <CAGH67wSw-aSbXdskApWdAD59TwDHW7QeYGmY4vTZaPWMubDb5w@mail.gmail.com> In-Reply-To: <20111110174722.GJ2164@hoeg.nl> References: <20111110123919.GF2164@hoeg.nl> <CAGE5yCr3BzWzwOAqo7wifgUTRC%2BG=2o4bDmk9H-%2BCxr=zJqYmw@mail.gmail.com> <20111110171605.GI2164@hoeg.nl> <CAGE5yCqMcHwAhXKbyEH6vUR=N14tCjkgX=RMJTdq-po92GcOMQ@mail.gmail.com> <20111110174722.GJ2164@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 10, 2011 at 9:47 AM, Ed Schouten <ed@80386.nl> wrote:
> * Peter Wemm <peter@wemm.org>, 20111110 18:33:
>> Having /sbin in $PATH where /sbin is a symlink to /bin would be worse
>> than having no /sbin at all, from a perspective of rootvnode lock
>> lifetime. If you can figure out how to get people to remove /sbin and
>> /usr/sbin from their paths after the symlink changes then it becomes a
>> moot point. But heck, I still have /usr/X11R6 in mine... :(
>
> On the other hand, if people used to have /sbin in their path and *do*
> remove it properly after the upgrade, they should in theory see a
> performance improvement, right?
Doesn't the negative directory cache (namei, etc) mitigate this?
Thanks!
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wSw-aSbXdskApWdAD59TwDHW7QeYGmY4vTZaPWMubDb5w>