From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Helge Hafting <helgehaf@idb.hist.no>,
Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Acpi] Re: ACPI fundamental locking problems
Date: Thu, 05 Jul 2001 04:34:52 -0400 [thread overview]
Message-ID: <3B4426AC.465712DE@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0107040956310.1668-100000@penguin.transmeta.com> <3B442354.BCA61010@idb.hist.no>
Helge Hafting wrote:
> I am fine with "You have to use initrd (or similiar) _if_ you want this
> feature."
> But please don't make initrd mandatory for those of us who don't
> need ACPI, don't need dhcp before mounting disks and so on.
I've always thought it would be neat to do:
cat bzImage initrd.tar.gz > vmlinuz
rdev --i-have-a-tarball-piggyback vmlinuz
Linking into the image is easy for hackers, but why not make it
scriptable and super-easy for end users? x86 already has the rdev
utility to mark a kernel image as having certain flags. It could even
be a command line option, "inittgz" or somesuch, telling us that a
gzip-format tarball immediately follows the end of our ELF image.
I wonder if any bootloader mods would be needed at all to do this...
AFAICS you just need to make sure the kernel doesn't trample the
piggyback'd data.
--
Jeff Garzik | Thalidomide, eh?
Building 1024 | So you're saying the eggplant has an accomplice?
MandrakeSoft |
next prev parent reply other threads:[~2001-07-05 8:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 10:37 [Acpi] Re: ACPI fundamental locking problems Dave J Woolley
2001-07-04 11:03 ` Alan Cox
2001-07-04 17:05 ` Linus Torvalds
2001-07-05 8:20 ` Helge Hafting
2001-07-05 8:34 ` Jeff Garzik [this message]
2001-07-05 11:21 ` Alan Cox
2001-07-05 13:42 ` Alexander Viro
2001-07-05 15:17 ` Linus Torvalds
2001-07-06 7:34 ` Benjamin Herrenschmidt
2001-07-06 8:45 ` Helge Hafting
2001-07-06 11:16 ` Alan Cox
2001-07-06 12:42 ` Daniel Phillips
2001-07-09 23:05 ` Pavel Machek
2001-07-07 10:32 ` Eugene Crosser
2001-07-07 11:32 ` Alexander Viro
2001-07-07 13:37 ` Eugene Crosser
2001-07-07 13:50 ` Jeff Garzik
2001-07-07 17:24 ` Daniel Phillips
2001-07-07 21:31 ` Jamie Lokier
2001-07-07 21:44 ` Steve VanDevender
2001-07-08 7:26 ` Alexander Viro
2001-07-08 16:46 ` Jonathan Lundell
2001-07-09 14:40 ` Anthony DeBoer
2001-07-07 11:34 ` Jeff Garzik
2001-07-07 21:40 ` Mike Touloumtzis
2001-07-07 21:54 ` Jamie Lokier
2001-07-07 22:00 ` arjan
2001-07-07 22:15 ` Jamie Lokier
2001-07-07 22:04 ` Mike Touloumtzis
2001-07-07 22:14 ` Jamie Lokier
2001-07-08 2:57 ` Keith Owens
2001-07-12 15:57 ` Eric W. Biederman
2001-07-12 16:14 ` Jeff Garzik
2001-07-12 21:18 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 5:26 Andreas Dilger
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=3B4426AC.465712DE@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=helgehaf@idb.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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