From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] u9fs: dealing with user names that differ between unix and plan 9?
Date: Fri, 5 Apr 2002 10:33:19 -0500 [thread overview]
Message-ID: <88cb92cf3c9085596ad4e509df4e812f@plan9.bell-labs.com> (raw)
> I have set up u9fs on a linux machine as indicated in the README,
> and it works, when my plan 9 username is the same as my linux username.
> When there is no linux user with the same name as the plan 9 user
> that does the mount (attach), it fails. Is there a way to specify,
> from the plan9 side, what linux user name should be used when doing
> the mount (attach)? (like the -l option of rlogin)
No, sorry.
> It seems that the -u command line option of u9fs can be used as
> a kind of workaround: it allows me to choose one single linux user
> name onto which then all plan 9 users will be mapped, correct?
Yes.
Russ
next reply other threads:[~2002-04-05 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 15:33 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-05 15:44 forsyth
2002-04-05 18:23 ` Axel Belinfante
2002-04-08 13:14 ` Axel Belinfante
2002-04-05 14:23 Axel Belinfante
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=88cb92cf3c9085596ad4e509df4e812f@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).