netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, 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: Thu, 6 Mar 2003 22:25:46 +0000	[thread overview]
Message-ID: <20030306222546.K838@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030306221136.GB26732@gtf.org>; from jgarzik@pobox.com on Thu, Mar 06, 2003 at 05:11:36PM -0500

On Thu, Mar 06, 2003 at 05:11:36PM -0500, Jeff Garzik wrote:
> On Thu, Mar 06, 2003 at 10:34:16PM +0000, Alan Cox wrote:
> > On Thu, 2003-03-06 at 21:10, Robin Holt wrote:
> > > The patch at the end of this email makes ipconfig.c work as a loadable 
> > > module under the 2.5.  The diff was taken against the bitkeeper tree 
> > > changeset 1.1075.
> > 
> > The right fix is to delete ipconfig.c, it has been the right fix for a long
> > long time. There are initrd based bootp/dhcp setups that can also then mount
> > a root NFS partition and they do *not* need any kernel helper.
> 
> The klibc tarball on kernel.org also has ipconfig-type code, waiting for
> initramfs early userspace :)
> 
> Many have wanted to delete ipconfig.c for a while now...

Yep, can't the deletion wait a couple more weeks or so until klibc gets
merged?  It's not like ipconfig.c is broken currently, is it?

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

  reply	other threads:[~2003-03-06 22:25 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 [this message]
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-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=20030306222546.K838@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).