From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] newaccount.html has gone missing
Date: Sun, 19 Feb 2006 09:50:29 +0100 [thread overview]
Message-ID: <4f4d5df2aa0d89ec125627373d6531e9@cat-v.org> (raw)
In-Reply-To: <6ac16811de59232cdd6b67e62c1365cb@collyer.net>
> Russ says that accounts are not needed any more to connect to sources
> (and thus to pull) and the current /bin/9fs seems to support that
> claim:
>
> case sources
> srv -q tcp!sources.cs.bell-labs.com sources
> mount -n /srv/sources /n/sources
>
> mount -n skips authentication entirely.
The problem is that that somewhat breaks patch(1), it still
works but spills a bunch of errors because it can't chmod
any files, and it shows up as created by none.
Also if you have a sources/contrib account you need to modify
your local 9fs to remove the -n.
Maybe we should add a sourcesauth entry to 9fs?
uriel
next prev parent reply other threads:[~2006-02-19 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 6:06 Frank Gleason
2006-02-19 6:45 ` geoff
2006-02-19 8:50 ` uriel [this message]
2006-02-19 8:55 ` geoff
2006-02-19 9:17 ` jmk
2006-02-19 9:18 ` andrey mirtchovski
2006-02-19 10:25 ` uriel
2006-02-19 19:20 Russ Cox
2006-02-22 2:22 ` Frank Gleason
2006-03-07 13:23 uriel
2006-03-07 13:45 ` Russ Cox
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=4f4d5df2aa0d89ec125627373d6531e9@cat-v.org \
--to=uriel@cat-v.org \
--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).