From: Russell King <rmk@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>, Robin Holt <holt@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: Make ipconfig.c work as a loadable module.
Date: Fri, 7 Mar 2003 00:08:16 +0000 [thread overview]
Message-ID: <20030307000816.P838@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1046996987.17718.144.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Fri, Mar 07, 2003 at 12:29:47AM +0000
On Fri, Mar 07, 2003 at 12:29:47AM +0000, Alan Cox wrote:
> On Thu, 2003-03-06 at 23:19, Russell King wrote:
> > "klibc doesnt really matter"
> >
> > I'd prefer not to have to have thousands of special programs around
> > just to be able to boot my machines, especially when it was all in-
> > kernel up until this point.
> >
> > klibc yes, dietlibc with random other garbage in some random filesystem
> > which'd need maintaining - no thanks.
>
> You can build the dhcp client with glibc static into your initrd. Its hardly
> magic or special programs or random garbage, and last time I counted it came
> to one program. Dunno what the other 999 utilities your dhcp needs are ?
How about mount for nfs-root, a shell and a shell script to supply the
correct parameters to mount so it doesn't go and try to mount the
nfs-root with locking enabled - oh, and a few programs like sed and
so forth to pull the mount parameters out of the dhcp client output,
if there is such an output.
ipconfig.c does more than just configure networking. It's a far smaller
solution to NFS-root than any userspace implementation could ever hope
to be.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-03-07 0:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 21:10 Make ipconfig.c work as a loadable module Robin Holt
2003-03-06 22:34 ` Alan Cox
2003-03-06 22:11 ` Jeff Garzik
2003-03-06 22:25 ` Russell King
2003-03-06 22:32 ` Jeff Garzik
2003-03-07 0:13 ` Alan Cox
2003-03-06 23:19 ` Russell King
2003-03-07 0:29 ` Alan Cox
2003-03-07 0:08 ` Russell King [this message]
2003-03-07 1:29 ` Chris Dukes
2003-03-07 9:42 ` Russell King
2003-03-07 11:46 ` Bogdan Costescu
2003-03-08 2:03 ` Eric W. Biederman
2003-03-08 10:45 ` Bogdan Costescu
2003-03-08 16:07 ` Eric W. Biederman
2003-03-08 16:19 ` Russell King
2003-03-08 16:48 ` Eric W. Biederman
2003-03-08 17:05 ` Russell King
2003-03-08 18:01 ` Eric W. Biederman
2003-03-07 13:38 ` Chris Dukes
2003-03-07 14:29 ` Russell King
2003-03-07 16:23 ` Richard B. Johnson
2003-03-07 21:47 ` William Lee Irwin III
2003-03-07 22:00 ` Chris Friesen
2003-03-07 7:15 ` Michael Mueller
2003-03-07 12:54 ` Alan Cox
2003-03-07 21:33 ` Michael Mueller
2003-03-09 4:46 ` Arnaldo Carvalho de Melo
2003-03-07 9:10 ` 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=20030307000816.P838@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=holt@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).