From: Samuel Flory <sflory@rackable.com>
To: michael_pruznick@mvista.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: root=nfs no longer works in 2.4.22
Date: Fri, 29 Aug 2003 16:21:16 -0700 [thread overview]
Message-ID: <3F4FDFEC.9040804@rackable.com> (raw)
In-Reply-To: <3F4FDD44.4151E86C@mvista.com>
Michael Pruznick wrote:
>Was root=nfs removed on purpose or is it an unexpected
>side effect of the "ROOT NFS fixes" patch from late
>July 2003?
>
>I understand this patch from the point of wanting to
>eliminate nfs attempts when nfs is not requested. That
>is clearly a reasonable thing to do. However, "root=nfs"
>is a nfs request that has been accepted in the past, I've
>been told, because nfs isn't a real device (but maybe it
>was accepted as bug and this patch fixed it).
>
>
>
So something like this doesn't work?
root=/dev/nfs ip=::::::dhcp nfsroot=10.10.1.1:/nfsroot
I know that this was work in rc2.
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-08-29 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 23:09 root=nfs no longer works in 2.4.22 Michael Pruznick
2003-08-29 23:21 ` Samuel Flory [this message]
2003-08-29 23:28 ` Herbert Poetzl
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=3F4FDFEC.9040804@rackable.com \
--to=sflory@rackable.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael_pruznick@mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.