From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <30d67801812489a7cdc7e0ad045ff5ad@plan9.ucalgary.ca> To: 9fans@cse.psu.edu Subject: Re: [9fans] ftpfs From: mirtchov@cpsc.ucalgary.ca In-Reply-To: <001801c37b93$676dbd80$0100a8c0@zk6veaghhlt7u5> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Mon, 15 Sep 2003 09:20:26 -0600 Topicbox-Message-UUID: 373f7670-eacc-11e9-9e20-41e7f4b1d025 > hi, > > just got plan9 installed and i can't figure out how to get the namespace > mounted on /n/ftp from the process/window that started it in acme into > another window so i can use the mouse to traverse the file structures. you can't jump across namespaces easily in Plan 9. if you think of them as hierarchical structures much like directory trees then it'd be obvious that in order to have the same mount/bind show up in two different rio windows they have to be descendants of the same namespace where the bind happened. for example, at the end of lib/profile's execution there's a uniform namespace in which rio starts. therefore every new rio window you open will be a descendant of this namespace (that's why you can import another machines' /net on top of your /net, open another window and see no effects of it whatsoever). so, to start a new window in rio sharing the same namespace with a previous one, you'll need to run 'window -m' in the second to create the first. then running acme /n/ftp will show the right thing, instead of an empty directory. this is exemplified in the following example, creating two different windows, one acting as the input for an irc client, the otheracting as a display (so the text i type doesn't mangle the text i receive from the server): % bind '#|' /tmp # this pipe connects the two windows % window -m # create the new window, sharing the same namespace % irc < /tmp/data # start the display, taking input from one end of the pipe now in the other window: % cat > /tmp/data1 # start the input ..... > > also, i can start the ftpd by aux/listen tcp but how do i start just the ftp > service? aux/listen tcp21 doesn't do it. ip/ftpd says it needs a network > address but it seems proper protocol that aux/listen is used from the man > pages > copy the tcp21 file in a new directory, say $home/ftp and run "aux/listen -d $home/ftp". better yet, check the listen1(8) man page, which will open just one port executing just one command. andrey