Powermaster
Site Supporter
How would one go about making a Symbolic Link?
Thanks
Thanks
So what is it then? What I see on my box, when I create a symbolic link is an autonomous file (with its own inode) with the length of exactly the source path plus a certain flag.Originally posted by lurk
You are assuming an implementation which does not correspond to what is done in HFS+.
Wow, I didn't know that. Which are these?For instance some file systems directly record the symbolic link in the directory structure itself.
See, I'm really a rookie on filesystems, that is also new to me. But this is HPFS and not HFS+ is it?therein directories are not explicitly stored, they are built on the fly from the individual entries.
(Another neat thing if you have ever used zsh doing wild-inferiors was just as cheap as globbing. That is /foo/*.c was a fast as /**/foo.c which normally under unix requires a call to find to compute.)
Originally posted by Eckhart
So what is it then? What I see on my box, when I create a symbolic link is an autonomous file (with its own inode) with the length of exactly the source path plus a certain flag.
Wow, I didn't know that. Which are these?
See, I'm really a rookie on filesystems, that is also new to me. But this is HPFS and not HFS+ is it?
Nope you misunderstood the ** that will match any number of arbitrarily nested directories. So /foo/**/bar.c would match /foo/baz/quuz/zot/bar.c which is not possible in bash or tsch. In those cases you have to use find to grovel over the directory for you. Another point is that this is very sow by comparison and on something like HPFS a wild inferiors match like above would be super fast.
Same for tcsh and bash.
Is now anyone here, who can answer my actual questions? Thanks again!