From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <634dfe943e8336054b4bb624596e421c@quanstro.net> Date: Tue, 5 May 2009 09:00:06 -0700 Message-ID: Subject: Re: [9fans] problems with redirection in rc From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: f65531c8-ead4-11e9-9d60-3106f5b1d025 On Tue, May 5, 2009 at 8:44 AM, roger peppe wrote: > in that case, surely it'd be trivial to make a root-suid > executable that allows namespace manipulation in > a non-sensitive area (e.g. /mnt)? maybe it could > be distributed as part of p9p meaning hacks like > $NAMESPACE could go away under linux. > maybe it already has been, and i'm as ignorant as usual. if you have the fuse kernel module installed, you can run mkdir $HOME/acme acme -m $HOME/acme and acme will mount itself there via 9pfuse. in general i don't view fuse etc as stable enough to warrant throwing away $NAMESPACE. also you'd still have to deal with non-linux systems. finally, in the specific case of label: the echoing trick is sad but also works around the lack of exported file system when you connect to another machine via ssh. (in plan 9, if you cpu somewhere rc can still find the terminal's /dev/label. not so on linux, even in the supposed presence of usable per-process name spaces.) russ