From: rob@plan9.att.com rob@plan9.att.com
Subject: gnot1.link.bull.se online
Date: Sat, 9 Sep 1995 21:51:40 -0400 [thread overview]
Message-ID: <19950910015140.DDkN0_LalnjTKGesc1q4AhcoRbMmHy92cYLF3XAYItk@z> (raw)
>>One problem with ftpfs is that its mount point is only known
>>to the process that forked and execed the ftpfs command and
>>its children. I don't know how to change that, but I guess
>>I have to dabble some in mount and bind.
>No dabbling will fix that. You could hack ftpfs to stick itself
>into /srv and then mount that somewhere else. It's easy enough to
>do, just look at the 's' option in /sys/src/cmd/ramfs.c
Doesn't take any hacking. See srvfs(4). The last sentence even
says that this is the canonical use of the command.
-rob
next reply other threads:[~1995-09-10 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-10 1:51 rob [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-09-09 20:43 presotto
1995-09-09 15:41 Mikael
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=19950910015140.DDkN0_LalnjTKGesc1q4AhcoRbMmHy92cYLF3XAYItk@z \
--to=rob@plan9.att.com \
/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).