From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Dick Streefland <dick.streefland@altium.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS-mounted, read-only /dev unusable in 2.6
Date: Tue, 03 Aug 2004 16:42:23 +0200 [thread overview]
Message-ID: <410FA44F.1020804@bio.ifi.lmu.de> (raw)
In-Reply-To: <64bf.410f9d6f.62af@altium.nl>
Dick Streefland wrote:
> Frank Steiner <fsteiner-mail@bio.ifi.lmu.de> wrote:
> | Or is there any other way to get an initial console or
> | output any messages from an init script if one boots via nfsroot
> | and / (and thus, /dev) is only exported read-only from the
> | server?
>
> You can boot with a ramdisk as root, initialized with an initrd, and
> then perform all NFS mounts manually in the init script. You can use
> pivot_root to switch to an NFS root to get rid of the ramdisk.
I'm hoping for an easier solution, because it's a lot of work just
to get the console messages onto the screen. But maybe I have to go
through this :-)
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
next prev parent reply other threads:[~2004-08-03 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 8:09 NFS-mounted, read-only /dev unusable in 2.6 Frank Steiner
2004-08-03 14:13 ` Dick Streefland
2004-08-03 14:42 ` Frank Steiner [this message]
2004-08-03 17:28 ` L A Walsh
2004-08-04 6:27 ` Frank Steiner
2004-08-03 21:09 ` Miquel van Smoorenburg
2004-08-04 6:34 ` Frank Steiner
2004-08-04 6:47 ` Miquel van Smoorenburg
2004-08-04 7:00 ` Frank Steiner
2004-08-04 7:05 ` Neil Brown
2004-08-04 10:35 ` Frank Steiner
2004-08-04 11:02 ` Neil Brown
2004-08-05 6:30 ` Frank Steiner
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=410FA44F.1020804@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=dick.streefland@altium.nl \
--cc=linux-kernel@vger.kernel.org \
/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