Phil Pennock wrote:
> On 2008-01-04 at 16:07 -0800, Michael G Schwern wrote:
>> Of course, as Peter insinuated, I'm sure by now it's been rationalized as a
>> "feature".
>
> In large environments, having everything always locally available on
> local disk is fairly recent, with cluster management
On 2008-01-04 at 16:07 -0800, Michael G Schwern wrote:
> Of course, as Peter insinuated, I'm sure by now it's been rationalized as a
> "feature".
In large environments, having everything always locally available on
local disk is fairly recent, with cluster management systems etc. NFS
is still com
Smylers wrote:
> I just spotted this in the README.Debian that Debian supply with Bash:
>
> bash does not check $PATH if hash fails
>
> bash hashes the location of recently executed commands. When a command
> is moved to a new location in the PATH, the command is still in the
> PATH but t
On Fri, Jan 04, 2008 at 07:09:04PM +0100, demerphq wrote:
> Heh. I got bit by this hatefulness for the first time just yesterday.
> Very confusing. Its nice to hear I'm not the only one who finds this
> stupidity to be, er, stupid.
It's particularly hateful because when you run "rehash" to fix it,
On 4 Jan 2008, at 18:39, Walt Mankowski wrote:
It's particularly hateful because when you run "rehash" to fix it, it
returns instantaneously. I wonder if this is a case of premature
optimization, or if it's a relic of bygone days when CPUs and hard
drives were a lot slower.
I assume hash -r j
Yes, this is one of those things that pisses me off about csh too.
It's something that was done back when it was running on a PDP-11 and
the four or five extra calls to namei() that you'd get when you
typoed a command were significant on a machine with 70 users, 2MB of
RAM, and big slow 14"
On 04/01/2008, Smylers wrote:
> I just spotted this in the README.Debian that Debian supply with Bash:
>
> bash does not check $PATH if hash fails
>
> bash hashes the location of recently executed commands. When a command
> is moved to a new location in the PATH, the command is still in the
I just spotted this in the README.Debian that Debian supply with Bash:
bash does not check $PATH if hash fails
bash hashes the location of recently executed commands. When a command
is moved to a new location in the PATH, the command is still in the
PATH but the hash table still records t
