public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Bronson <bronson@rinspin.com>
To: Scott Bronson <bronson@rinspin.com>
Cc: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>,
	linux-kernel@vger.kernel.org
Subject: Re: IDE?  IDE-TNG driver
Date: 17 Aug 2002 20:47:30 -0700	[thread overview]
Message-ID: <1029642451.1599.2.camel@emma> (raw)
In-Reply-To: <1029630519.1541.11.camel@emma>

> Everyone I've heard advocating a moduleless kernel uses an argument that
> boils down to "it's slightly more secure."  Does anybody have a GOOD
> reason for not using modules?  Obsolete or embedded hardware arguments
> don't count.

Someone replied off-list saying that initrds are too hard to create.

That's true.  They are.  One day, hopefully that will change.

Any other reasons?

    - Scott





  reply	other threads:[~2002-08-18  3:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 21:00 IDE? Martin J. Bligh
2002-08-16 21:28 ` IDE? Linus Torvalds
2002-08-17 11:52   ` IDE? Matthias Andree
2002-08-17 12:06     ` IDE? IDE-TNG driver Andre Hedrick
2002-08-17 13:56       ` Skip Ford
2002-08-17 15:23         ` Matthew D. Pitts
2002-08-17 20:07           ` Alan Cox
2002-08-17 17:16       ` Ruth Ivimey-Cook
2002-08-17 18:03         ` Andre Hedrick
2002-08-17 22:57           ` Ruth Ivimey-Cook
2002-08-17 23:06             ` Andre Hedrick
2002-08-18  3:01               ` Erik Andersen
2002-08-18  0:28             ` Scott Bronson
2002-08-18  3:47               ` Scott Bronson [this message]
2002-08-18  4:07                 ` Thomas Molina
2002-08-18  4:20                 ` CaT
2002-08-19  0:03               ` David Lang
2002-08-19  9:11               ` Helge Hafting
2002-08-17 12:08     ` IDE? Russell King
  -- strict thread matches above, loose matches on Subject: below --
2002-08-26 19:17 IDE? IDE-TNG driver David Balazic

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=1029642451.1599.2.camel@emma \
    --to=bronson@rinspin.com \
    --cc=Ruth.Ivimey-Cook@ivimey.org \
    --cc=linux-kernel@vger.kernel.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