l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 May 29 08:57

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Building a big kernel verses one that uses modules
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Building a big kernel verses one that uses modules

Thanks ME

I'm reading it now

----- Original Message ----- 
From: "ME" <dugan@passwall.com>
To: <vox-tech@lists.lugod.org>
Sent: Friday, May 28, 2004 11:54 PM
Subject: Re: [vox-tech] Building a big kernel verses one that uses modules

me@heyjay.com said:
> Hi,
> To piggyback on the other thread "Can't mount root while booting 2.6.5
> kernel"  ME said:
>>> How do you eliminate the need for initrd on a system? Simple, make
> support
>>> for all required hardware necessary to get "/" and supported volumes
>>> mounted an permit the booting of your machine to continue.
> How do you know what you have to have in the kernel?  I went thru
> 2.6.5's menuconfig and there are a billion options.  I'd like to build a
> small kernel but I don't know what I need what I don't need.  I know I'd
> like it to be built for my AMD chip, I'd like raid.  I know I don't need
> any (except one) of the network drives but the rest...who knows.
> I know there is "make defconfig" but then most of the stuff is modules
> I guess what I'm asking is there a minumum config that one can start
> with and add to, rather than starting with everthing and knowing what
> you need to get rid of?

Though it is not current to a 2.6.x kernel, I offered a presentationon
building kernels, and one of the key points I tried to address was
gathering information on what options you may want to select when
configuring a kernel.

(Shameless self plug)

This is a copy of the presentation with slides, summary of what I said for
each slide, and comments from the people in the audience.

You can skip most of the stuff (theory) up until you get to "HOW"

>From that point until the end, you should find helpful information.

The idea I provide is to use existing running and working kernels to your
advantage. I try to go through various tools made availbale to you as an
admin to inspect the running system and better decide what things you
should enable in your config.

This presentation took nearly 3 hours of straight talking. It really
should be broken into 2 or 3 parts clumped in this order
1) Theory
2) Interface for selection of kernel options (without explanation of what
will be selected)
3) Tools for gathering information about your machine to help decide what
hardware you have, and what you will want to support
4) Step through the actual process of configuring, building, installing
and testing kernels (System.map, modules, etc)
5) Applying kernel patches to enhance security or offer other features.

1, 2 and 3 would probably be one persentation, and 4 and 5 would be part
of a second presentation.


vox-tech mailing list

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.