public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org, viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: initrd does not boot in 2.6.3, working in 2.4.25
Date: Fri, 5 Mar 2004 09:06:19 -0800	[thread overview]
Message-ID: <20040305170619.GX655@holomorphy.com> (raw)
In-Reply-To: <200403051831.31271.vda@port.imtp.ilyichevsk.odessa.ua>

On Friday 05 March 2004 13:04, William Lee Irwin III wrote:
>> nfsroot works in 2.6.3 and above here. I'm not sure you need it per se
>> for initrd's; I think the way it's intended to work with that is for
>> the scripts to configure network interfaces, mount the nfsroot, and then
>> pivot_root(). Can you try without initrd?
>> Also, try passing ip= for these things.

On Fri, Mar 05, 2004 at 06:31:31PM +0200, Denis Vlasenko wrote:
> I run these things everyday.
> nfsroot and ip=.... works, no question about that.
> Just imagine all-modular kernel which needs to load ethernet driver first,
> *then* mount nfs root and pivot_root. Or nfsroot-over-wireless :)
> --
> vda

For this, you should probably script the initrd to do the IP
configuration and mount the nfsroot before pivot_root().


-- wli

  reply	other threads:[~2004-03-05 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 10:38 initrd does not boot in 2.6.3, working in 2.4.25 vda
2004-03-05 11:04 ` William Lee Irwin III
2004-03-05 16:31   ` Denis Vlasenko
2004-03-05 17:06     ` William Lee Irwin III [this message]
2004-03-05 21:28       ` Denis Vlasenko
     [not found] <1wle0-48P-31@gated-at.bofh.it>
2004-03-05 12:57 ` Pascal Schmidt
2004-03-05 16:27   ` Denis Vlasenko

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=20040305170619.GX655@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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