00000063.htm

一份很好的linux入门资料

support&nbsp;is&nbsp;a&nbsp;definite&nbsp;``gotcha''.&nbsp;You'll&nbsp;get&nbsp;more&nbsp;efficient&nbsp;code&nbsp;compiling&nbsp;&nbsp;<BR>
the&nbsp;kernel&nbsp;for&nbsp;the&nbsp;machine's&nbsp;specific&nbsp;architecture&nbsp;(Pentium
&nbsp;<BR>
or&nbsp;486),&nbsp;but&nbsp;a&nbsp;386&nbsp;kernel&nbsp;will&nbsp;run&nbsp;in&nbsp;any&nbsp;32-bit&nbsp;Intel&nbsp;compatible&nbsp;clone;&nbsp;a&nbsp;&nbsp;<BR>
Pentium&nbsp;kernel&nbsp;won't.&nbsp;An&nbsp;emergency&nbsp;boot&nbsp;disk&nbsp;for&nbsp;a&nbsp;large
&nbsp;<BR>
number&nbsp;of&nbsp;computers&nbsp;(as&nbsp;well&nbsp;as&nbsp;distribution&nbsp;install&nbsp;disks)&nbsp;is&nbsp;best&nbsp;compiled&nbsp;&nbsp;<BR>
as&nbsp;a&nbsp;386.&nbsp;However,&nbsp;a&nbsp;386&nbsp;will&nbsp;not&nbsp;run&nbsp;a&nbsp;kernel&nbsp;compiled
&nbsp;<BR>
for&nbsp;a&nbsp;Pentium.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Next&nbsp;comes&nbsp;block&nbsp;devices--nothing&nbsp;special&nbsp;here.&nbsp;If&nbsp;your&nbsp;root&nbsp;device&nbsp;is&nbsp;on&nbsp;an&nbsp;&nbsp;<BR>
IDE&nbsp;drive,&nbsp;just&nbsp;make&nbsp;sure&nbsp;you&nbsp;compile&nbsp;it.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Then&nbsp;comes&nbsp;networking.&nbsp;For&nbsp;computers&nbsp;not&nbsp;connected&nbsp;to&nbsp;a&nbsp;network,&nbsp;you&nbsp;won't&nbsp;&nbsp;<BR>
need&nbsp;much&nbsp;here&nbsp;unless&nbsp;you&nbsp;plan&nbsp;to&nbsp;use&nbsp;one
&nbsp;<BR>
computer&nbsp;to&nbsp;dial-out&nbsp;while&nbsp;others&nbsp;connect&nbsp;through&nbsp;it.&nbsp;In&nbsp;this&nbsp;case,&nbsp;you'll&nbsp;&nbsp;<BR>
need&nbsp;to&nbsp;read&nbsp;up&nbsp;on&nbsp;such&nbsp;things&nbsp;as&nbsp;masquerading&nbsp;and&nbsp;follow
&nbsp;<BR>
the&nbsp;suggested&nbsp;guidelines.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
SCSI&nbsp;support&nbsp;is&nbsp;next,&nbsp;though&nbsp;why&nbsp;it&nbsp;doesn't&nbsp;directly&nbsp;follow&nbsp;block&nbsp;devices&nbsp;I&nbsp;&nbsp;<BR>
don't&nbsp;know.&nbsp;If&nbsp;your&nbsp;root&nbsp;partition&nbsp;is&nbsp;on&nbsp;a&nbsp;SCSI&nbsp;device,
&nbsp;<BR>
don't&nbsp;choose&nbsp;modules&nbsp;for&nbsp;SCSI&nbsp;support.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
SCSI&nbsp;low-level&nbsp;drivers&nbsp;follow&nbsp;general&nbsp;SCSI&nbsp;support.&nbsp;Again,&nbsp;modules&nbsp;only&nbsp;for&nbsp;&nbsp;<BR>
devices&nbsp;that&nbsp;don't&nbsp;contain&nbsp;the&nbsp;root&nbsp;partition.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
The&nbsp;next&nbsp;section&nbsp;takes&nbsp;us&nbsp;back&nbsp;to&nbsp;networking&nbsp;again.&nbsp;Expect&nbsp;to&nbsp;do&nbsp;a&nbsp;lot&nbsp;of&nbsp;&nbsp;<BR>
looking&nbsp;for&nbsp;your&nbsp;particular&nbsp;card&nbsp;here&nbsp;as&nbsp;well&nbsp;as&nbsp;some
&nbsp;<BR>
other&nbsp;support&nbsp;such&nbsp;as&nbsp;ppp,&nbsp;slip,&nbsp;etc.&nbsp;If&nbsp;you&nbsp;use&nbsp;nfs&nbsp;to&nbsp;mount&nbsp;your&nbsp;root&nbsp;&nbsp;<BR>
device,&nbsp;compile&nbsp;in&nbsp;Ethernet&nbsp;support.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
For&nbsp;those&nbsp;lucky&nbsp;enough&nbsp;to&nbsp;be&nbsp;needing&nbsp;ISDN&nbsp;support,&nbsp;the&nbsp;ISDN&nbsp;subsection&nbsp;will&nbsp;&nbsp;<BR>
need&nbsp;to&nbsp;be&nbsp;completed.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Older&nbsp;CD-ROMs&nbsp;may&nbsp;require&nbsp;support&nbsp;from&nbsp;the&nbsp;next&nbsp;section.&nbsp;If&nbsp;you're&nbsp;using&nbsp;a&nbsp;&nbsp;<BR>
SCSI&nbsp;or&nbsp;IDE&nbsp;CD-ROM,&nbsp;you&nbsp;can&nbsp;skip&nbsp;this&nbsp;one.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Next&nbsp;comes&nbsp;file&nbsp;systems.&nbsp;Again,&nbsp;compile&nbsp;what&nbsp;you&nbsp;need,&nbsp;in&nbsp;most&nbsp;cases&nbsp;ext2&nbsp;and&nbsp;&nbsp;<BR>
use&nbsp;modules&nbsp;for&nbsp;the&nbsp;rest.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Character&nbsp;devices&nbsp;are&nbsp;chosen&nbsp;next.&nbsp;Non-serial&nbsp;mice,&nbsp;like&nbsp;the&nbsp;PS/2&nbsp;mouse&nbsp;are&nbsp;&nbsp;<BR>
supported.&nbsp;Look&nbsp;on&nbsp;the&nbsp;bottom&nbsp;of&nbsp;your&nbsp;mouse.&nbsp;Many
&nbsp;<BR>
two-button&nbsp;mice&nbsp;are&nbsp;PS/2&nbsp;type,&nbsp;even&nbsp;though&nbsp;they&nbsp;look&nbsp;and&nbsp;connect&nbsp;like&nbsp;serial&nbsp;&nbsp;<BR>
mice.&nbsp;You'll&nbsp;almost&nbsp;certainly&nbsp;want&nbsp;serial&nbsp;support
&nbsp;<BR>
(generic)&nbsp;as&nbsp;a&nbsp;minimum.&nbsp;Generic&nbsp;printer&nbsp;support&nbsp;is&nbsp;also&nbsp;listed&nbsp;here.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
The&nbsp;penultimate&nbsp;section&nbsp;is&nbsp;often&nbsp;the&nbsp;most&nbsp;troubling:&nbsp;sound.&nbsp;Choose&nbsp;carefully&nbsp;&nbsp;<BR>
from&nbsp;the&nbsp;list&nbsp;and&nbsp;read&nbsp;the&nbsp;available&nbsp;help.&nbsp;Make&nbsp;sure
&nbsp;<BR>
you've&nbsp;chosen&nbsp;the&nbsp;correct&nbsp;I/O&nbsp;base&nbsp;and&nbsp;IRQs&nbsp;for&nbsp;your&nbsp;card.&nbsp;The&nbsp;MPU&nbsp;I/O&nbsp;base&nbsp;&nbsp;<BR>
for&nbsp;a&nbsp;SoundBlaster&nbsp;card&nbsp;is&nbsp;listed&nbsp;as&nbsp;0.&nbsp;This&nbsp;is
&nbsp;<BR>
normally&nbsp;330&nbsp;and&nbsp;your&nbsp;sound&nbsp;module&nbsp;will&nbsp;complain&nbsp;if&nbsp;this&nbsp;value&nbsp;is&nbsp;incorrect.&nbsp;&nbsp;<BR>
Don't&nbsp;worry.&nbsp;One&nbsp;of&nbsp;the&nbsp;nice&nbsp;things&nbsp;about&nbsp;modules&nbsp;is
&nbsp;<BR>
you&nbsp;can&nbsp;recompile&nbsp;and&nbsp;reinstall&nbsp;the&nbsp;modules&nbsp;as&nbsp;long&nbsp;as&nbsp;the&nbsp;kernel&nbsp;was&nbsp;&nbsp;<BR>
compiled&nbsp;with&nbsp;the&nbsp;hook.&nbsp;(Aren't&nbsp;modules&nbsp;great?).&nbsp;
&nbsp;<BR>

&nbsp;<BR>
The&nbsp;final&nbsp;section&nbsp;contains&nbsp;one&nbsp;question&nbsp;that&nbsp;should&nbsp;probably&nbsp;be&nbsp;answered&nbsp;as&nbsp;&nbsp;<BR>
``no,&nbsp;kernel&nbsp;hacking''.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Save&nbsp;your&nbsp;configuration&nbsp;and&nbsp;exit.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
I&nbsp;have,&nbsp;on&nbsp;several&nbsp;occasions,&nbsp;had&nbsp;trouble&nbsp;editing&nbsp;the&nbsp;numbers&nbsp;in&nbsp;menuconfig&nbsp;&nbsp;<BR>
or&nbsp;xconfig&nbsp;to&nbsp;values&nbsp;I&nbsp;knew&nbsp;were&nbsp;correct.&nbsp;For
&nbsp;<BR>
whatever&nbsp;reason,&nbsp;I&nbsp;couldn't&nbsp;change&nbsp;the&nbsp;number&nbsp;or&nbsp;config&nbsp;wouldn't&nbsp;accept&nbsp;the&nbsp;&nbsp;<BR>
number,&nbsp;telling&nbsp;me&nbsp;it&nbsp;was&nbsp;invalid.&nbsp;For&nbsp;example,
&nbsp;<BR>
changing&nbsp;the&nbsp;SoundBlaster&nbsp;IRQ&nbsp;from&nbsp;the&nbsp;config&nbsp;default&nbsp;of&nbsp;7&nbsp;to&nbsp;5,&nbsp;and&nbsp;the&nbsp;MPU&nbsp;&nbsp;<BR>
base&nbsp;I/O&nbsp;from&nbsp;0&nbsp;to&nbsp;300.&nbsp;If&nbsp;you&nbsp;experience&nbsp;this
&nbsp;<BR>
problem,&nbsp;but&nbsp;everything&nbsp;else&nbsp;went&nbsp;well,&nbsp;don't&nbsp;despair.&nbsp;The&nbsp;file&nbsp;you&nbsp;just&nbsp;&nbsp;<BR>
wrote&nbsp;when&nbsp;you&nbsp;did&nbsp;a&nbsp;``Save''&nbsp;and&nbsp;``Exit''&nbsp;is&nbsp;an&nbsp;editable&nbsp;text
&nbsp;<BR>
file.&nbsp;You&nbsp;may&nbsp;use&nbsp;your&nbsp;text&nbsp;editor&nbsp;of&nbsp;choice:&nbsp;Emacs,&nbsp;vi,&nbsp;CrispLite,&nbsp;joe,&nbsp;etc.&nbsp;&nbsp;<BR>
Your&nbsp;configuration&nbsp;file&nbsp;is&nbsp;in&nbsp;the&nbsp;/usr/src/linux&nbsp;directory
&nbsp;<BR>
and&nbsp;is&nbsp;called&nbsp;.config.&nbsp;The&nbsp;leading&nbsp;dot&nbsp;causes&nbsp;the&nbsp;file&nbsp;to&nbsp;be&nbsp;hidden&nbsp;during&nbsp;a&nbsp;&nbsp;<BR>
normal&nbsp;directory&nbsp;listing&nbsp;(ls),&nbsp;but&nbsp;it&nbsp;shows&nbsp;up&nbsp;when
&nbsp;<BR>
the&nbsp;-a&nbsp;option&nbsp;is&nbsp;specified.&nbsp;Just&nbsp;edit&nbsp;the&nbsp;numbers&nbsp;in&nbsp;this&nbsp;file&nbsp;that&nbsp;you&nbsp;had&nbsp;&nbsp;<BR>
trouble&nbsp;with&nbsp;in&nbsp;the&nbsp;configuration&nbsp;process.&nbsp;Next,&nbsp;type
&nbsp;<BR>
make&nbsp;dep&nbsp;to&nbsp;propagate&nbsp;your&nbsp;configurations&nbsp;from&nbsp;the&nbsp;.config&nbsp;file&nbsp;to&nbsp;the&nbsp;proper&nbsp;&nbsp;<BR>
subdirectories&nbsp;and&nbsp;to&nbsp;complete&nbsp;the&nbsp;setup.&nbsp;Finally,
&nbsp;<BR>
type&nbsp;make&nbsp;clean&nbsp;to&nbsp;prepare&nbsp;for&nbsp;the&nbsp;final&nbsp;kernel&nbsp;build.&nbsp;
&nbsp;<BR>

&nbsp;<BR>

&nbsp;<BR>

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

&nbsp;<BR>
We're&nbsp;now&nbsp;ready&nbsp;to&nbsp;begin&nbsp;building&nbsp;the&nbsp;kernel.&nbsp;There&nbsp;are&nbsp;several&nbsp;options&nbsp;for&nbsp;&nbsp;<BR>
accomplishing&nbsp;this&nbsp;task:&nbsp;
&nbsp;<BR>

&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make&nbsp;zImage:&nbsp;makes&nbsp;the&nbsp;basic,&nbsp;compressed&nbsp;kernel&nbsp;and&nbsp;leaves&nbsp;it&nbsp;in&nbsp;the&nbsp;&nbsp;<BR>
/usr/src/linux/arch/i386/boot&nbsp;directory&nbsp;as&nbsp;zImage.&nbsp;
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make&nbsp;zlilo:&nbsp;Copies&nbsp;the&nbsp;zImage&nbsp;to&nbsp;the&nbsp;root&nbsp;directory&nbsp;(unless&nbsp;you&nbsp;edited&nbsp;&nbsp;<BR>
the&nbsp;top-level&nbsp;Makefile)&nbsp;and&nbsp;runs&nbsp;LILO.&nbsp;If&nbsp;you
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;choose&nbsp;to&nbsp;use&nbsp;this&nbsp;option,&nbsp;you'll&nbsp;have&nbsp;to&nbsp;ensure&nbsp;that&nbsp;/etc/lilo.conf&nbsp;is&nbsp;&nbsp;<BR>
preconfigured.&nbsp;
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make&nbsp;zdisk:&nbsp;Writes&nbsp;zImage&nbsp;to&nbsp;a&nbsp;floppy&nbsp;disk&nbsp;in&nbsp;/dev/fd0&nbsp;(the&nbsp;first&nbsp;floppy&nbsp;&nbsp;<BR>
drive--the&nbsp;a:&nbsp;drive&nbsp;in&nbsp;DOS).&nbsp;You'll&nbsp;need&nbsp;the&nbsp;disk
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;in&nbsp;the&nbsp;drive&nbsp;before&nbsp;you&nbsp;start.&nbsp;You&nbsp;can&nbsp;accomplish&nbsp;the&nbsp;same&nbsp;thing&nbsp;by&nbsp;&nbsp;<BR>
running&nbsp;make&nbsp;zImage&nbsp;and&nbsp;copying&nbsp;the&nbsp;image&nbsp;to&nbsp;a
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;floppy&nbsp;disk&nbsp;cp&nbsp;/usr/src/linux/arch/i386/boot/zImage&nbsp;/dev/fd0&nbsp;Note&nbsp;that&nbsp;&nbsp;<BR>
you'll&nbsp;need&nbsp;to&nbsp;use&nbsp;a
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;high-density&nbsp;disk.&nbsp;The&nbsp;low&nbsp;density&nbsp;720k&nbsp;disks&nbsp;will&nbsp;reportedly&nbsp;not&nbsp;boot&nbsp;&nbsp;<BR>
the&nbsp;kernel.&nbsp;
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make&nbsp;boot:&nbsp;Works&nbsp;just&nbsp;the&nbsp;same&nbsp;as&nbsp;the&nbsp;zImage&nbsp;option.&nbsp;
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make&nbsp;bzImage:&nbsp;Used&nbsp;for&nbsp;big&nbsp;kernels&nbsp;and&nbsp;operates&nbsp;the&nbsp;same&nbsp;as&nbsp;zImage.&nbsp;You&nbsp;&nbsp;<BR>
will&nbsp;know&nbsp;if&nbsp;you&nbsp;need&nbsp;this&nbsp;option,&nbsp;because
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make&nbsp;will&nbsp;fail&nbsp;with&nbsp;a&nbsp;message&nbsp;that&nbsp;the&nbsp;image&nbsp;is&nbsp;too&nbsp;big.&nbsp;
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make&nbsp;bzdisk:&nbsp;Used&nbsp;for&nbsp;big&nbsp;kernels&nbsp;and&nbsp;operates&nbsp;the&nbsp;same&nbsp;as&nbsp;zdisk.&nbsp;You&nbsp;&nbsp;<BR>
will&nbsp;know&nbsp;if&nbsp;you&nbsp;need&nbsp;this&nbsp;option,&nbsp;because
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make&nbsp;will&nbsp;fail&nbsp;with&nbsp;a&nbsp;message&nbsp;that&nbsp;the&nbsp;image&nbsp;is&nbsp;too&nbsp;big.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Other&nbsp;make&nbsp;options&nbsp;are&nbsp;available,&nbsp;but&nbsp;are&nbsp;specialized,&nbsp;and&nbsp;are&nbsp;not&nbsp;covered&nbsp;&nbsp;<BR>
here.&nbsp;Also,&nbsp;if&nbsp;you&nbsp;need&nbsp;specialized&nbsp;support,&nbsp;such&nbsp;as&nbsp;for
&nbsp;<BR>
a&nbsp;RAM&nbsp;disk&nbsp;or&nbsp;SMP,&nbsp;read&nbsp;the&nbsp;appropriate&nbsp;documentation&nbsp;and&nbsp;edit&nbsp;the&nbsp;Makefile&nbsp;&nbsp;<BR>
in&nbsp;/usr/src/linux&nbsp;(also&nbsp;called&nbsp;the&nbsp;top-level&nbsp;Makefile)
&nbsp;<BR>
accordingly.&nbsp;Since&nbsp;all&nbsp;the&nbsp;options&nbsp;I&nbsp;discussed&nbsp;above&nbsp;are&nbsp;basically&nbsp;the&nbsp;same&nbsp;&nbsp;<BR>
as&nbsp;the&nbsp;zImage&nbsp;option,&nbsp;the&nbsp;rest&nbsp;of&nbsp;this&nbsp;article&nbsp;deals&nbsp;with
&nbsp;<BR>
make&nbsp;zImage--it&nbsp;is&nbsp;the&nbsp;easiest&nbsp;way&nbsp;to&nbsp;build&nbsp;the&nbsp;kernel.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
For&nbsp;those&nbsp;of&nbsp;you&nbsp;who&nbsp;wish&nbsp;to&nbsp;speed&nbsp;up&nbsp;the&nbsp;process&nbsp;and&nbsp;won't&nbsp;be&nbsp;doing&nbsp;other&nbsp;&nbsp;<BR>
things&nbsp;(such&nbsp;as&nbsp;configuring&nbsp;other&nbsp;applications),&nbsp;I
&nbsp;<BR>
suggest&nbsp;you&nbsp;look&nbsp;at&nbsp;the&nbsp;man&nbsp;page&nbsp;for&nbsp;make&nbsp;and&nbsp;try&nbsp;out&nbsp;the&nbsp;-j&nbsp;option&nbsp;(perhaps&nbsp;&nbsp;<BR>
with&nbsp;a&nbsp;limit&nbsp;like&nbsp;5)&nbsp;and&nbsp;also&nbsp;the&nbsp;-l&nbsp;option.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
If&nbsp;you&nbsp;chose&nbsp;modules&nbsp;during&nbsp;the&nbsp;configuration&nbsp;process,&nbsp;you'll&nbsp;want&nbsp;to&nbsp;issue&nbsp;&nbsp;<BR>
the&nbsp;commands:&nbsp;
&nbsp;<BR>

&nbsp;<BR>
make&nbsp;modules
&nbsp;<BR>
make&nbsp;modules_install
&nbsp;<BR>

&nbsp;<BR>
to&nbsp;put&nbsp;the&nbsp;modules&nbsp;in&nbsp;their&nbsp;default&nbsp;location&nbsp;of&nbsp;/lib/modules/2.0.x/,&nbsp;x&nbsp;being&nbsp;&nbsp;<BR>
the&nbsp;kernel&nbsp;minor&nbsp;number.&nbsp;If&nbsp;you&nbsp;already&nbsp;have&nbsp;this
&nbsp;<BR>
subdirectory&nbsp;and&nbsp;it&nbsp;has&nbsp;subdirectories&nbsp;such&nbsp;as&nbsp;block,&nbsp;net,&nbsp;scsi,&nbsp;cdrom,&nbsp;etc.,&nbsp;&nbsp;<BR>
you&nbsp;may&nbsp;want&nbsp;to&nbsp;remove&nbsp;2.0.x&nbsp;and&nbsp;everything&nbsp;below&nbsp;it
&nbsp;<BR>
unless&nbsp;you&nbsp;have&nbsp;some&nbsp;proprietary&nbsp;modules&nbsp;installed,&nbsp;in&nbsp;which&nbsp;case&nbsp;don't&nbsp;&nbsp;<BR>
remove&nbsp;it.&nbsp;When&nbsp;the&nbsp;modules&nbsp;are&nbsp;installed,&nbsp;the
&nbsp;<BR>
subdirectories&nbsp;are&nbsp;created&nbsp;and&nbsp;populated.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
You&nbsp;could&nbsp;just&nbsp;as&nbsp;easily&nbsp;have&nbsp;combined&nbsp;the&nbsp;last&nbsp;three&nbsp;commands:&nbsp;
&nbsp;<BR>

&nbsp;<BR>
make&nbsp;zImage;&nbsp;make&nbsp;modules;&nbsp;make&nbsp;modules_install
&nbsp;<BR>

&nbsp;<BR>
then&nbsp;returned&nbsp;after&nbsp;all&nbsp;the&nbsp;disk&nbsp;churning&nbsp;finished.&nbsp;The&nbsp;;&nbsp;(semicolon)&nbsp;&nbsp;<BR>
character&nbsp;separates&nbsp;sequential&nbsp;commands&nbsp;on&nbsp;one&nbsp;line&nbsp;and
&nbsp;<BR>
performs&nbsp;each&nbsp;command&nbsp;in&nbsp;order&nbsp;so&nbsp;that&nbsp;you&nbsp;don't&nbsp;have&nbsp;to&nbsp;wait&nbsp;around&nbsp;just&nbsp;to&nbsp;&nbsp;<BR>
issue&nbsp;the&nbsp;next&nbsp;command.&nbsp;
&nbsp;<BR>

&nbsp;<BR>
Once&nbsp;your&nbsp;kernel&nbsp;is&nbsp;built&nbsp;and&nbsp;your&nbsp;modules&nbsp;installed,&nbsp;we&nbsp;have&nbsp;a&nbsp;few&nbsp;more&nbsp;&nbsp;<BR>
items&nbsp;to&nbsp;take&nbsp;care&nbsp;of.&nbsp;First,&nbsp;copy&nbsp;your&nbsp;kernel&nbsp;to&nbsp;the&nbsp;root
&nbsp;<BR>
(or&nbsp;/boot/&nbsp;or&nbsp;/etc/,&nbsp;if&nbsp;you&nbsp;wish):&nbsp;
&nbsp;<BR>

&nbsp;<BR>
cp&nbsp;/usr/src/linux/arch/i386/boot/zImage&nbsp;/zImage
&nbsp;<BR>

&nbsp;<BR>
You&nbsp;should&nbsp;also&nbsp;copy&nbsp;the&nbsp;/usr/src/linux/System.map&nbsp;file&nbsp;to&nbsp;the&nbsp;same&nbsp;directory&nbsp;&nbsp;<BR>
as&nbsp;the&nbsp;kernel&nbsp;image.&nbsp;Then&nbsp;change&nbsp;(cd)&nbsp;to&nbsp;the&nbsp;/etc
&nbsp;<BR>
directory&nbsp;to&nbsp;configure&nbsp;LILO.&nbsp;This&nbsp;is&nbsp;a&nbsp;very&nbsp;important&nbsp;step.&nbsp;If&nbsp;we&nbsp;don't&nbsp;&nbsp;<BR>
install&nbsp;a&nbsp;pointer&nbsp;to&nbsp;the&nbsp;new&nbsp;kernel,&nbsp;it&nbsp;won't&nbsp;boot.&nbsp;Normally,
&nbsp;<BR>
an&nbsp;install&nbsp;kernel&nbsp;is&nbsp;called&nbsp;vmlinuz.&nbsp;Old-time&nbsp;Unix&nbsp;users&nbsp;will&nbsp;recognize&nbsp;the&nbsp;&nbsp;<BR>
construction&nbsp;of&nbsp;this&nbsp;name.&nbsp;The&nbsp;trailing&nbsp;``z''&nbsp;means&nbsp;the
&nbsp;<BR>
image&nbsp;is&nbsp;compressed.&nbsp;The&nbsp;``v''&nbsp;and&nbsp;``m''&nbsp;also&nbsp;have&nbsp;significance&nbsp;and&nbsp;mean&nbsp;&nbsp;<BR>
``virtual''&nbsp;and&nbsp;``sticky''&nbsp;respectively&nbsp;and&nbsp;pertain&nbsp;to
&nbsp;<BR>
memory&nbsp;and&nbsp;disk&nbsp;management.&nbsp;I&nbsp;suggest&nbsp;you&nbsp;leave&nbsp;the&nbsp;vmlinuz&nbsp;kernel&nbsp;in&nbsp;place,&nbsp;&nbsp;<BR>
since&nbsp;you&nbsp;know&nbsp;it&nbsp;works.&nbsp;
&nbsp;<BR>

&nbsp;<BR>