From: Willy Tarreau <willy@w.ods.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
root@chaos.analogic.com
Subject: Re: Make ipconfig.c work as a loadable module.
Date: Sun, 9 Mar 2003 09:57:43 +0100 [thread overview]
Message-ID: <20030309085743.GA6138@alpha.home.local> (raw)
In-Reply-To: <200303090121.h291LDbx003771@eeyore.valparaiso.cl>
On Sat, Mar 08, 2003 at 10:21:13PM -0300, Horst von Brand wrote:
> The "floppy booting" discussed here is doing:
>
> dd if=bzImage of=/dev/fd0
>
> and booting that floppy directly. I really don't remember when I did that
> last time, it must have been at least 5 years ago.
I do use it frequently. I frequently boot systems using PXE, but sometimes,
either the bios is buggy, or I don't find how to set it up correctly, so the
better, and most reliable solution is to insert a floppy containing the kernel
which would have been loaded from the PXE server.
In fact, NONE of my systems need nor use an initrd. I find it really useful
to be able to boot from one single file. Having to set up an initrd is really
a pain compared to other trivial solutions. I'd really like Linux not to become
like microsoft products : it's not because one developper doesn't have the need
for something that he must prevent all his users/customers from using it.
I think that there are several people here who think they need ipconfig, and
that should be enough to understand that it's a useful feature, even if you
don't need it yourself.
Regards,
Willy
next prev parent reply other threads:[~2003-03-09 8:47 UTC|newest]
Thread overview: 32+ 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-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 [this message]
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=20030309085743.GA6138@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=vonbrand@inf.utfsm.cl \
/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