[647] in athena10

home help back first fref pref prev next nref lref last post

Re: attach -e

daemon@ATHENA.MIT.EDU (Greg Price)
Tue Dec 2 15:57:18 2008

Date: Tue, 2 Dec 2008 15:56:33 -0500
From: Greg Price <price@MIT.EDU>
To: Jonathan Reed <jdreed@mit.edu>
Cc: athena10@mit.edu
Message-ID: <20081202205632.GE10836@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D6C9FB0-FF09-4028-94AC-4EC11B65EB4D@mit.edu>

On Tue, Dec 02, 2008 at 03:46:59PM -0500, Jonathan Reed wrote:
> On Dec 2, 2008, at 3:38 PM, Greg Price wrote:
> >Perhaps I'm missing something, but this is equivalent to an
> >ln -s ; aklog, right?  So if I were attaching RW volumes, I'd just
> >symlink the volume into /mit on a single-user machine, or some other
> >location on a public machine.  Is there another reason that makes this
> >compelling as a special feature of attach?
> 
> Yes, because it puts it under the /mit mountpoint.  That way, you can  
> run software out of an RW volume.  If you attach it somewhere else,  
> the software will still refer to /mit/whatever and you'll get the RO  
> version, not the RW one.

Right, so
 $ sudo ln -s /afs/.athena/foo/bar /mit/bar
and then go about your business.

It only makes sense to be putting it in /mit on a single-user machine
anyway because otherwise you alter other users' namespaces and could
confuse them, so it's fine that you have to have root.

Greg

home help back first fref pref prev next nref lref last post