From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] ethernet detection problems
Date: Sun, 27 Nov 2005 20:42:58 -0500 [thread overview]
Message-ID: <ee9e417a0511271742i7640284ej526245b0a367ceb1@mail.gmail.com> (raw)
In-Reply-To: <820b2c9014c3f18bf8a2a9b351b67c93@orthanc.cc.titech.ac.jp>
> If it properly reflects the actual boot method, we could
> write a trivial script "bootmethod" and hide those knowledge
> concerning /srv in there, maybe?
>
> % bootmethod
> kfs #S/sdC0/fs
I don't understand how this would be used.
Knowing where the root file system came from
is not a very common need.
Russ
next prev parent reply other threads:[~2005-11-28 1:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 1:29 YAMANASHI Takeshi
2005-11-28 1:42 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-25 4:57 Ray Amberg
2005-11-25 6:00 ` Federico Benavento
2005-11-25 17:35 ` jmk
2005-11-25 13:57 ` Russ Cox
2005-11-06 6:41 Ray Amberg
2005-11-06 14:42 ` Russ Cox
2005-11-07 10:45 ` Charles Forsyth
2005-11-06 21:22 ` Federico Benavento
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=ee9e417a0511271742i7640284ej526245b0a367ceb1@mail.gmail.com \
--to=rsc@swtch.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).