From: Andrew Kelly <akelly@transparency.org>
To: "linux-admin@vger.kernel.org" <linux-admin@vger.kernel.org>
Subject: Re: Monolithic kernel again
Date: 13 Sep 2004 10:09:47 +0200 [thread overview]
Message-ID: <1095062986.19331.5.camel@hermes.at.home> (raw)
In-Reply-To: <Pine.SOL.4.56.0409111934210.7390@hadar.cse.Buffalo.EDU>
On Sun, 2004-09-12 at 01:36, Tony Gogoi wrote:
> > why don't you just do a make modules_install ? maybe it just needs the
> > presence of such a file
> > regardless of wether your kernel is modular or not.... atleast, if
> > nothing else , to ensure that there are no module
> > dependencies.....
> >
> A modular kernel may be a little more unstable then a monolithic kernel
> I've heard. I feel it would be better to have a monolithic kernel for a
> server. At least there won't be any probing for a non-existent device +
> race conditions.
Another good reason (my primary reason, actually) for putting a
monolithic kernel in a server is for security's sake.
Not being able to load modules narrows the threat vector a bit.
Andy
next prev parent reply other threads:[~2004-09-13 8:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 20:01 Monolithic kernel again Tony Gogoi
2004-09-10 20:13 ` Matt Hemingway
2004-09-10 20:28 ` Tony Gogoi
2004-09-10 20:53 ` Matt Hemingway
2004-09-10 21:31 ` terry white
2004-09-10 23:41 ` Tony Gogoi
2004-09-11 11:57 ` joy
2004-09-11 20:44 ` terry white
2004-09-11 20:58 ` Adrian C.
2004-09-11 23:38 ` Monolithic kernel again : Fixed :-) Tony Gogoi
2004-09-12 19:39 ` Monolithic kernel again terry white
2004-09-11 23:36 ` Tony Gogoi
2004-09-13 8:09 ` Andrew Kelly [this message]
2004-09-10 21:37 ` terry white
-- strict thread matches above, loose matches on Subject: below --
2004-09-12 22:27 terry white
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=1095062986.19331.5.camel@hermes.at.home \
--to=akelly@transparency.org \
--cc=linux-admin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.