Linux Kernel Release 2.0.xx

zhaozj2021-02-16  136

THESE ARE The Release Notes for Linux Version 2.0. Read Them Carefully,

As the tell you what this is all about, explain how to install the

KERNEL, AND what to do if things wroes.

What is linux?

Linux is a unix clone Written from scratch by linus torvalds with

Assistance from a loosely-knit team of harkers across the net.

IT AIMS TOWARDS POSIX Compliance.

IT Has All The Features You Would EXPECT IN A MODERN FULLY-FLEDGED

UNIX, INCLUDING TRUE MULTITASKING, Virtual Memory, Shared Libraries,

Demand Loading, Shared Copy-On-Write Executables, Proper Memory

Management and tcp / ip networking.

IT IS Distributed Under The GNU General Public License - See T

Accompanying Copying File for more details.

On What Hardware Does It Run?

Linux Was First Developed for 386/486-Based PCS. Thays it Also

Runs on Dec Alphas, Sun Sparcs, M68000 Machines (Like Atari and Amiga),

MIPS AND POWERPC.

Documentation:

- There Is a Lot of Documentation Available Both in Electronic Form on ON

The Internet and in books, Both Linux-Specific and Pertaining to

General UNIX Questions. I'd Recommend Looking Into The Documentation

Subdirectories on Any Linux FTP Site for the LDP (Linux Documentation

Project) Books. This Readme is Not Meant to Be Documentation on The

System: There is much beetter Sources Available.

- There Are Various Readme in The Kernel Documentation / Subdirectory:

THESE TYPICLY Contain Kernel-Specific Installation Notes for Some

Drivers for example. See./documentation/00-index for a list of what

Is Contained in Each File.

Installing the kenel:

- IF you install the full sources, do a

CD / USR / SRC

Gzip -cd Linux-2.0.xx.tar.gz | TAR XFV -

TO GET IT All Put in place. Replace "xx" with the version number of thelatest kernel.

- you can also Upgrade Between 2.0.xx releases by patching. EACH

Patch That Is Released for 2.0.xx Contains Only Bugfixes. no

New Features Will Be Added to the Linux Kernel Until The 2.1.xx

DEVELOPMENT EFFORT Begins. To Install by Patching, Get All The

NEWER PATCH FILES AND DO

CD / USR / SRC

gzip -cd patchxx.gz | patch -p0

(REPEAT XX for All Versions Bigger Than The Version of Your Current

Source tree, _in_order_) and you shop be ok. You may want to remove

The Backup Files (xxx ~ or xxx.orig), And make Sure That the the the are no

Failed patches (xxx # or xxx.rej). if there is, Either you or me HAS

Made a mistake.

Alternatively, the script patch-kernel can be used to automate this

Process. It determines the current kernel version and applies any

Patches found.

CD / USR / SRC

Linux / scripts / patch-kernel

The Default Directory for the Kernel Source IS / USR / SRC / Linux, but BUT

Can Be Specified As The First Argument. Patches Are Applied from

The Current Directory, But An Alternative Directory Can Be Specified

As the second argument.

- Make Sure Your / usr / include / asm, / usr / include / linux, and / usr / include / SCSI

Directories Are Just Symlinks to the Kernel Sources:

CD / usr / include

RM-RF ASM Linux SCSI

LN -S / USR / SRC / Linux / include / ASM-I386 ASM

Ln -s / usr / src / linux / include / linux linux

LN -S / USR / SRC / Linux / include / SCSI SCSI

- Make Sure You Have No Stale .o Files and Dependencies Lying AROEND:

CD / USR / SRC / Linux

Make Mrproper

You Should Now Have The Sources Correctly Installed.

CONFIGURING THE KERNEL:

- Do a "make config" to configure the basic kernel. "make config"

Needs Bash To Work: IT Will Search for Bash In $ Bash, / BIN / BASH AND / BIN / SH (In That Order), SO Hopefully One of Those Is Correct.

- Alternate Configuration Commands Are:

"Make MenuConfig" Text Based Color Menus, Radiolists & Dialogs.

"make Xconfig" x Windows based configuration Tool.

Notes On "make config":

- Having Unnecessary Drivers Will Make The Kernel Bigger, And Can

Under Some Circumstances Lead to Problems: Probing for a

Nonexistent Controller Card May Confuse Your Other Controllers

- Compiling The Kernel with "Processor Type" set higher Than 386

Will Result in a kenergy this does not work on a 386. The

Kernel Will Detect this on bootup, and give up.

- a kernel with maath-emulation completed in Will Still Use the

Coprocessor if One is present: The Math Emulation Will Just

Never Get Used In That Case. The Kernel Will Be Slightly Larger,

But Will Work On Different Machines Regardless of Whather They

Have a Math Coprocessor or Not.

- The "kernel Hacking" Configuration Details Usually Result in A

Bigger or Slower Kernel (or Both), And Can Even Make the Kernel

Less Stable by Configuring Some Routines TO Actively Try To

Break Bad Code to Find Kernel Problems (kmalloc ()). Thus you

SHOULD PROBABLY ANSWER 'N' TO The Questions for a "Production"

Kernel.

- Check the top makefile for further site-dependent configuration. - DEPENDENT CONFIGURATION

DEFAULT SVGA Mode ETC.

- Finally, Do a "make DEP" to set up all the dependencies Correctly.

Compiling the kenel:

- Make Sure You Have GCC-2.6.3 or NEWER AVAILABLE. IT Seems Older GCC

Versions Can Have Problems Compiableing Newer Versions of Linux. if you

Upgrade your compiler, Remember to get the new binutils package TOO (for AS / LD / NM AND Company).

Do a "make zimage" to create a commitsed kernel image. if you want

To make a bootdisk (WITHOUT root filesystem or lilo), INSERT A FLOPPY

IN your a: drive, and do a "make zdisk". It is also Possible to do

"Make Zlilo" if you have lilo installed to suit the kernel makefiles,

But You May Want to Check your particular lilo setup first.

- if Your Keernel Is Too Large for "Make Zimage", Use "make bzimage"

INSTEAD.

- if you configured Any of the parts of the kernel as `` Modules', you

Will Have to do "make modules" followed by "make modules_install".

Read Documentation / Modules.txt for more information. For example,

An explanation of how to use the modules is included there.

- Keep A Backup Kernel Handy In Case Something Goes Wrong. this is

Especially True for The Development Releases, Since Each New Release

Contains New Code Which Has Not Been Debugged.

- in Order to boot your new kernel, You'll Need to Copy THE KERNEL

Image (Found IN / USR / SRC / Linux / Arch / I386 / Boot / Zimage After CompiLation)

To The Place WHERE YOUR REGULAR BOOTABLE KERNEL IS Found.

For Some, this is on a floppy disk, in which case you can "CP" CP

/ usr / src / linux / arch / i386 / boot / zimage / dev / fd0 "to make a bootable

FLOPPY. Note That as of Linux 2.0.0, a kernel copied to a 720k

Double-Density 3.5 "Floppy Disk No longer Boots. in this case,

IT IS Highly Recommended That You Install LILO ION YOUR

Double-density bootfloppy or switch to high-density floppies.

If you boot linux from the hard drive, chance y you us e

Uses the kernel image as specified in the file /etc/lilo.conf. Thekernel Image File IS Usually / VMLinuz, or / zimage, or / etc / zimage.

To use the new kernel, Copy the New Image over the old one (save a

Backup of the Original!). THEN, You Must Run Lilo To Update The

Loading map !! if you don't, you won't becomle to boot the new kernel

Image.

Reinstalling lilo is usually a matter of running / sbin / lilo.

You May wish to edit /etc/lilo.conf to specify an entry for your

Old kernel image (say, /vmlinux.old) in case the new one does not

Work. See the lilo docs for more information.

After Reinstalling Lilo, You Should Be All Set. Shutdown The System,

Reboot, and enjoy!

IF you Ever Need to change the default root device, Video Mode,

Ramdisk size, etc. in the kernel image, use the 'RDEV' Program (OR

Alternative above the lilo boot options when appropriate). No need to

Recompile The Kernel to Change these Parameters.

- Reboot with the new kernel and enjoy.

IF Something Goes WRONG:

- IF you have problems what seem to be due to kenel bugs, please check

The file maintainers to see reason there is a particular persected

With the part of the kenel That you are havning trouble with. if there

Isn't Anyone listed there, tell Mail

THEM to Me (Linus.torvalds@helsinki.fi), and Possibly to any other

Relevant mailing-list or to the news. The mailing-lists area

Useful Especial For SCSI and NetWorking Problems, AS I Can't Test

Either of those.

- in all bug-reports, * please * tell what kernel you are Talking About,

How to duplicate the problem, and what your setup is (use your commit

Sense). If The Problem is New, Tell Me So, Andi The Problem isold, please try to Tell me at you first noticed it.

- IF The Bug Results in a Message Like

UNABLE to Handle Kernel Paging Request At Address C0000010

OOPS: 0002

EIP: 0010: XXXXXXXX

EAX: xxxxxxxx EBX: XXXXXXX ECX: XXXXXXXE

ESI: XXXXXXX EDI: XXXXXXX EBP: XXXXXXXXXX

DS: xxxx es: xxxx fs: xxxx gs: xxxx

PID: XX, Process NR: XX

XX xx xx xx xx xx xx xx xx xx

Or Similar Kernel Debugging Information On Your Screen Or in Your

System log, please duplicate it * exactly *. The Dump May Look

INCOMPREHENSIBLE to you, But it does contain information That May

Help Debugging The Problem. The text Above the dump is also

Important: IT Tells Something About Why The Kernel Dumped Code (in

The Above Example It's Due To a Bad Kernel Pointer. More Information

ON MAKING SENSE OF THE DUMP IS in Documentation / OOPS-TRACING.TXT

- you can use the "ksymoops" program to make sense of the dump. Find

The C Sources Under The Scripts / Directory To Avoid Having To DO

The dump lookup by hand:

- in Debugging Dumps like the Above, IT Helps ENORMOUSLY IF you can

Look Up What The Eip Value Means. The Hex Value As Such Doesn't Help

Me OR Anybody Else Very Much: IT Will Depend On Your Particular

Kernel setup. What you shop do is take the hex value from the EIP

LINE (Ignore the "0010:"), And Look It Up in the Kernel Namelist To

See Which kernel function contains the offending address.

To Find Out the kernel function name, You'll Need to find the system

Binary associated with the kernel That Exhibited The Symptom. this is

The file 'linux / vmlinux'. To extract the namelist and match it against

The Eip from the Kernel Crash, DO:

NM VMLINUX | SORT | Less

This Will Give you a list of kernel addresses sorted in assending

Order, from which it is simple to find the function That Contains the

Offending address. Note That The Address Given by the Kernel

Debugging Messages Will Not Necessarily Match EXACTLY with THE

Function Addresses (In Fact, That Is Very Unlikely), SO you can't

Just 'grep' The List: The List Will, However, Give You the Starting

Point of Each Kernel Function, SO by looking for the function That

HAS a Starting Address Lower Than The One You Are Searching for But BUT

Is Followed by a function with a higher address you will find the one

You Want. in Fact, IT May Beh Good Idea To Include A Bit of

"Context" in Your Problem Report, Giving A Few Lines Around To

INTERESTINE.

IF you for some reason cannot do the above (you have a pre-compiled

Kernel Image Or Similar, Telling Me As Much About Your Setup AS

Possible Will Help.

- Alternately, you can use gdb on a running kernel. (read-only; I.e. You

Cannot Change Values ​​or Set Break Points.) To do this, first compile the

Kernel with -g; edit arch / i386 / makefile appropriately, The DO A "Make

". You'll Also need to enable config_proc_fs (VIA" make config ").

After You'Ve Rebooted with the new kernel, do "gdb vmlinux / proc / kcore".

You can now use all the us asseand to look up

Point where your system crashed is "l * 0xxxxxxxxx". (Replace the xxxes

WITH The EIP VALUE.)

GDB'ing a non-Running kernel currently fails Because GDB (WRONGLY)

Disregards The Starting Offset for Which The Kernel Is Compiled.

转载请注明原文地址:https://www.9cbs.com/read-8821.html

New Post(0)