Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NFS mounting a directory of symbolic links to other directories

On 02/26/2009 01:34 PM, Abreau John wrote:
>  =20
>> First a symbolic link is nothing more than a file containing=20
>> a path. If that path is valid the link works, if it is not, it doesn't=
>> So, if on a remote system, the target is mounted at a different=20
>> point the link will not be valid.
>>    =20
> A symlink stores that path within the inode; it doesn't use any data bl=
>  =20
Both is true. It will be stored in the inode if it's size is within a=20
certain range, otherwise it will be stored as a file. It used to be=20
stored as a file, but now nearly every inode is stored in the inode=20
structure. It is also dependent on the filesystem. Ext2 is different=20
from reiserFS. The important thing is the behavior whether the symbolic=20
link is the old way (as a file) or the newer way in the inode itself.

The behavior is that the path is stored, and this allows for crossing=20
the file system boundaries where a hard link is essentially a pointer to =

the inode element.

Jerry Feldman <gaf-mNDKBlG2WHs at>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /