[9fans] ftpfs

[9fans] ftpfs

[James]

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.

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.

thanks,
James

[9fans] ftpfs

[James]

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.

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

thanks,
James

Re: [9fans] ftpfs

[mirtchov]

> 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

Re: [9fans] ftpfs

[Richard C Bilson]

> 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.

Andrey is correct, but if you want to change the namespace for an
already-running instance of acme you can use the "Local" builtin --
i.e., type "Local some_namespace_changing_command" in a tag and sweep
it with B2.  Doing this won't affect instances of "win" that you're
already running, but it will affect new ones that you start.

Re: [9fans] ftpfs

[rob pike, esq.]

>> 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.
>
> Andrey is correct, but if you want to change the namespace for an
> already-running instance of acme you can use the "Local" builtin --
> i.e., type "Local some_namespace_changing_command" in a tag and sweep
> it with B2.  Doing this won't affect instances of "win" that you're
> already running, but it will affect new ones that you start.

right.  and clever uses of srvfs (see exportfs(4)) allow a name space created
in one window visible in another. in your case, if the ftp is already going,
you could run
	srvfs ftp /n/ftp
in that window, then run
	mount /srv/ftp /n/ftp
in another window or
	Local mount /srv/ftp /n/ftp
in acme.

-rob

[9fans] ftpfs

[boyd]

i found a bug when you hit your disc quota:

brahma% diff /n/sources/plan9/sys/src/cmd/ip/ftpfs/proto.c .
991,992c991
< 	getreply(&ctlin, msg, sizeof(msg), 0);
< 	return off;
---
> 	return getreply(&ctlin, msg, sizeof(msg), 0) == Success ? off : -1;