From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] auth
Date: Mon, 29 Apr 2002 10:35:31 -0400 [thread overview]
Message-ID: <0fe00bca29e2e29b47b64ab0a8fe29a6@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3 bytes --]
yes
[-- Attachment #2: Type: message/rfc822, Size: 1377 bytes --]
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] auth
Date: Mon, 29 Apr 2002 16:26:21 +0200
Message-ID: <20020429142622.BA15F19A1C@mail.cse.psu.edu>
A silly question.
Can the auth database be used as-is to upgrade a 3rd
ed cpu server to a 4th ed one?
Otherwise all my users will have to enter their passwords again.
thanks
next reply other threads:[~2002-04-29 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 14:35 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-29 14:30 forsyth
2002-04-29 14:26 Fco.J.Ballesteros
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=0fe00bca29e2e29b47b64ab0a8fe29a6@plan9.bell-labs.com \
--to=presotto@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).