From: Pavel Machek <pavel@suse.cz>
To: Linus Torvalds <torvalds@transmeta.com>,
Helge Hafting <helgehaf@idb.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Acpi] Re: ACPI fundamental locking problems
Date: Tue, 10 Jul 2001 01:05:05 +0200 [thread overview]
Message-ID: <20010710010505.C557@bug.ucw.cz> (raw)
In-Reply-To: <3B442354.BCA61010@idb.hist.no> <Pine.LNX.4.33.0107050810400.22053-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0107050810400.22053-100000@penguin.transmeta.com>; from Linus Torvalds on Thu, Jul 05, 2001 at 08:17:04AM -0700
Hi!
> > 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.
>
> You would never even know the difference. You'd do a "make bzImage", and
> the default filesystem would just be embedded into the image. By default
> it probably doesn't need to do much - although things like the BIOS DPMI
> scan etc would surely be good to get rid of.
>
> Why complain about that?
I'm afraid it will make bzImage way bigger. And making bzImage build
dependend on libc is not nice... Or are you going with "userspace but
no libc" way? That would solve size, but such userspace
is... well.. not too different from kernel space ;-).
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
next prev parent reply other threads:[~2001-07-10 19:15 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
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 [this message]
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-08 7:26 ` Alexander Viro
2001-07-08 16:46 ` Jonathan Lundell
2001-07-09 14:40 ` Anthony DeBoer
2001-07-07 21:44 ` Steve VanDevender
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
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=20010710010505.C557@bug.ucw.cz \
--to=pavel@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).