is this because the inodes are only guaranteed to be _unique_ within a filesystem - and not *across* filesystems? -jf On Wed, 26 Feb 2003 12:49:30 -0500, "Balint, Jess" <JBalint@alldata.net> said: > Allen, > > The reason that you cannot create a hard link on a remote file system is > because it has to be done of the system that the fs is local. That is why > you can login to the box, then create the link and logout and it shows > remotely. I think it is taken care of somewhere in the vfs layer. > > jess > > > -----Original Message----- > > From: Allen Curtis [mailto:acurtis@onz.com] > > Sent: Wednesday, February 26, 2003 10:09 AM > > To: Newbies > > Subject: Hard links and Auto Mounting > > > > > > I was wondering if someone could explain this too me. > > > > What is the difference when trying to create hard links on a > > local drive vs. > > a remote auto mounted drive? In either case the links are > > being made to > > files on the same physical disk. However you cant actually > > create hard links > > unless it is recognized as a local drive. e.g. If you ssh > > into the remote > > machine, create the links, then exit, everything is fine. > > > > TIA > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > > -- "It's an extraordinary world!" - jfsworld <at> fastmail.fm -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
