Messages in this thread | | | Date | Tue, 5 Aug 2003 10:57:11 -0400 (EDT) | From | "Richard B. Johnson" <> | Subject | Re: FS: hardlinks on directories |
| |
On Tue, 5 Aug 2003, Stephan von Krawczynski wrote:
> On Tue, 5 Aug 2003 09:36:37 -0400 (EDT) > "Richard B. Johnson" <root@chaos.analogic.com> wrote: > > > A hard-link is, by definition, indistinguishable from the original > > entry. In fact, with fast machines and the course granularity of > > file-system times, even the creation time may be exactly the > > same. > > Hello Richard, > > I really don't mind if you call the thing I am looking for a hardlink or a > chicken. And I am really not sticking to creating them by ln or mount or just > about anything else. I am, too, not bound to making them permanent on the > media. All I really want to do is to _export_ them via nfs. > And guys, looking at mount -bind makes me think someone else (before poor me) > needed just about the same thing. > So, instead of constantly feeding my bad conscience, can some kind soul explain > the possibilities to make "mount -bind/rbind" work over a network fs of some > flavor, please? > > Regards, > Stephan > > PS: if you ever want to find out what *nix people are carrying guns, just enter > the room and cry out loud "directory hardlinks to the left!" > ;-) >
But symlinks work over NFS. You just have to make sure they are relative to whatever the remote mount-point is:
Script started on Tue Aug 5 10:38:55 2003 # mount boneserver:/tmp /mnt # df Filesystem 1k-blocks Used Available Use% Mounted on /dev/sdb1 16603376 6560676 9199292 42% / /dev/sdc1 6356624 1217040 4816680 20% /alt /dev/sdc3 2253284 1796788 342036 84% /home/users /dev/sda1 1048272 280960 767312 27% /dos/drive_C /dev/sda5 1046224 181280 864944 17% /dos/drive_D boneserver:/tmp 3881192 2385676 1294706 65% /mnt # cd /mnt # ls # mkdir foo # ls foo # ln -s foo bar # ls bar foo # cd bar # pwd /mnt/bar # mkdir xxx # ln -s xxx ../zzz # cd .. # ls bar foo zzz # file zzz zzz: broken symbolic link to xxx # rm zzz # cd bar # ls xxx # file xxx xxx: directory # pwd /mnt/bar # ln -s /mnt/bar/xxx ../zzz # cd .. # ls bar foo zzz # file zzz zzz: symbolic link to /mnt/bar/xxx # ls zzz # home # umount /mnt # exit exit Script done on Tue Aug 5 10:41:41 2003
As you an clearly see, the symlink to the directories worked fine. You don't need a hard-link at all. I deliberately created a broken link, deleted it, then made another that works. Everything I did locally could have been done remotely on the server who's /tmp directory I mounted R/W. All you need to do to make such working links is to use the same mount-point name on each of you clients. That way, a sim-link will work the same for everybody.
Cheers, Dick Johnson Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips). Note 96.31% of all statistics are fiction.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |