From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] import
Date: Wed, 9 Oct 2002 16:30:55 -0400 [thread overview]
Message-ID: <6cd75b0b297ef230845f4187469f9849@plan9.bell-labs.com> (raw)
> Command `import' sometimes does what I don't want.
> Let's /mnt/factotum be:
> key dom=aichi-u.ac.jp proto=p9sk1 user=bootes !password?
> key dom=aichi-u.ac.jp proto=p9sk1 user=arisawa !password?
> And then assume I execute:
> import ar / /n/ar
> where ar is my cpu server.
> Then `import' will import remote fs as user bootes.
> I have some user accounts in 'ar' and I have to manage them.
> I want to have user option for `import'
> or to let `import' look $user.
>
> Same problem is also in `cpu'.
I added -k flags to mount, cpu, and import,
to specify arbitrary key patterns that get used
in auth_proxy (in addition to the patterns that
the commands already used). Pull down the
changes and then you can do:
import -k 'user=arisawa' / /n/ar
Russ
next reply other threads:[~2002-10-09 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 20:30 Russ Cox [this message]
2002-10-10 12:12 ` Kenji Arisawa
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 0:38 Kenji Arisawa
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=6cd75b0b297ef230845f4187469f9849@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).