From: philippe.anel@noos.fr (Philippe Anel)
To: 9fans@cse.psu.edu
Subject: Re: Fw: [9fans] some problems
Date: Tue, 28 Aug 2001 08:23:59 +0000 [thread overview]
Message-ID: <3b8b53b3.6555926@smtp.noos.fr> (raw)
In-Reply-To: <1070FB530C37D511967A006008F6A51456BD8B@hktgv001v3>
Hi,
On Tue, 28 Aug 2001 07:38:00 GMT, in comp.os.plan9 you wrote:
>This makes experimenting with the plan9.ini settings rather risky: when
>things go wrong it takes up to five (!) reboots just to get back to where I
>started.
plan9.ini file may contain multiple configurations. see plan9.ini(8).
It works for me (I had to re-compile 9load though).
>
>BTW, I noticed that the original plan9.ini on the install floppy is padded
>to exactly 512 bytes. Should I keep it that way ?
>
>Geerten
>
>
Philippe
next prev parent reply other threads:[~2001-08-28 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 7:20 g.j.kuiper
2001-08-28 8:23 ` Lucio De Re
2001-08-28 8:23 ` Philippe Anel [this message]
2001-08-29 9:05 ` Ian Richards
2001-08-28 11:15 g.j.kuiper
2001-08-28 11:46 g.j.kuiper
2001-08-28 11:57 ` Lucio De Re
2001-08-28 13:02 jmk
2001-08-28 17:32 ` geerten kuiper
2001-08-29 4:52 jmk
2001-08-29 6:48 g.j.kuiper
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=3b8b53b3.6555926@smtp.noos.fr \
--to=philippe.anel@noos.fr \
--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).