From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: changeset: Make forced module loading optional
Date: Mon, 5 May 2008 08:08:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805050805460.32269@woody.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0805050801120.32269@woody.linux-foundation.org>
On Mon, 5 May 2008, Linus Torvalds wrote:
>
> Right. Which is why I build the stuff into my kernel that is required, and
> then initrd can do whatever it damn well pleases.
Btw, I realize that a distro *can* make an initrd that only works with
their own kernel. I personally suspect I'll just switch distros if that
happens - I'm already irritated enough with startup scripts etc that
complain about "/proc/modules: No such file or directory" for stuff that
is already compiled in because they want to check if it's loaded.
But quite frankly, the distro really shouldn't need to make their startup
scripts (whether on initrd or just the regular /etc/rc.d/ ones) so
fragile. And quite frankly, I don't understand why people seem to use a
kernel *BUG* as an excuse to say that I shouldn't do what I have always
done - replace just the kernel.
Linus
next prev parent reply other threads:[~2008-05-05 15:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 4:55 Rusty Russell
2008-05-05 5:05 ` Linus Torvalds
2008-05-05 5:35 ` Rusty Russell
2008-05-05 17:07 ` Linus Torvalds
2008-05-05 18:42 ` Rusty Russell
2008-05-05 19:47 ` David Miller
2008-05-05 6:43 ` Jan Engelhardt
2008-05-05 14:37 ` Linus Torvalds
2008-05-05 14:50 ` Jeff Garzik
2008-05-05 15:01 ` Linus Torvalds
2008-05-05 15:08 ` Linus Torvalds [this message]
2008-05-05 15:32 ` Dave Jones
2008-05-05 15:48 ` Linus Torvalds
2008-05-05 16:01 ` Jan Engelhardt
2008-05-05 15:57 ` Alan Cox
2008-05-05 6:35 ` Jan Engelhardt
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=alpine.LFD.1.10.0805050805460.32269@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=jengelh@medozas.de \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®