From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, Kay Sievers <kay.sievers@suse.de>,
penberg@cs.helsinki.fi, gregkh@suse.de, bunk@stusta.de,
rml@novell.com, linux-kernel@vger.kernel.org,
johnstul@us.ibm.com
Subject: Re: 2.6.16-rc4: known regressions
Date: Wed, 22 Feb 2006 06:21:58 -0500 [thread overview]
Message-ID: <20060222112158.GB26268@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0602211700580.30245@g5.osdl.org>
On Tue, Feb 21, 2006 at 05:06:48PM -0800, Linus Torvalds wrote:
>
> To some degree, /initrd was supposed to do things like that, and in
> theory, it still could. However, realistically, 99% of any /initrd is more
> about the distribution than the kernel, so right now we have to count
> /initrd as a distribution thing, not a kernel thing.
... and if we're truly going to be pouring more and more complexity
into initrd (such as userspace swsusp), then (a) we probably should
make it more of a kernel-specific thing, and not a distro-specific
thing, since without that you can be pretty much guaranteed that more
and more people will be using and testing swsusp2, and not uswsusp,
and (b) we need to add _way_ better debugging provisions so that if
something dies in early boot, you don't go pulling out your hair
trying to figure out what went wrong, and having to spend a good 20
minutes or so between each try-to-fix the initrd, watch the boot fail,
reboot into a working setup, cursing Red Hat's nash, modifying the
initrd, and trying again.
Usually I break the loop by giving up, and ripping out whatever kernel
feature requires initrd, such as dm, and installing on hard partitions
with all of the kernel modules I need compiled into the kernel. I
still have no idea why mptscsi fails to detect SCSI disks when loaded
as a module via initrd on various bits of IBM hardware (including the
e326 and ls-20 blade), but works fine when compiled directly into the
kernel....
If we want more and more stuff to be poured into initrd, it's got to
be made easier to debug and consistent across distributions, such that
more people can test initrd configurations, and flush out the bugs,
never mind the question of programs like udev randomly breaking
between kernel releases. Maybe it's time to consider moving all of
that into the kernel source; if they wanted to be treated as part of
the kernel, then let them liteally become part of the kernel from a
source code and release management perspective.
- Ted
next prev parent reply other threads:[~2006-02-22 11:22 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 22:45 Linux 2.6.16-rc4 Linus Torvalds
2006-02-17 23:14 ` 2.6.16-rc4: known regressions Adrian Bunk
2006-02-19 11:06 ` Pekka Enberg
2006-02-19 14:54 ` Adrian Bunk
2006-02-19 17:50 ` Pekka Enberg
2006-02-19 21:14 ` Pekka Enberg
2006-02-20 1:02 ` Greg KH
2006-02-20 7:08 ` Pekka J Enberg
2006-02-21 22:51 ` Pekka Enberg
2006-02-21 22:57 ` Kay Sievers
2006-02-21 23:33 ` Andrew Morton
2006-02-22 0:04 ` Kay Sievers
2006-02-22 0:15 ` Mark Lord
2006-02-22 0:21 ` Andrew Morton
2006-02-22 0:34 ` Linus Torvalds
2006-02-22 0:46 ` Con Kolivas
2006-02-22 1:06 ` Linus Torvalds
2006-02-22 11:21 ` Theodore Ts'o [this message]
2006-02-22 14:25 ` uswsusp & initrd -- was " Pavel Machek
2006-02-22 15:48 ` Joel Becker
2006-02-22 16:25 ` Theodore Ts'o
2006-02-22 17:33 ` Gabor Gombas
2006-02-22 17:57 ` Linus Torvalds
2006-02-22 18:37 ` Christian Trefzer
2006-02-22 18:59 ` Joel Becker
2006-02-22 19:18 ` Greg KH
2006-02-22 19:29 ` Arjan van de Ven
2006-02-22 19:40 ` Greg KH
2006-02-22 20:45 ` Jens Axboe
2006-02-22 22:51 ` Greg KH
2006-02-23 6:39 ` Jens Axboe
2006-02-23 17:29 ` Martin Bligh
2006-02-23 17:52 ` Greg KH
2006-02-23 18:01 ` Martin Bligh
2006-02-23 18:04 ` Arjan van de Ven
2006-02-23 20:26 ` Benjamin LaHaise
2006-02-24 23:42 ` Eric W. Biederman
2006-02-22 19:39 ` Linus Torvalds
2006-02-22 19:54 ` Andrew Morton
2006-02-22 20:02 ` Arjan van de Ven
2006-02-22 20:12 ` Linus Torvalds
2006-02-22 20:44 ` Andrew Morton
2006-02-22 20:26 ` Greg KH
2006-02-23 5:28 ` Jody McIntyre
2006-02-22 20:57 ` Diego Calleja
2006-02-22 21:19 ` Russell King
2006-02-22 21:30 ` Greg KH
2006-02-22 20:47 ` Bryan O'Sullivan
2006-02-22 19:07 ` Greg KH
2006-02-22 17:06 ` Matthias Andree
2006-02-23 12:36 ` Paulo Marques
2006-02-22 10:49 ` Diego Calleja
2006-02-22 7:06 ` Pekka J Enberg
2006-02-22 15:27 ` Kay Sievers
2006-02-22 15:44 ` Linus Torvalds
2006-02-22 16:03 ` Arjan van de Ven
2006-02-22 16:11 ` Christoph Hellwig
2006-02-22 17:17 ` sysfs regressions (was: 2.6.16-rc4: known regressions) Matthias Andree
2006-02-22 17:47 ` Greg KH
2006-02-22 16:18 ` 2.6.16-rc4: known regressions David Zeuthen
2006-02-22 16:35 ` Christoph Hellwig
2006-02-22 16:46 ` David Zeuthen
2006-02-22 16:51 ` Christoph Hellwig
2006-02-22 17:08 ` Linus Torvalds
2006-02-22 17:31 ` Linus Torvalds
2006-02-22 18:04 ` Al Viro
2006-02-23 3:01 ` John Stoffel
2006-02-22 17:51 ` Al Viro
2006-02-22 17:55 ` Christoph Hellwig
2006-02-22 18:10 ` Al Viro
2006-02-22 19:25 ` David Zeuthen
2006-02-22 17:10 ` Al Viro
2006-02-22 17:10 ` grundig
2006-02-22 17:14 ` Martin Bligh
2006-02-23 4:17 ` Theodore Ts'o
2006-02-22 18:10 ` Pekka Enberg
2006-02-22 8:28 ` Arjan van de Ven
2006-02-17 23:27 ` Linux 2.6.16-rc4 Nigel Cunningham
2006-02-18 8:59 ` Edmondo Tommasina
2006-02-18 9:19 ` Gene Heskett
2006-02-18 10:20 ` Con Kolivas
2006-02-18 11:26 ` Gene Heskett
2006-02-18 16:04 ` Jean Delvare
2006-02-22 22:02 ` Linux 2.6.16-rc4 edac oops Mark Rustad
2006-02-24 11:09 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-02-22 2:39 2.6.16-rc4: known regressions Yu, Luming
2006-02-22 3:16 ` Adrian Bunk
2006-02-22 6:55 Yu, Luming
2006-02-22 12:23 ` Adrian Bunk
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=20060222112158.GB26268@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rml@novell.com \
--cc=torvalds@osdl.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