mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Dukes <pakrat@www.uk.linux.org>
To: Alan Cox <alan@lxorguk.ukuu.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, 7 Mar 2003 01:29:05 +0000	[thread overview]
Message-ID: <20030307012905.G20725@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030307000816.P838@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Fri, Mar 07, 2003 at 12:08:16AM +0000

On Fri, Mar 07, 2003 at 12:08:16AM +0000, Russell King wrote:
> > 
> > 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.

If IBM can fit a kernel and a ramdisk containing all the utilities you
describe and more in smaller than 5M of file for tftp, one would think 
that it could be done on Linux.
> 
> 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.

That's nice.  Would you mind explaining to us where that would be a
benefit?  Aside from dead header space in elf executables, I'm at
a loss as to how a usermode implementation must be significantly
larger than kernel code.

-- 
Chris Dukes
I tried being reasonable once--I didn't like it.

  reply	other threads:[~2003-03-07  1:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 21:10 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 [this message]
2003-03-07  9:42                 ` Russell King
2003-03-07 11:46                   ` Bogdan Costescu
2003-03-08  2:03                     ` 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
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
     [not found] <Pine.LNX.4.44.0303081132030.12316-100000@kenzo.iwr.uni-heidelberg.de>
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

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=20030307012905.G20725@parcelfarce.linux.theplanet.co.uk \
    --to=pakrat@www.uk.linux.org \
    --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

all inboxes | Powered by JetHome®