From: malware@t-online.de (Michael Mueller)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Russell King <rmk@arm.linux.org.uk>,
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, 07 Mar 2003 08:15:20 +0100 [thread overview]
Message-ID: <200303070715.IAA27138@fire.malware.de> (raw)
In-Reply-To: 1046996987.17718.144.camel@irongate.swansea.linux.org.uk
Hi Alan,
you wrote:
> > 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 ?
Sorry, but I must join Russel here. I have atleast one machine which has
a bootloader able to load exactly one file only. There is currently no
way to load an initrd. It would need to implement the whole (BOOTP+)TFTP
stuff again, just to get the initrd. So I was quite happy linux 2.4
still knows about mounting a NFS root filesystem without user-space
help.
Michael
next prev parent reply other threads:[~2003-03-07 7:05 UTC|newest]
Thread overview: 33+ 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
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-09 1:21 ` Horst von Brand
2003-03-09 8:57 ` Willy Tarreau
2003-03-07 21:47 ` William Lee Irwin III
2003-03-07 22:00 ` Chris Friesen
2003-03-07 7:15 ` Michael Mueller [this message]
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
2003-03-07 14:43 ` Charles Cazabon
2003-03-07 15:06 ` John Bradford
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=200303070715.IAA27138@fire.malware.de \
--to=malware@t-online.de \
--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 \
--cc=rmk@arm.linux.org.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 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.