NFS mounting a directory of symbolic links to other directories

[jay-R5TnC2l8y5lBDgjK7y7TUQ at public.gmane.org]

Why not just use permission to control access? Have a group for restricted music and limit read access to that group.

Not sure it will work with your setup but it sounds easier to manage. 

------Original Message------
From: Don Levey
Sender: discuss-bounces-mNDKBlG2WHs at public.gmane.org
To: L BLU
Sent: Feb 25, 2009 12:24 PM
Subject: Re: NFS mounting a directory of symbolic links to other directories

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Eisenbraun wrote:
> On Wed, Feb 25, 2009 at 11:49:30AM -0500, Don Levey wrote:
>> Ben Eisenbraun wrote:
>>> Hard links can't cross file system boundaries.  Are /base/music and 
>>> /base/kidsmusic on the same file system?
>>>
>> Yes, they are - on both machines.
> 
> Hmm, I'm not sure I follow you.
> 
Sorry, I wasn't properly clear.  On the server /base/media/music and
/base/media/kidsmusic and on the same filesystem, on the same physical disk.

On the kids' machine, everything under /base/kidsmusic is also on the
same filesystem (but remotely mounted).  However, looking at that is a
bit of a "duh!" moment, as it's only an empty directory serving as a
mountpoint.

> When I say that hard links can't cross file system boundaries, I mean 
> the linked files have to be on the same file system on the same partition 
> on the same physical disk (lvm and RAID notwithstanding).  They can't 
> just be mounted in the same directory tree.
> 
> Does that make sense?
> 
Yup.

> So for the hard link method to work, /base needs to be a single file 
> system.  You could check that in the 'mount' output, e.g.
> 
> I think hard links would actually work nicely in this situation.  I haven't 
> tested it, but I think you would only need a single NFS export with the 
> hard link solution, so the kids machine could mount the kidsmusic directory 
> and nothing else.
> 

Since that's the goal, I'm looking into the possibility.  I'm also
looking at the "cp -al" suggestion mentioned by John, which looks to be
an easy way to accomplish this.

Thanks again!
 -Don

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJpX6yiVR8AmYXiFARAmALAJ96/ec88e69nUfDG3moapqFZmaqgACeIgX0
FWQfAhov//eHyohxJ+sFJKE=
=/u3H
-----END PGP SIGNATURE-----
_______________________________________________
Discuss mailing list
Discuss-mNDKBlG2WHs at public.gmane.org
http://lists.blu.org/mailman/listinfo/discuss



Sent from my BlackBerry® smartphone with SprintSpeed