public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: David Lang <david.lang@digitalinsight.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6] The List, pass #2
Date: Thu, 01 Aug 2002 11:33:33 +0200	[thread overview]
Message-ID: <3D49006C.12ABC6FC@aitel.hist.no> (raw)
In-Reply-To: Pine.LNX.4.44.0207311500210.1038-100000@dlang.diginsite.com

David Lang wrote:
> 
> > > o Remove all hardwired drivers from kernel
> >
> > I really hope this means drivers MAY be used as modules, not MUST. There
> > is some overhead in doing things as modules, and added complexity usually
> > means "harder to debug." Particularly with modules where there can be
> > corner conditions and races on [un]load.
> 
> Bill,
>   Several people (IIRC including Alan Cox) would like to make many of the
> modules (network cards and scsi drivers for example) mandatory, requiring
> use of an initrd (or it's replacement) on all boot setups.

As far as I know, they plan on doing things like 
disk partition detection outside the kernel, i.e. in
a userspace program.  That clearly require
a initrd (or similiar) for anybody with root
on a partitioned disk.

Lots of other bootup initialization, like DHCP,
might move to userspace as well.  This gives a smaller
and safer kernel.

I cannot see this requiring modules though.  Even a
kernel without any module support at all should
work fine for those who compile their own.
Redhat and other distributors may be interested in
shipping a completely modular kernel that
loads modules from that initrd, but that certainly
won't be a _requirement_ for all kernels. 

Helge Hafting

  reply	other threads:[~2002-08-01  9:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19  4:47 [2.6] The List, pass #2 Guillaume Boissiere
2002-07-19  5:08 ` Karim Yaghmour
2002-07-19 12:41 ` mbs
2002-07-19 13:16 ` jlnance
2002-07-20  7:28 ` Bruce Harada
2002-07-28 10:47 ` Aaron Lehmann
2002-07-31 17:43 ` Bill Davidsen
2002-07-31 17:58   ` Christoph Hellwig
2002-07-31 18:54     ` Bill Davidsen
2002-07-31 20:20     ` Trond Myklebust
2002-07-31 20:23       ` Christoph Hellwig
2002-07-31 20:24         ` Christoph Hellwig
2002-07-31 20:34         ` Trond Myklebust
2002-08-01  0:31           ` Alan Cox
2002-07-31 23:42             ` J. Bruce Fields
2002-08-01  9:33             ` David Schwartz
2002-08-01 13:42               ` Alan Cox
2002-08-01 15:39                 ` J. Bruce Fields
2002-07-31 22:04   ` David Lang
2002-08-01  9:33     ` Helge Hafting [this message]
2002-08-03  3:40       ` Pavel Machek
2002-08-08  9:02         ` Helge Hafting
2002-08-13  3:00           ` Bill Davidsen
2002-08-13  5:27           ` H. Peter Anvin
2002-08-01  0:34   ` Neil Brown
2002-08-01  1:56 ` Albert D. Cahalan
2002-08-01  2:30   ` Roland Dreier
2002-08-01  3:25     ` Albert D. Cahalan
2002-08-01  4:05       ` Roland Dreier
2002-08-01  5:08   ` Linus Torvalds
2002-08-01  6:10     ` Austin Gonyou
2002-08-05  7:29       ` Rob Landley
2002-08-01 18:45     ` Ben Greear
2002-08-01 14:12   ` Alan Cox
2002-08-09  2:30 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-08-07 17:11 Matt_Domsch

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=3D49006C.12ABC6FC@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=david.lang@digitalinsight.com \
    --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