From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs config problem: accidental config deletion?
Date: Fri, 22 Feb 2002 13:55:03 +0100 [thread overview]
Message-ID: <200202221255.g1MCt3q02259@copernicus.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 22 Feb 2002 12:37:58." <20020222122536.A643419A6E@mail.cse.psu.edu>
Thanks for the reply.
Will I get feedback that tells me when I guessed the
filsys string wrong?
The reason I'm asking is that I know how I configured
the fake-worm part of main, but am a bit unsure about
the cache part, that is on another disk that also
contains an empty other file-system.
Because I made a dump before switching the system off,
I don't care much about the cache nor about the (empty)
other file system, assuming that I can use 'recover main'
to reinitialise the cache.
Yes, avoiding not-intented ream is very important.
(Seemingly) a long time ago with disk/kfs I included a
not-intended ream request, when I copied/pasted a
disk/kfs command from the man page without paying
attention to _all_ the options (i.e. overseeing the 'r' option);
luckily that was a very fresh file system,
just after installation -- it just took me time to
reinstall.
Axel.
> the configuration is stored where you tell it,
> and as you say, giving a new "config" command
> causes it to reset the configuration.
> you need to give it the filsys lines as before.
> DO NOT INCLUDE a ream request, or you WILL be sad.
> just the filsys
next prev parent reply other threads:[~2002-02-22 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 12:37 forsyth
2002-02-22 12:55 ` Axel Belinfante [this message]
2002-02-22 18:39 ` [9fans] fs config problem status update (still unsolved) Axel Belinfante
2002-02-28 21:06 ` Axel Belinfante
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 11:37 [9fans] fs config problem: accidental config deletion? 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=200202221255.g1MCt3q02259@copernicus.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).