linux readme

1、來(lái)自linux-/README Linux kernel release 2.6.xx </>These are the release notes for Linux version 2.6.  Read them carefully,as they tell you what this is all about, explain how to install thekernel, and what to do if something goes wrong. WHAT IS LINUX? 

2、Linux is a clone of the operating system Unix, written from scratch by  Linus Torvalds with assistance from a loosely-knit team of hackers across  the Net. It aims towards POSIX and Single UNIX Specification compliance.  It has all the features you would expect in a modern fully-fledg

3、ed Unix,  including true multitasking, virtual memory, shared libraries, demand  loading, shared copy-on-write executables, proper memory management,  and multistack networking including IPv4 and IPv6.  It is distributed under the GNU General Public License - see the  accomp

4、anying COPYING file for more details. ON WHAT HARDWARE DOES IT RUN?在什么機(jī)器上可以跑？  Although originally developed first for 32-bit x86-based PCs (386 or higher),  today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and  UltraSPARC, Motorola 68000, PowerPC, PowerPC64, A

5、RM, Hitachi SuperH, Cell,  IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,  Xtensa, AVR32 and Renesas M32R architectures.  Linux is easily portable(方便的) to most general-purpose 32- or 64-bit architectures  as long as they have a paged memory management u

6、nit (PMMU) and a port of the  GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has  also been ported to a number of architectures without a PMMU, although  functionality is then obviously somewhat（有點(diǎn)） limited.  Linux has also been ported to itself. You can n

7、ow run the kernel as a  userspace application - this is called UserMode Linux (UML).    linux很容易就可以移植到32或者64位的機(jī)器上，只要它們有內(nèi)存管理單元(PMMU)和一個(gè)GNU C編譯工具。  linux也可以移植到一些沒(méi)有PMMU的機(jī)器上，雖然功能上有點(diǎn)限制。linux也可以移植到自身。你現(xiàn)在就可以  將內(nèi)核作為一個(gè)用戶空間的應(yīng)用程序（UML）。  DOCUMENTATION: - There is a l

8、ot of documentation available both in electronic form 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 Documen

9、tation   Project) books.  This README is not meant to be documentation on the   system: there are much better sources available.      這個(gè)文件夾下面包括了許多有用多文件，來(lái)自網(wǎng)絡(luò)和書(shū)的電子版，還有l(wèi)inux和一般性u(píng)nix的問(wèn)題。   我推薦去看這個(gè)文件夾下面的那些linux FTP站點(diǎn)。此README在系統(tǒng)中并不意味著是完整的說(shuō)明，站點(diǎn)里面 

10、  有更加好的資源。 - There are various README files in the Documentation/ subdirectory:   these typically contain kernel-specific installation notes for some    drivers for example. See Documentation/00-INDEX for a list of what   is contained in each file. 

11、Please read the Changes file, as it   contains information about the problems, which may result by upgrading   your kernel.      在每個(gè)子目錄下面都有README文件，包含來(lái)內(nèi)核安裝的提示，比如某些驅(qū)動(dòng)?？匆幌隆癉ocumentation/00-INDEX”   這個(gè)子目錄，里面列出來(lái)每個(gè)文件。請(qǐng)讀“Changs”這個(gè)文件，里面包含了一些難點(diǎn)信息，可能要導(dǎo)致你內(nèi)核的升級(jí)

12、。    - The Documentation/DocBook/ subdirectory contains several guides for   kernel developers and users.  These guides can be rendered in a   number of formats:  PostScript (.ps), PDF, HTML, & man-pages, among others.   After installation,

13、"make psdocs", "make pdfdocs", "make htmldocs",   or "make mandocs" will render the documentation in the requested format.      在“Documentation/DocBook/”這個(gè)子目錄下包含了內(nèi)核開(kāi)發(fā)者和使用者的一些向?qū)??？梢宰鞒?ps、PDF、   HTML等格式，用命令"make psdocs

14、"、“make pdfdocs”、"make htmldocs"或者“make mandocs”。   INSTALLING the kernel source: - If you install the full sources, put the kernel tarball in a   directory where you have permissions (eg. your home directory) and   unpack it:     

15、; 如果你想安裝源代碼，請(qǐng)安裝tar打包工具，然后用以下命令：        gzip -cd linux-2.6.XX.tar.gz | tar xvf -   or        bzip2 -dc linux-2.6.XX.tar.bz2 | tar xvf -   Replace "XX" with the version number of the latest kernel.   &#

16、160;  請(qǐng)用“XX”代替最近內(nèi)核的版本號(hào)。   Do NOT use the /usr/src/linux area! This area has a (usually   incomplete) set of kernel headers that are used by the library header   files.  They should match the library, and not get messed up by   whatever the kernel-du-

17、jour happens to be.      不要使用“/usr/src/linux”作為目錄，因?yàn)檫@個(gè)是內(nèi)核庫(kù)頭文件的目錄。 - You can also upgrade between 2.6.xx releases by patching.  Patches are   distributed in the traditional gzip and the newer bzip2 format.  To   install by patching, get all the n

18、ewer patch files, enter the   top level directory of the kernel source (linux-2.6.xx) and execute:      你可以通過(guò)patch升級(jí)你的發(fā)行版。Patches一般都是用gzip和bzip2打包的。為了安裝補(bǔ)丁，   要得到所有新的patch文件，然后進(jìn)入內(nèi)核源代碼的頂級(jí)目錄，使用以下命令：        gzip -cd ./patch-2.6.xx.gz

19、| patch -p1   or        bzip2 -dc ./patch-2.6.xx.bz2 | patch -p1   (repeat xx for all versions bigger than the version of your current   source tree, _in_order_) and you should be ok.  You may want to remove   the backup file

20、s (xxx or xxx.orig), and make sure that there are no   failed patches (xxx# or xxx.rej). If there are, either you or me has   made a mistake.      （打完補(bǔ)丁后，“xx”會(huì)替代當(dāng)前源代碼樹(shù)的版本號(hào)），這樣就ok了。你可能還要將一些備份文件刪除掉，   (xxx or xxx.orig),確保沒(méi)有失敗的patches(xxx# or xxx.rej)。如

21、果有，不是你犯錯(cuò)了，就是我。   Unlike patches for the 2.6.x kernels, patches for the 2.6.x.y kernels   (also known as the -stable kernels) are not incremental but instead apply   directly to the base 2.6.x kernel.  Please read   Documentation/applying-patches.txt for m

22、ore information.      不像“2.6.x”的內(nèi)核補(bǔ)丁，“2.6.x.y”的內(nèi)核補(bǔ)丁不是遞增而是直接急于“2.6.x”內(nèi)核的。請(qǐng)閱讀“   Documentation/applying-patches.txt”文件，有更多信息。   Alternatively, the script patch-kernel can be used to automate this   process.  It determines the current kernel versio

23、n and applies any   patches found.      這個(gè)腳本“patch-kernel”被自動(dòng)地使用在這個(gè)過(guò)程中，決定當(dāng)前內(nèi)核版本，運(yùn)用在任何的補(bǔ)丁上。        linux/scripts/patch-kernel linux   The first argument in the command above is the location of the   kernel source.  P

24、atches are applied from the current directory, but   an alternative directory can be specified as the second argument.      上面那個(gè)放在內(nèi)核源代碼中。補(bǔ)丁們可以用于當(dāng)前目錄，而且可以選擇不同的目錄。 - If you are upgrading between releases using the stable series patches   (for example, patch

25、-2.6.xx.y), note that these "dot-releases" are   not incremental and must be applied to the 2.6.xx base tree. For   example, if your base kernel is 2.6.12 and you want to apply the   patch, you do not and indeed must not first apply the   2.

26、6.12.1 and patches. Similarly, if you are running kernel   version and want to jump to , you must first   reverse the patch (that is, patch -R) _before_ applying   the patch.   You can read more on this in Documentat

27、ion/applying-patches.txt - Make sure you have no stale .o files and dependencies lying around:        cd linux        make mrproper   You should now have the sources correctly installed.SOFTWARE REQUIREMENTS   Compi

28、ling and running the 2.6.xx kernels requires up-to-date   versions of various software packages.  Consult   Documentation/Changes for the minimum version numbers required   and how to get updates for these packages.  Beware that using   excessively o

29、ld versions of these packages can cause indirect   errors that are very difficult to track down, so don't assume that   you can just update packages when obvious problems arise during   build or operation.      我們編譯和運(yùn)行內(nèi)核時(shí)，需要一些軟件包，并且這些軟件包要符合內(nèi)核更新的版

30、本，否則會(huì)帶來(lái)   很難追蹤的錯(cuò)誤。BUILD directory for the kernel:為內(nèi)核建立目錄：   When compiling the kernel all output files will per default be   stored together with the kernel source code.   Using the option "make O=output/dir" allow you to specify an alternate &#

31、160; place for the output files (including .config).   Example:     kernel source code:    /usr/src/linux-2.6.N     build directory:        /home/name/build/kernel        我們編譯

32、內(nèi)核時(shí)，可以將輸出文件放在一起。   To configure and build the kernel use:   cd /usr/src/linux-2.6.N   make O=/home/name/build/kernel menuconfig   make O=/home/name/build/kernel   sudo make O=/home/name/build/kernel modules_install install   Please note: If

33、 the 'O=output/dir' option is used then it must be   used for all invocations of make.      注意：所有的“make”命令都要帶著“0=output/dir”。CONFIGURING the kernel:配置內(nèi)核：   Do not skip this step even if you are only upgrading one minor   version.  New co

34、nfiguration options are added in each release, and   odd problems will turn up if the configuration files are not set up   as expected.  If you want to carry your existing configuration to a   new version with minimal work, use "make oldconfig", which wil

35、l   only ask you for the answers to new questions.      不要跳過(guò)這個(gè)步驟，即使你僅僅只是升級(jí)一個(gè)小的版本。新的配置選項(xiàng)被增加到每個(gè)發(fā)行版中。   如果你想盡量用最小的工作量來(lái)配置，可以使用“use oldconfig”。 - Alternate configuration commands are:    "make config"      Plai

36、n text interface.                         簡(jiǎn)單的文本界面    "make menuconfig"  Text based color menus, radiolists & dialogs.            &#

37、160;          有顏色的文本菜單，按鈕列表和對(duì)話框    "make xconfig"     X windows (Qt) based configuration tool.                       圖形界面（QT） 

38、0;  "make gconfig"     X windows (Gtk) based configuration tool.                       圖形界面（GTK）    "make oldconfig"   Default all questions base

39、d on the contents of               your existing ./.config file and asking about               new config symbols.               會(huì)默認(rèn)一些基

40、本內(nèi)容，問(wèn)一些新的配置    "make silentoldconfig"               Like above, but avoids cluttering the screen               with questions already answered.    

41、60;          Additionally updates the dependencies.    "make defconfig"   Create a ./.config file by using the default               symbol values from either arch/$ARCH/defco

42、nfig               or arch/$ARCH/configs/$PLATFORM_defconfig,               depending on the architecture.    "make $PLATFORM_defconfig"     

43、0;        Create a ./.config file by using the default              symbol values from              arch/$ARCH/configs/$PLATFORM_defconfig.       

44、0;      Use "make help" to get a list of all available              platforms of your architecture.    "make allyesconfig"               Cre

45、ate a ./.config file by setting symbol               values to 'y' as much as possible.    "make allmodconfig"               Create a ./.config file by setti

46、ng symbol               values to 'm' as much as possible.    "make allnoconfig" Create a ./.config file by setting symbol               values to 'n'

47、; as much as possible.    "make randconfig"  Create a ./.config file by setting symbol               values to random values.   You can find more information on using the Linux kernel config tools 

48、60; in Documentation/kbuild/kconfig.txt.      你可以通過(guò)“Documentation/kbuild/kconfig.txt”得到更多信息。    NOTES on "make config":    - having unnecessary drivers will make the kernel bigger, and can      under some circumstances l

49、ead to problems: probing for a      nonexistent controller card may confuse your other controllers      沒(méi)有必要的驅(qū)動(dòng)會(huì)使內(nèi)核變大，在某些環(huán)境下可能會(huì)導(dǎo)致問(wèn)題：探測(cè)一個(gè)不存在的控制器卡可能會(huì)      拒絕你另外一些控制器    - compiling the kernel with "Processor type" set

50、 higher than 386      will result in a kernel that does NOT work on a 386.  The      kernel will detect this on bootup, and give up.      編譯內(nèi)核時(shí)，高于386的處理器在386的機(jī)器上無(wú)法工作。    - A kernel with math-emulation compiled in will st

51、ill 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 whether they    &

52、#160; have a math coprocessor or not.      就是說(shuō)如果內(nèi)核將數(shù)學(xué)模擬編譯進(jìn)去后，不管運(yùn)行在什么機(jī)器上，即使那個(gè)機(jī)器上有數(shù)學(xué)協(xié)處理器，      它都會(huì)進(jìn)行模擬。     - the "kernel hacking" configuration details usually result in a      bigger or slower kernel (or both),

53、 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  &#

54、160;       "development", "experimental", or "debugging" features.      像“kernel hacking”這樣的選項(xiàng)會(huì)導(dǎo)致內(nèi)核的不穩(wěn)定。因此最好不要將它們編譯進(jìn)內(nèi)核，比如有      "development", "experimental", or "de

55、bugging"特征的。COMPILING the kernel:編譯內(nèi)核： - Make sure you have at least gcc 3.2 available.   For more information, refer to Documentation/Changes.      最低gcc本版為3.2，可以參考“Documentation/Changes”文件   Please note that you can still run a.out user programs wi

56、th this kernel. - Do a "make" to create a compressed kernel image. It is also   possible to do "make install" if you have lilo installed to suit the   kernel makefiles, but you may want to check your particular lilo setup first.      你

57、可以使用“make”來(lái)創(chuàng)建壓縮內(nèi)核映像，也可以使用“make install”，不過(guò)要檢查一下是否安裝來(lái)lilo。   To do the actual install you have to be root, but none of the normal   build should require that. Don't take the name of root in vain. - If you configured any of the parts of the kernel as modules', you 

58、;  will also have to do "make modules_install".      如果你將內(nèi)核配置成了模塊，那么你得用“make modules_install”。 - Verbose kernel compile/build output:  - 編譯/建立的詳細(xì)輸出：   Normally the kernel build system runs in a fairly quiet mode (but not   totally

59、 silent).  However, sometimes you or other kernel developers need   to see compile, link, or other commands exactly as they are executed.   For this, use "verbose" build mode.  This is done by inserting   "V=1" in the "make" comma

60、nd.  E.g.:      一般來(lái)說(shuō)內(nèi)核建立步驟比較簡(jiǎn)單啦，然而，有些時(shí)候，需要學(xué)習(xí)一下編譯、鏈接和另外一些命令。    make V=1 all   To have the build system also tell the reason for the rebuild of each   target, use "V=2".  The default is "V=0". - Keep a backup ke

61、rnel 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.  Make sure you keep a   backup of the modules corresponding to that kernel, as well.

62、  If you   are installing a new kernel with the same version number as your   working kernel, make a backup of your modules directory before you   do a "make modules_install".   Alternatively, before compiling, use the kernel config option 

63、  "LOCALVERSION" to append a unique suffix to the regular kernel version.   LOCALVERSION can be set in the "General Setup" menu.      就是說(shuō)讓內(nèi)核編譯的模塊時(shí)，有個(gè)備份，如果你不備份，也可以使用“General Setup”菜單下面的   “LOCALVERSION”選項(xiàng)。 - In order to boot your n

64、ew kernel, you'll need to copy the kernel   image (e.g. ./linux/arch/i386/boot/bzImage after compilation)   to the place where your regular bootable kernel is found.       為了讓你的新內(nèi)核啟動(dòng)，要將內(nèi)核映像放在boot可以找得到的地方。 - Booting a kernel directly from a floppy

65、 without the assistance of a   bootloader such as LILO, is no longer supported.      我們不提倡用軟盤(pán)啟動(dòng)內(nèi)核在沒(méi)有bootloader“LILO”的情況下。   If you boot Linux from the hard drive, chances are you use LILO which   uses the kernel image as specified in the file /etc/li

66、lo.conf.  The   kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or   /boot/bzImage.  To use the new kernel, save a copy of the old image   and copy the new image over the old one.  Then, you MUST RERUN LILO   to update the loading

67、 map! If you don't, you won't be able to boot   the new kernel image.      如果用硬盤(pán)啟動(dòng)，你使用LILO，配置文件在“/etc/lilo.conf”，內(nèi)核映像在"/boot/"目錄下。   為了使用新的內(nèi)核，為舊的內(nèi)核保存一份拷貝，將新的內(nèi)核映像覆蓋舊的。然后重新運(yùn)行一下LILO，更新   加載的map!否則不能啟動(dòng)新的內(nèi)核映像。   Reinstalling LI

68、LO 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.      

69、; 下載后的LILO程序放在“/sbin/lilo”里，如果你將它的配置文件“/etc/lilo.conf”配置   成舊內(nèi)核啟動(dòng)，那么新內(nèi)核就無(wú)法工作了，可以查看LILO文檔獲得更多的信息。   After reinstalling LILO, you should be all set.  Shutdown the system,   reboot, and enjoy!      重新啟動(dòng)，即可進(jìn)入新內(nèi)核了！   If you ever need to cha

70、nge the default root device, video mode,   ramdisk size, etc.  in the kernel image, use the 'rdev' program (or   alternatively the LILO boot options when appropriate).  No need to   recompile the kernel to change these parameters.    

71、60;  如果你想改變內(nèi)核映像的根設(shè)備、視頻模式、虛擬盤(pán)的大小，可以使用"rdev"程序（或者在   LILO的選項(xiàng)中配置），不需要改變內(nèi)核參數(shù)重新編譯內(nèi)核。 - Reboot with the new kernel and enjoy. IF SOMETHING GOES WRONG:如果出錯(cuò)了： - If you have problems that seem to be due to kernel bugs, please check   the file MAINTAINERS to s

72、ee if there is a particular person associated   with the part of the kernel that you are having trouble with. If there   isn't anyone listed there, then the second best thing is to mail   them to me (), and possibly to any other 

73、0; relevant mailing-list or to the newsgroup. - In all bug-reports, *please* tell what kernel you are talking about,   how to duplicate the problem, and what your setup is (use your common   sense).  If the problem is new, tell me so, and if the problem is   o

74、ld, please try to tell me when 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:

75、 xxxxxxxx   ecx: xxxxxxxx   edx: xxxxxxxx    esi: xxxxxxxx   edi: xxxxxxxx   ebp: xxxxxxxx    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   hel