From: Simon Horman <horms@verge.net.au>
To: "Ville Syrjälä" <syrjala@sci.fi>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Cc: Amos Waterland <apw@us.ibm.com>
Subject: Re: Problems with nfsroot due to ip= cmdline changes
Date: Sun, 6 Jan 2008 18:32:11 +0900 [thread overview]
Message-ID: <20080106093211.GB3172@verge.net.au> (raw)
In-Reply-To: <20080105165623.GA30987@sci.fi>
On Sat, Jan 05, 2008 at 06:56:23PM +0200, Ville Syrjälä wrote:
> I recently rebased my kernel tree and discovered that my nfsroot setup
> no longer worked. Here's the relevat part of my cmdline:
>
> ip=192.168.2.200:192.168.2.185:192.168.2.1:255.255.255.0::eth0:off nfsroot=192.168.2.185:/my_nfsroot,v3,tcp root=/dev/nfs
>
> I discovered that now I had to change the autoconfiguration option to
> "on" in order to make nfsroot work. I only want to specify the IP
> address manually so I don't really want autoconfiguration. The current
> code works since it will not try autoconfiguration when all options are
> specified manually but the current behaviour does not really match the
> documentation ie. now the autoconf parameter can disable the whole IP
> configuration step even though the documentation says it will only
> disable autoconfiguration.
>
> Looks like these are the relevant commits:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a6c05c3d064dbb83be88cba3189beb5db9d2dfc3
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9cecd07c3f7a818a5865daad8cb5be408508dc99
Hi,
I believe that this patch from Amos Waterland resolves the problem that
you are seeing: http://lkml.org/lkml/2008/1/5/247
--
Horms
prev parent reply other threads:[~2008-01-06 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 16:56 Ville Syrjälä
2008-01-06 9:32 ` Simon Horman [this message]
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=20080106093211.GB3172@verge.net.au \
--to=horms@verge.net.au \
--cc=apw@us.ibm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syrjala@sci.fi \
/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
all inboxes | Powered by JetHome®