From: Tobias Brox <tobias@stud.cs.uit.no>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: nfsroot.c + ipconfig.c (2.4.20)
Date: Sat, 26 Apr 2003 12:33:56 +0200 [thread overview]
Message-ID: <20030426123356.C12540@stud.cs.uit.no> (raw)
In-Reply-To: <shs8yu1uqak.fsf@charged.uio.no>; from trond.myklebust@fys.uio.no on Wed, Apr 23, 2003 at 06:33:39PM +0200
[Trond Myklebust - Wed at 06:33:39PM +0200]
> ftp://ftp.uninett.no/pub/linux/docs/HOWTO/mini/NFS-Root
I'm pretty sure my problems stems from something fishy in the kernel
code, not simply because I don't know what I'm doing.
The FAQ above is not much up-to-date, either. I have a creeping
feeling that the nfsroot feature is not much used together with the
more recent kernel versions, as most modern computers are equipped
with harddisks. I'd like to hear success-stories from people that
have managed to do a diskless boot with a kernel of version 2.4.20 or
more recent.
According to a an earlier mail to this list (available at
http://www.geocrawler.com/archives/3/35/2001/6/0/6079479/ ) ipconfig
should be called from init/main.c:checksetup() - I can say for sure
that this does not take place, regardless of what options I feed the
kernel with.
In the 2.5.66-version of the kernel, the function above has been
renamed to obsolete_checksetup.
When booting up with 2.5.66, it also fails to load the network driver
in time. I know I have compiled the right driver into the kernel (and
not as a module).
--
Check our new Mobster game at http://hstudd.cs.uit.no/mobster/
(web game, updates every 4th hour, no payment, no commercials)
next prev parent reply other threads:[~2003-04-26 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 15:10 PROBLEM: nfsroot.c + ipconfig.c (2.4.20) Tobias Brox
2003-04-23 16:33 ` Trond Myklebust
2003-04-26 10:33 ` Tobias Brox [this message]
2003-04-26 10:39 ` Tobias Brox
2003-04-29 12:28 ` Hans-Peter Jansen
2003-04-29 12:37 ` Tobias Brox
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=20030426123356.C12540@stud.cs.uit.no \
--to=tobias@stud.cs.uit.no \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.