All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guy Van Den Bergh guy.vandenbergh@bigfoot.com
To: lartc@vger.kernel.org
Subject: [LARTC] cbq.init v 0.6.1
Date: Sun, 14 Jan 2001 20:29:33 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416881@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416879@msgid-missing>

<PRE>&gt;<i> 
</I>&gt;<i> Second -- you said it all.  You answered Y to all the QOS stuff rather
</I>&gt;<i> than M, so you have no modules, it's all compiled into the kernel (why
</I>&gt;<i> do folks insist on building monstrous monolithic kernels??).
</I>&gt;<i> 
</I>

Why tinkering with modules if you have the memory available anyway?
I have built a kernel with all I  need in it, and all I don't need out 
of it.
I think it is a lot easier (I never have to check whether module x or y 
is already loaded or not..).
With todays memory prices &quot;monstrous&quot; kernels are not a problem anymore 
anyway.

However, it is useful if you have to test new kernel functionality, or 
for building distributions with broad application possibilities.
But I do not see any reason to NOT build a monolithic kernel for just 
your own system.

Guy



</PRE>

  parent reply	other threads:[~2001-01-14 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-14 19:18 [LARTC] cbq.init v 0.6.1 Rick
2001-01-14 19:20 ` David
2001-01-14 20:29 ` Guy [this message]
2001-01-14 21:39 ` David

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=marc-lartc-98373940416881@msgid-missing \
    --to=lartc@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.