> Richard B. Johnson wrote:
> > >
> > > ls -F will access the files. check that you don't alias ls to 'ls -F'
> > >
> > Yes! `ls` is aliased to `ls -AF`. Don't know why. I just removed it from
> > ..bashrc.
> Are all files getting "accessed" or just the directories?
> Just the Directories is a feature, all the files is a problem. I still
> can't reproduce what you're saying but I don't have 2.1.56 running
> right now.
All of the files were being accessed. This seems to be a feature of
my version of 'color ls', although I can't be sure.
As shown in my test, I performed `la -R /`, and __ALL__ every file on
the system was accessed. I did this several times and again every file
Then I removed my alias, ls=/bin/ls -AF, and the problem seemed to go
away.... but. I deleted my old /bin/ls and built a new `color ls` from
After this, I can't replicate the problem. It doesn't seem to be a kernel
problem now, but the old `ls` had been previously built with the exact
same sources and 'C' runtime library.
bash's built-in should have been in-use when I performed init=/bin/bash
because my .bashrc was not read and the 'system' profile does not
reference /bin/ls. Therefore, I don't really know what was happening
except that it have 1.2 gb of files that were 'accessed' during my
Richard B. Johnson
Penguin : Linux version 2.1.55 on an i586 machine (66.15 BogoMips).
Warning : It's hard to stay on the trailing edge of technology.
Linux : Engineering tool
Spam : sync@localhost, daemon@loghost