From: "Stephen C. Tweedie" <sct@redhat.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andries.Brouwer@cwi.nl, helgehaf@idb.hist.no,
linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: [PATCH] struct char_device
Date: Thu, 24 May 2001 11:35:39 +0100 [thread overview]
Message-ID: <20010524113539.K27177@redhat.com> (raw)
In-Reply-To: <UTC200105231334.PAA86145.aeb@vlet.cwi.nl> <Pine.GSO.4.21.0105231351360.20269-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0105231351360.20269-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Wed, May 23, 2001 at 01:54:15PM -0400
Hi,
On Wed, May 23, 2001 at 01:54:15PM -0400, Alexander Viro wrote:
> On Wed, 23 May 2001 Andries.Brouwer@cwi.nl wrote:
>
> > > But I don't want an initrd.
> > Don't be afraid of words. You wouldnt notice - it would do its
> > job and disappear just like piggyback today.
>
> Andries, initrd code is _sick_. Our boot sequence is not a wonder of
> elegance, but that crap is the worst part. I certainly can understand
> people not wanting to use that on aesthetical reasons alone.
It's the principle of a kernel-linked boot image, not initrd, which is
important. Unpacking a cramfs image from an __init section is much
cleaner than initrd and has almost the same effect: the boot
filesystem just ends up readonly that way. Either way we can hook
in that default user-space code at boot time transparently.
--Stephen
next prev parent reply other threads:[~2001-05-24 11:17 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 13:34 [PATCH] struct char_device Andries.Brouwer
2001-05-23 17:54 ` Alexander Viro
2001-05-24 10:35 ` Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 20:01 Andries.Brouwer
2001-05-23 18:28 Andries.Brouwer
2001-05-23 18:42 ` Alexander Viro
2001-05-23 15:24 Wayne.Brown
2001-05-23 12:29 Andries.Brouwer
2001-05-23 12:30 ` Alan Cox
2001-05-23 13:26 ` Helge Hafting
2001-05-23 11:57 Andries.Brouwer
2001-05-23 12:13 ` Alan Cox
2001-05-23 6:47 Andries.Brouwer
2001-05-23 0:28 Andries.Brouwer
2001-05-23 0:38 ` Alexander Viro
2001-05-23 0:22 Andries.Brouwer
2001-05-23 0:29 ` Martin Dalecki
2001-05-23 0:20 Andries.Brouwer
2001-05-23 2:43 ` Linus Torvalds
2001-05-23 0:01 Andries.Brouwer
2001-05-22 23:33 Andries.Brouwer
2001-05-23 0:03 ` Alexander Viro
2001-05-22 22:17 Andries.Brouwer
2001-05-22 22:34 ` Martin Dalecki
2001-05-22 22:47 ` Martin Dalecki
2001-05-23 0:02 ` Jeff Garzik
2001-05-23 0:14 ` Jens Axboe
2001-05-23 2:40 ` Linus Torvalds
2001-05-23 12:35 ` Martin Dalecki
2001-05-22 21:35 Andries.Brouwer
2001-05-22 22:00 ` Martin Dalecki
2001-05-22 20:54 Andries.Brouwer
2001-05-22 21:17 ` Martin Dalecki
2001-05-22 22:37 ` Linus Torvalds
2001-05-22 23:51 ` Alexander Viro
2001-05-23 0:06 ` Jeff Garzik
2001-05-23 0:14 ` Jens Axboe
2001-05-23 2:37 ` Linus Torvalds
2001-05-23 3:04 ` Jeff Garzik
2001-05-23 3:21 ` Jeff Garzik
2001-05-23 9:05 ` Alan Cox
2001-05-23 2:35 ` Linus Torvalds
2001-05-22 19:52 Andries.Brouwer
2001-05-22 20:10 ` Alexander Viro
[not found] <Pine.GSO.4.21.0105221007460.15685-100000@weyl.math.psu.edu >
2001-05-22 15:26 ` Anton Altaparmakov
2001-05-22 16:08 ` Oliver Xymoron
2001-05-22 16:12 ` Alexander Viro
2001-05-22 17:30 ` Oliver Xymoron
2001-05-22 17:41 ` Alexander Viro
2001-05-22 19:22 ` Guest section DW
2001-05-22 19:25 ` Alexander Viro
2001-05-22 19:38 ` Oliver Xymoron
[not found] <Pine.LNX.4.10.10105221050080.8984-100000@coffee.psychology.mcmaster.ca>
2001-05-22 14:59 ` Tommy Hallgren
2001-05-22 14:40 Tommy Hallgren
2001-05-22 14:18 Alexander Viro
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=20010524113539.K27177@redhat.com \
--to=sct@redhat.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=helgehaf@idb.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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