cache_lookup() work this week.

Garance A Drosihn drosih at rpi.edu
Wed Sep 3 12:05:08 PDT 2003


At 10:10 PM -0700 9/2/03, Matthew Dillon wrote:
    The fourth step will be a *BIG* Carrot...
    This means that (A) it will be possible to hardlink
    directories,
Isn't this dangerous?  What if you have a hardlink between
/a/b/c/d and /a/b?  Something like 'find' will descend down
into /a/b/c/d and only find itself back at /a/b (but with a
longer pathname...).  There won't be a good way for 'find'
to avoid that kind of loop, if I understand this correctly.
    and (B) it will be possible to implement semi-hard links,
    basically softlinks that *look* like hardlinks
What will this be like?  Ie, what will be the difference
between hard-links and semi-hard links?  Will this be
something like the way OpenAFS handles volume-mounting?
    and (C) to be able to CD forwards and backwards without
    the system getting confused about paths.
This would be nice!

--
Garance Alistair Drosehn            =   gad at xxxxxxxxxxxxxxxxxxxx
Senior Systems Programmer           or  gad at xxxxxxxxxxx
Rensselaer Polytechnic Institute    or  drosih at xxxxxxx




More information about the Kernel mailing list