Re: [cobalt-users] Re: Default FTP login on RaQ2/3

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

root@xxxxxxxxxxxxxxxxxxxxxxxx wrote:

>   Symbolic links are resolved as simple text substitutions on the
> filename, as such the system doesn't care what the symlink points to, it
> just does the substitution before it tries to resolve the filename,

> ...<stuff snipped out of middle>...

> Hard links on the other hand, cause two or more filenames to point to
> the same actual block of data (the 'inode') on the disk,
>  since filenames can only
> reference data on the same disk they are located on,
>  hard links can not point to
> another disk, and the file obviously has to exist. File ownership and
> permissions on unix are associated with data, not the filename btw..
> so changing the permission on one filename
> will change it on the other.(hard linked filename)

Now that you've done such a good job of explaining this, I'm of the
thought that it really needs a knowledge base entry to do it justice.  I
had learned this all a long time ago, but had forgotten the details. 
And the other day I looked into four books and couldn't find those
details again, but I did find the snippet about only using symbolic
links in directories (hence my reference to "mom" you referred to).  So
it's time for a knowledge-base entry.

The question is do you want to do it (talk to Cobalt as to how to make
knowledge-base entries), or do you want me to do it?  If you give me
permission, I can have this in the knowledge base in another day or so,
or you do it.  Either way, it SHOULD be done.

Good writing!

> > I remember, when I was a little boy, mom used to tell me not to use hard
> > links for directories.
> 
> Always listen to mom....-/

Yeah, but she also told me to drink plenty of milk, and that two
sunnyside-up eggs, bacon and hash-browns were a good part of a healthy
breakfast <smile>.

Jeff
-- 
Jeff Lasman <jblists@xxxxxxxxxxxxx>
nobaloney.net
P. O. Box 52672
Riverside, CA  92517
voice: (909) 787-8589  *  fax: (909) 782-0205