From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] hello
Date: Sat, 22 Jun 2002 08:46:33 -0400 [thread overview]
Message-ID: <Pine.LNX.4.30.0206220841420.9777-100000@athena> (raw)
Quick question,
How can I pull all the config info off of the fileserver
that I might write it down somewhere in the event of
disaster? It's been about 2 years since I set up the
fs here and between office moves and passed time if I wrote
it down it has since vanished.
Please pardon me for not hunting in the paper, but I know
Russ can probably give me the command in a snap so I can keep
working.
Cheers,
Sam
next reply other threads:[~2002-06-22 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-22 12:46 Sam [this message]
2002-06-22 13:46 rob pike, esq.
2002-06-22 15:54 anothy
2004-01-27 0:35 cbishop
2004-01-27 0:46 ` mirtchov
2004-01-28 0:51 ` okamoto
2004-01-28 23:00 tinhanhvanthe
2004-01-31 10:19 tomatojoe
2004-02-02 15:10 bob
2004-07-26 18:17 [9fans] Hello Post Office
2010-10-27 6:10 [9fans] HELLO hernando hernandez flores
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=Pine.LNX.4.30.0206220841420.9777-100000@athena \
--to=sah@softcardsystems.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).