00000063.htm

一份很好的linux入门资料

&nbsp;<BR>
Now&nbsp;issue&nbsp;the&nbsp;command:&nbsp;
&nbsp;<BR>

&nbsp;<BR>
tar&nbsp;xzvf&nbsp;linux-kernel-source.tar.gz
&nbsp;<BR>

&nbsp;<BR>
I&nbsp;have&nbsp;a&nbsp;habit&nbsp;of&nbsp;always&nbsp;including&nbsp;w&nbsp;(wait&nbsp;for&nbsp;confirmation)&nbsp;in&nbsp;the&nbsp;tar&nbsp;&nbsp;<BR>
option&nbsp;string,&nbsp;then&nbsp;when&nbsp;I&nbsp;see&nbsp;that&nbsp;the&nbsp;.tar.gz&nbsp;or&nbsp;.tgz&nbsp;file&nbsp;is
&nbsp;<BR>
going&nbsp;to&nbsp;unpack&nbsp;into&nbsp;its&nbsp;own&nbsp;subdirectory,&nbsp;I&nbsp;ctrl-C&nbsp;out&nbsp;and&nbsp;reissue&nbsp;the&nbsp;&nbsp;<BR>
command&nbsp;without&nbsp;the&nbsp;w.&nbsp;This&nbsp;way&nbsp;I&nbsp;can&nbsp;prevent
&nbsp;<BR>
corrupted&nbsp;archives&nbsp;from&nbsp;unpacking&nbsp;into&nbsp;the&nbsp;current&nbsp;directory.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Once&nbsp;you&nbsp;have&nbsp;the&nbsp;kernel&nbsp;unpacked,&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;patches&nbsp;you&nbsp;wish&nbsp;to&nbsp;apply,&nbsp;&nbsp;<BR>
now&nbsp;is&nbsp;a&nbsp;good&nbsp;time.&nbsp;Let's&nbsp;say&nbsp;you&nbsp;don't&nbsp;wish&nbsp;to
&nbsp;<BR>
run&nbsp;kernel&nbsp;2.0.30,&nbsp;but&nbsp;you&nbsp;do&nbsp;want&nbsp;the&nbsp;tcp-syn-cookies.&nbsp;Copy&nbsp;the&nbsp;patch&nbsp;&nbsp;<BR>
(called&nbsp;tcp-syn-cookies-patch-1)&nbsp;into&nbsp;the&nbsp;/usr/src&nbsp;directory
&nbsp;<BR>
and&nbsp;issue&nbsp;the&nbsp;command:&nbsp;
&nbsp;<BR>

&nbsp;<BR>
patch&nbsp;&lt;&nbsp;tcp-syn-cookies-patch-1
&nbsp;<BR>

&nbsp;<BR>
This&nbsp;command&nbsp;applies&nbsp;the&nbsp;patch&nbsp;to&nbsp;the&nbsp;kernel.&nbsp;Look&nbsp;for&nbsp;files&nbsp;with&nbsp;an&nbsp;.rej&nbsp;&nbsp;<BR>
extension&nbsp;in&nbsp;in&nbsp;the&nbsp;/usr/src&nbsp;directory.&nbsp;These&nbsp;files&nbsp;didn't
&nbsp;<BR>
patch&nbsp;properly.&nbsp;They&nbsp;may&nbsp;be&nbsp;unimportant,&nbsp;but&nbsp;peruse&nbsp;them&nbsp;anyway.&nbsp;If&nbsp;you&nbsp;&nbsp;<BR>
installed&nbsp;a&nbsp;Red&nbsp;Hat&nbsp;system&nbsp;with&nbsp;some&nbsp;but&nbsp;not&nbsp;all&nbsp;of&nbsp;the
&nbsp;<BR>
kernel&nbsp;source&nbsp;(SPARC,&nbsp;PowerPC,&nbsp;etc.),&nbsp;you'll&nbsp;see&nbsp;some&nbsp;of&nbsp;these&nbsp;files.&nbsp;As&nbsp;long&nbsp;&nbsp;<BR>
as&nbsp;they're&nbsp;not&nbsp;for&nbsp;your&nbsp;architecture,&nbsp;you're&nbsp;okay.&nbsp;
&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>
Preparation
&nbsp;<BR>

&nbsp;<BR>
As&nbsp;a&nbsp;final&nbsp;note,&nbsp;before&nbsp;we&nbsp;change&nbsp;(cd)&nbsp;into&nbsp;the&nbsp;kernel&nbsp;source&nbsp;directory&nbsp;and&nbsp;&nbsp;<BR>
start&nbsp;building&nbsp;our&nbsp;new&nbsp;kernel,&nbsp;let's&nbsp;check&nbsp;some&nbsp;links
&nbsp;<BR>
that&nbsp;are&nbsp;needed.&nbsp;In&nbsp;your&nbsp;/usr/include&nbsp;directory,&nbsp;make&nbsp;sure&nbsp;you&nbsp;have&nbsp;the&nbsp;&nbsp;<BR>
following&nbsp;soft&nbsp;links:&nbsp;
&nbsp;<BR>

&nbsp;<BR>
asm&nbsp;-&nbsp;/usr/src/linux/include/asm
&nbsp;<BR>
linux&nbsp;-&nbsp;/usr/src/linux/include/linux
&nbsp;<BR>
scsi&nbsp;-&nbsp;/usr/src/linux/include/scsi
&nbsp;<BR>

&nbsp;<BR>
Now,&nbsp;you&nbsp;see&nbsp;another&nbsp;reason&nbsp;to&nbsp;standardize&nbsp;the&nbsp;location&nbsp;of&nbsp;the&nbsp;kernel.&nbsp;If&nbsp;you&nbsp;&nbsp;<BR>
don't&nbsp;put&nbsp;the&nbsp;latest&nbsp;kernel&nbsp;you&nbsp;wish&nbsp;to&nbsp;install&nbsp;in
&nbsp;<BR>
/usr/src/linux&nbsp;(via&nbsp;a&nbsp;link),&nbsp;the&nbsp;above&nbsp;links&nbsp;will&nbsp;not&nbsp;reach&nbsp;their&nbsp;intended&nbsp;&nbsp;<BR>
target&nbsp;(dangling&nbsp;links),&nbsp;and&nbsp;the&nbsp;kernel&nbsp;may&nbsp;fail&nbsp;to&nbsp;compile.&nbsp;
&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>
How&nbsp;to&nbsp;proceed
&nbsp;<BR>

&nbsp;<BR>
Once&nbsp;everything&nbsp;else&nbsp;is&nbsp;set&nbsp;up,&nbsp;change&nbsp;directories&nbsp;into&nbsp;/usr/src/linux.&nbsp;&nbsp;<BR>
Although&nbsp;you&nbsp;may&nbsp;want&nbsp;to&nbsp;stop&nbsp;off&nbsp;and&nbsp;peruse&nbsp;some&nbsp;of&nbsp;the
&nbsp;<BR>
documentation&nbsp;in&nbsp;the&nbsp;Documentation&nbsp;directory,&nbsp;particularly&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;&nbsp;<BR>
special&nbsp;hardware&nbsp;needs.&nbsp;Also,&nbsp;several&nbsp;of&nbsp;the&nbsp;CD-ROM
&nbsp;<BR>
drivers&nbsp;need&nbsp;to&nbsp;be&nbsp;built&nbsp;with&nbsp;customized&nbsp;settings.&nbsp;While&nbsp;they&nbsp;usually&nbsp;work&nbsp;as&nbsp;&nbsp;<BR>
is,&nbsp;these&nbsp;drivers&nbsp;may&nbsp;give&nbsp;warning&nbsp;messages&nbsp;when
&nbsp;<BR>
loaded.&nbsp;If&nbsp;this&nbsp;doesn't&nbsp;bother&nbsp;you&nbsp;and&nbsp;they&nbsp;work&nbsp;as&nbsp;they&nbsp;should,&nbsp;don't&nbsp;worry.&nbsp;&nbsp;<BR>
Otherwise,&nbsp;read&nbsp;the&nbsp;appropriate&nbsp;.txt,&nbsp;.h&nbsp;(header)&nbsp;files
&nbsp;<BR>
and&nbsp;.c&nbsp;(c&nbsp;code)&nbsp;files.&nbsp;For&nbsp;the&nbsp;most&nbsp;part,&nbsp;I&nbsp;have&nbsp;found&nbsp;them&nbsp;to&nbsp;be&nbsp;well&nbsp;&nbsp;<BR>
commented&nbsp;and&nbsp;easy&nbsp;to&nbsp;configure.&nbsp;If&nbsp;you&nbsp;don't&nbsp;feel&nbsp;brave,
&nbsp;<BR>
you&nbsp;don't&nbsp;have&nbsp;to&nbsp;do&nbsp;it.&nbsp;Just&nbsp;remember&nbsp;you&nbsp;can&nbsp;always&nbsp;restore&nbsp;the&nbsp;original&nbsp;&nbsp;<BR>
file&nbsp;by&nbsp;unpacking&nbsp;the&nbsp;gzipped&nbsp;tar&nbsp;file&nbsp;(or&nbsp;reinstalling&nbsp;the
&nbsp;<BR>
.rpm&nbsp;files)&nbsp;again.&nbsp;
&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>
Beginning&nbsp;to&nbsp;Compile
&nbsp;<BR>

&nbsp;<BR>
The&nbsp;first&nbsp;command&nbsp;I&nbsp;recommend&nbsp;you&nbsp;issue&nbsp;is:&nbsp;
&nbsp;<BR>

&nbsp;<BR>
make&nbsp;mrproper
&nbsp;<BR>

&nbsp;<BR>
While&nbsp;this&nbsp;command&nbsp;is&nbsp;not&nbsp;necessary&nbsp;when&nbsp;the&nbsp;kernel&nbsp;source&nbsp;is&nbsp;in&nbsp;pristine&nbsp;&nbsp;<BR>
condition,&nbsp;it&nbsp;is&nbsp;a&nbsp;good&nbsp;habit&nbsp;to&nbsp;cultivate.&nbsp;This&nbsp;command
&nbsp;<BR>
ensures&nbsp;that&nbsp;old&nbsp;object&nbsp;files&nbsp;are&nbsp;not&nbsp;littering&nbsp;the&nbsp;source&nbsp;tree&nbsp;and&nbsp;are&nbsp;not&nbsp;&nbsp;<BR>
used&nbsp;or&nbsp;in&nbsp;the&nbsp;way.&nbsp;
&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>
Configuring&nbsp;the&nbsp;Kernel
&nbsp;<BR>

&nbsp;<BR>
Now,&nbsp;you're&nbsp;ready&nbsp;to&nbsp;configure&nbsp;the&nbsp;kernel.&nbsp;Before&nbsp;starting,&nbsp;you'll&nbsp;need&nbsp;to&nbsp;&nbsp;<BR>
understand&nbsp;a&nbsp;little&nbsp;about&nbsp;modules.&nbsp;Think&nbsp;of&nbsp;a&nbsp;module&nbsp;as
&nbsp;<BR>
something&nbsp;you&nbsp;can&nbsp;plug&nbsp;into&nbsp;the&nbsp;kernel&nbsp;for&nbsp;a&nbsp;special&nbsp;purpose.&nbsp;If&nbsp;you&nbsp;have&nbsp;a&nbsp;&nbsp;<BR>
small&nbsp;network&nbsp;at&nbsp;home&nbsp;and&nbsp;sometimes&nbsp;want&nbsp;to&nbsp;use&nbsp;it
&nbsp;<BR>
(but&nbsp;not&nbsp;always),&nbsp;maybe&nbsp;you'll&nbsp;want&nbsp;to&nbsp;compile&nbsp;your&nbsp;Ethernet&nbsp;card&nbsp;as&nbsp;a&nbsp;&nbsp;<BR>
module.&nbsp;To&nbsp;use&nbsp;the&nbsp;module,&nbsp;the&nbsp;machine&nbsp;must&nbsp;be&nbsp;running
&nbsp;<BR>
and&nbsp;have&nbsp;access&nbsp;to&nbsp;the&nbsp;/lib/modules&nbsp;This&nbsp;means&nbsp;that&nbsp;the&nbsp;drive&nbsp;(IDE,&nbsp;SCSI,&nbsp;&nbsp;<BR>
etc.,&nbsp;but&nbsp;could&nbsp;be&nbsp;an&nbsp;ethernet&nbsp;card&nbsp;in&nbsp;the&nbsp;case&nbsp;of&nbsp;nfs),
&nbsp;<BR>
the&nbsp;file&nbsp;system&nbsp;(normally&nbsp;ext2&nbsp;but&nbsp;could&nbsp;be&nbsp;nfs)&nbsp;and&nbsp;the&nbsp;kernel&nbsp;type&nbsp;&nbsp;<BR>
(hopefully&nbsp;elf)&nbsp;must&nbsp;be&nbsp;compiled&nbsp;in&nbsp;and&nbsp;cannot&nbsp;be&nbsp;modules.
&nbsp;<BR>
Modules&nbsp;aren't&nbsp;available&nbsp;until&nbsp;the&nbsp;kernel&nbsp;is&nbsp;loaded,&nbsp;the&nbsp;drive&nbsp;(or&nbsp;network)&nbsp;&nbsp;<BR>
accessed,&nbsp;and&nbsp;the&nbsp;file&nbsp;system&nbsp;mounted.&nbsp;These&nbsp;files&nbsp;must
&nbsp;<BR>
be&nbsp;compiled&nbsp;into&nbsp;the&nbsp;kernel&nbsp;or&nbsp;it&nbsp;will&nbsp;not&nbsp;be&nbsp;able&nbsp;to&nbsp;mount&nbsp;the&nbsp;root&nbsp;&nbsp;<BR>
partition.&nbsp;If&nbsp;you're&nbsp;mounting&nbsp;the&nbsp;root&nbsp;partition&nbsp;over&nbsp;the&nbsp;network,
&nbsp;<BR>
you'll&nbsp;need&nbsp;the&nbsp;network&nbsp;file&nbsp;system&nbsp;module,&nbsp;and&nbsp;your&nbsp;Ethernet&nbsp;card&nbsp;compiled.&nbsp;&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>
Why&nbsp;use&nbsp;modules?&nbsp;Modules&nbsp;make&nbsp;the&nbsp;kernel&nbsp;smaller.&nbsp;This&nbsp;reduces&nbsp;the&nbsp;amount&nbsp;of&nbsp;&nbsp;<BR>
protected&nbsp;space&nbsp;never&nbsp;given&nbsp;up&nbsp;by&nbsp;the&nbsp;kernel.
&nbsp;<BR>
Modules&nbsp;load&nbsp;and&nbsp;unload&nbsp;and&nbsp;that&nbsp;memory&nbsp;can&nbsp;be&nbsp;reallocated.&nbsp;If&nbsp;you&nbsp;use&nbsp;a&nbsp;&nbsp;<BR>
module&nbsp;more&nbsp;than&nbsp;about&nbsp;90%&nbsp;of&nbsp;the&nbsp;time&nbsp;the&nbsp;machine
&nbsp;<BR>
is&nbsp;up,&nbsp;compile&nbsp;it.&nbsp;Using&nbsp;a&nbsp;module&nbsp;in&nbsp;this&nbsp;case&nbsp;can&nbsp;be&nbsp;wasteful&nbsp;of&nbsp;memory,&nbsp;&nbsp;<BR>
because&nbsp;while&nbsp;the&nbsp;module&nbsp;takes&nbsp;up&nbsp;the&nbsp;same&nbsp;amount&nbsp;of
&nbsp;<BR>
memory&nbsp;as&nbsp;if&nbsp;it&nbsp;were&nbsp;compiled,&nbsp;the&nbsp;kernel&nbsp;needs&nbsp;a&nbsp;little&nbsp;more&nbsp;code&nbsp;to&nbsp;have&nbsp;a&nbsp;&nbsp;<BR>
hook&nbsp;for&nbsp;the&nbsp;module.&nbsp;Remember,&nbsp;the&nbsp;kernel&nbsp;runs&nbsp;in
&nbsp;<BR>
protected&nbsp;space,&nbsp;but&nbsp;the&nbsp;modules&nbsp;don't.&nbsp;That&nbsp;said,&nbsp;I&nbsp;don't&nbsp;often&nbsp;follow&nbsp;my&nbsp;&nbsp;<BR>
own&nbsp;advice.&nbsp;I&nbsp;compile&nbsp;in:&nbsp;ext2,&nbsp;IDE&nbsp;and&nbsp;elf&nbsp;support&nbsp;only.
&nbsp;<BR>
While&nbsp;I&nbsp;use&nbsp;an&nbsp;Ethernet&nbsp;card&nbsp;almost&nbsp;all&nbsp;the&nbsp;time,&nbsp;I&nbsp;compile&nbsp;everything&nbsp;else&nbsp;&nbsp;<BR>
as&nbsp;modules:&nbsp;a.out,&nbsp;java,&nbsp;floppy,&nbsp;iso9660,&nbsp;msdos,&nbsp;minix,
&nbsp;<BR>
vfat,&nbsp;smb,&nbsp;nfs,&nbsp;smc-ultra&nbsp;(Ethernet&nbsp;card),&nbsp;serial,&nbsp;printer,&nbsp;sound,&nbsp;ppp,&nbsp;etc.&nbsp;&nbsp;<BR>
Many&nbsp;of&nbsp;these&nbsp;only&nbsp;run&nbsp;for&nbsp;a&nbsp;few&nbsp;minutes&nbsp;at&nbsp;a&nbsp;time&nbsp;here
&nbsp;<BR>
and&nbsp;there.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
The&nbsp;next&nbsp;step&nbsp;is&nbsp;to&nbsp;configure&nbsp;the&nbsp;kernel.&nbsp;Here&nbsp;we&nbsp;have&nbsp;three&nbsp;choices--while&nbsp;&nbsp;<BR>
all&nbsp;do&nbsp;the&nbsp;same&nbsp;thing,&nbsp;I&nbsp;recommend&nbsp;using&nbsp;one&nbsp;of&nbsp;the
&nbsp;<BR>
graphical&nbsp;methods.&nbsp;The&nbsp;old&nbsp;way&nbsp;was&nbsp;to&nbsp;simply&nbsp;type:&nbsp;make&nbsp;config.&nbsp;This&nbsp;begins&nbsp;a&nbsp;&nbsp;<BR>
long&nbsp;series&nbsp;of&nbsp;questions.&nbsp;However,&nbsp;if&nbsp;you
&nbsp;<BR>
make&nbsp;a&nbsp;mistake,&nbsp;your&nbsp;only&nbsp;option&nbsp;is&nbsp;to&nbsp;press&nbsp;ctrl-C&nbsp;and&nbsp;begin&nbsp;again.&nbsp;You&nbsp;also&nbsp;&nbsp;<BR>
can't&nbsp;go&nbsp;back&nbsp;in&nbsp;the&nbsp;sequence,&nbsp;and&nbsp;some
&nbsp;<BR>
questions&nbsp;depend&nbsp;on&nbsp;previous&nbsp;answers.&nbsp;If&nbsp;for&nbsp;some&nbsp;reason&nbsp;you&nbsp;absolutely&nbsp;can't&nbsp;&nbsp;<BR>
use&nbsp;either&nbsp;of&nbsp;the&nbsp;graphical&nbsp;methods,&nbsp;be&nbsp;my&nbsp;guest.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
I&nbsp;recommend&nbsp;using&nbsp;either&nbsp;make&nbsp;menuconfig&nbsp;or&nbsp;make&nbsp;xconfig.&nbsp;In&nbsp;order&nbsp;to&nbsp;use&nbsp;&nbsp;<BR>
menuconfig,&nbsp;you&nbsp;must&nbsp;have&nbsp;installed&nbsp;the
&nbsp;<BR>
ncurses-dev&nbsp;and&nbsp;the&nbsp;tk4-dev&nbsp;libraries.&nbsp;If&nbsp;you&nbsp;didn't&nbsp;install&nbsp;them&nbsp;and&nbsp;you&nbsp;&nbsp;<BR>
don't&nbsp;want&nbsp;to&nbsp;use&nbsp;the&nbsp;next&nbsp;method,&nbsp;I&nbsp;highly&nbsp;recommend
&nbsp;<BR>
that&nbsp;you&nbsp;install&nbsp;them&nbsp;now.&nbsp;You&nbsp;can&nbsp;always&nbsp;uninstall&nbsp;them&nbsp;later.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
To&nbsp;run&nbsp;make&nbsp;xconfig,&nbsp;you&nbsp;must&nbsp;install&nbsp;and&nbsp;configure&nbsp;X.&nbsp;Since&nbsp;X&nbsp;is&nbsp;such&nbsp;a&nbsp;&nbsp;<BR>
memory&nbsp;hog,&nbsp;I&nbsp;install,&nbsp;configure&nbsp;and&nbsp;startx&nbsp;only&nbsp;for
&nbsp;<BR>
this&nbsp;portion&nbsp;of&nbsp;the&nbsp;process,&nbsp;going&nbsp;back&nbsp;to&nbsp;a&nbsp;console&nbsp;while&nbsp;the&nbsp;kernel&nbsp;&nbsp;<BR>
compiles&nbsp;so&nbsp;it&nbsp;can&nbsp;have&nbsp;all&nbsp;the&nbsp;memory&nbsp;it&nbsp;needs.&nbsp;The&nbsp;xconfig
&nbsp;<BR>
menu&nbsp;is,&nbsp;in&nbsp;my&nbsp;opinion,&nbsp;the&nbsp;best&nbsp;and&nbsp;easiest&nbsp;way&nbsp;to&nbsp;configure&nbsp;the&nbsp;kernel.&nbsp;&nbsp;<BR>
Under&nbsp;menuconfig,&nbsp;if&nbsp;you&nbsp;disable&nbsp;an&nbsp;option,&nbsp;any
&nbsp;<BR>
subordinate&nbsp;options&nbsp;are&nbsp;not&nbsp;shown.&nbsp;Under&nbsp;xconfig,&nbsp;if&nbsp;you&nbsp;disable&nbsp;an&nbsp;option,&nbsp;&nbsp;<BR>
subordinate&nbsp;options&nbsp;still&nbsp;show,&nbsp;they&nbsp;are&nbsp;just&nbsp;greyed&nbsp;out.
&nbsp;<BR>
I&nbsp;like&nbsp;this&nbsp;because&nbsp;I&nbsp;can&nbsp;see&nbsp;what's&nbsp;been&nbsp;added&nbsp;since&nbsp;the&nbsp;last&nbsp;kernel.&nbsp;I&nbsp;may&nbsp;&nbsp;<BR>
want&nbsp;to&nbsp;enable&nbsp;an&nbsp;option&nbsp;to&nbsp;get&nbsp;one&nbsp;of&nbsp;the&nbsp;new
&nbsp;<BR>
sub-options&nbsp;in&nbsp;order&nbsp;to&nbsp;to&nbsp;experiment&nbsp;with&nbsp;it.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
I'm&nbsp;going&nbsp;to&nbsp;take&nbsp;some&nbsp;space&nbsp;here&nbsp;to&nbsp;describe&nbsp;the&nbsp;sections&nbsp;in&nbsp;the&nbsp;kernel&nbsp;&nbsp;<BR>
configuration&nbsp;and&nbsp;tell&nbsp;you&nbsp;some&nbsp;of&nbsp;the&nbsp;things&nbsp;I've
&nbsp;<BR>
discovered--mostly&nbsp;the&nbsp;hard&nbsp;way.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
The&nbsp;first&nbsp;section&nbsp;is&nbsp;the&nbsp;code-maturity-level&nbsp;option.&nbsp;The&nbsp;only&nbsp;question&nbsp;is&nbsp;&nbsp;<BR>
whether&nbsp;you&nbsp;want&nbsp;to&nbsp;use&nbsp;developmental&nbsp;drivers&nbsp;and&nbsp;code.
&nbsp;<BR>
You&nbsp;may&nbsp;not&nbsp;have&nbsp;a&nbsp;choice&nbsp;if&nbsp;you&nbsp;have&nbsp;some&nbsp;bleeding&nbsp;edge&nbsp;hardware.&nbsp;If&nbsp;you&nbsp;&nbsp;<BR>
choose&nbsp;``no'',&nbsp;the&nbsp;experimental&nbsp;code&nbsp;is&nbsp;greyed&nbsp;out&nbsp;or
&nbsp;<BR>
not&nbsp;shown.&nbsp;If&nbsp;you&nbsp;use&nbsp;this&nbsp;kernel&nbsp;for&nbsp;commercial&nbsp;production&nbsp;purposes,&nbsp;you'll&nbsp;&nbsp;<BR>
probably&nbsp;want&nbsp;to&nbsp;choose&nbsp;``no''.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
The&nbsp;second&nbsp;section&nbsp;concerns&nbsp;modules.&nbsp;If&nbsp;you&nbsp;want&nbsp;modules,&nbsp;choose&nbsp;``yes''&nbsp;for&nbsp;&nbsp;<BR>
questions&nbsp;1&nbsp;and&nbsp;3.&nbsp;If&nbsp;you&nbsp;want&nbsp;to&nbsp;use&nbsp;proprietary
&nbsp;<BR>
modules&nbsp;that&nbsp;come&nbsp;with&nbsp;certain&nbsp;distributions,&nbsp;such&nbsp;as&nbsp;Caldera's&nbsp;OpenLinux&nbsp;for&nbsp;&nbsp;<BR>
their&nbsp;Netware&nbsp;support,&nbsp;also&nbsp;answer&nbsp;``yes''&nbsp;to&nbsp;the
&nbsp;<BR>
second&nbsp;question&nbsp;since&nbsp;you&nbsp;won't&nbsp;be&nbsp;able&nbsp;to&nbsp;recompile&nbsp;the&nbsp;module.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
The&nbsp;third&nbsp;section&nbsp;is&nbsp;general&nbsp;setup.&nbsp;Do&nbsp;compile&nbsp;the&nbsp;kernel&nbsp;as&nbsp;ELF&nbsp;and&nbsp;compile&nbsp;&nbsp;<BR>
support&nbsp;for&nbsp;ELF&nbsp;binaries.&nbsp;Not&nbsp;compiling&nbsp;the&nbsp;proper
&nbsp;<BR>