All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Networking options + patch
Date: Mon, 24 Mar 2003 16:01:10 +0000	[thread overview]
Message-ID: <marc-lartc-104852178805841@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104851682931578@msgid-missing>

On Monday 24 March 2003 16:27, sun reflex4 wrote:
> thanx for the fast reply, and i have just printed the "Kernel HOWTO", to
> read it carefully before doing anything. In respect to "m", should i leave
> it in the .config, or replace it with "y" to enable e.g. CBQ or other
> things?
There are also other ways for configuring the kernel.  Try to run
make menuconfig
in /usr/scr/linux.

Compiling an option as module or not is your choice.  If you compile it as a 
module and you change something in the source, you can remove the module and 
reload the modified module.  I sometimes use it to test a change in the htb 
qdisc.  I also have all qos options compiled as module.  I don't use them so 
I don't have them in the kernel.  But if I want to use them to test 
something, there are loaded by the kernel.

Be aware, compiling and booting from your own kernel is a real challenge if 
it's your first time.  Be sure you ALWAYS have a good kernel so you can go 
back to your old situation.  Or try make bzdisk.  It will create the new 
kernel and place it on a floppy so you can boot from it.  If boot 
succesfully, you can configure your boot loader to use it.

I also suggest using grub as boot loader and not lilo.  Grub is "filesystem 
aware" so it can see the kernel in the file system.  If you use lilo, you 
have to update the bootloader each time you create a new kernel.  Debian has 
a script that finds all kernels that can be used and configures grub 
accordingly.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-03-24 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 14:38 [LARTC] Networking options + patch sun reflex4
2003-03-24 15:18 ` Stef Coene
2003-03-24 15:27 ` sun reflex4
2003-03-24 16:01 ` Stef Coene [this message]

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-104852178805841@msgid-missing \
    --to=stef.coene@docum.org \
    --cc=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.