From: Russell King <rmk@arm.linux.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>,
Chris Dukes <pakrat@www.uk.linux.org>,
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: Sat, 8 Mar 2003 17:05:32 +0000 [thread overview]
Message-ID: <20030308170532.D1896@flint.arm.linux.org.uk> (raw)
In-Reply-To: <m1zno5kdnz.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Sat, Mar 08, 2003 at 09:48:16AM -0700
On Sat, Mar 08, 2003 at 09:48:16AM -0700, Eric W. Biederman wrote:
> I can change the contents of my ramdisk as easily as I can change
> the kernel command line. For the complex setups just placing
> a configuration file in the ramdisk is what seems to work the best
> in practice.
You'll forgive me if I don't think that "change the contents of ramdisk"
is as easy as changing the kernel command line.
Last time I checked, to change the contents of a ramdisk image, you needed
to ungzip it, mount it, make some changes, unmount it, re-gzip it, and
re-install the thing. Or, in the case of initramfs, you need to rebuild
the kernel image. Compare this to changing the kernel command line from
"root=/dev/hda1" to "root=/dev/nfs ip=dhcp" in the boot loader by hitting
a few keys on the keyboard before the kernel loads, and I think you'll
start to get my point here.
--
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-08 17:05 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
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 [this message]
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=20030308170532.D1896@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=ebiederm@xmission.com \
--cc=holt@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pakrat@www.uk.linux.org \
/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).