9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ftpfs
Date: Mon, 15 Sep 2003 09:20:26 -0600	[thread overview]
Message-ID: <30d67801812489a7cdc7e0ad045ff5ad@plan9.ucalgary.ca> (raw)
In-Reply-To: <001801c37b93$676dbd80$0100a8c0@zk6veaghhlt7u5>

> 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




  reply	other threads:[~2003-09-15 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 14:12 James
2003-09-15 15:20 ` mirtchov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-09  0:16 boyd
2003-09-15 15:32 Richard C Bilson
2003-09-15 15:51 ` rob pike, esq.
2003-09-15  8:27 James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30d67801812489a7cdc7e0ad045ff5ad@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).