00000004.htm

一份很好的linux入门资料

Memory:&nbsp;7000k/8192k&nbsp;available&nbsp;(496k&nbsp;kernel&nbsp;code,&nbsp;384k&nbsp;reserved,&nbsp;312k&nbsp;<BR>
data)&nbsp;<BR>
&nbsp;<BR>
7.3.&nbsp;核心没有编译&nbsp;<BR>
&nbsp;<BR>
如果它没有被编译，那麽可能是有个修补档失败了，或者是你从某个地方拿到的原始程&nbsp;<BR>
式码有问题。也有可能是因为你的&nbsp;gcc&nbsp;版本不正确或坏掉了。确定&nbsp;Linus&nbsp;在&nbsp;README&nbsp;<BR>
里所描述的符号链结都有正确建立。一般说来，如果核心没能编译，这表示在某些地方&nbsp;<BR>
有严重的错误。&nbsp;<BR>
&nbsp;<BR>
7.4.&nbsp;新版的核心似乎不能启动&nbsp;<BR>
&nbsp;<BR>
没有执行&nbsp;LILO&nbsp;，或是没有正确的配置它。有一次我曾经碰到的问题是出在配置档里，&nbsp;<BR>
我用了″&nbsp;root&nbsp;=&nbsp;/dev/hda&nbsp;″而不是″&nbsp;&nbsp;root&nbsp;=&nbsp;/dev/hda1″（这在刚开始时真的是&nbsp;<BR>
很讨厌，但是一旦你有了一个可以用的配置档，应该不需要去再去改变它）&nbsp;<BR>
&nbsp;<BR>
7.5.&nbsp;你忘了执行&nbsp;lilo&nbsp;，或系统根本不能启动&nbsp;<BR>
&nbsp;<BR>
噢！现在最好的办法是用磁片启动，并且准备另一张可以启动的磁片（像是”&nbsp;make&nbsp;<BR>
zdisk&nbsp;”时做的磁片）。你得知道你的根目录（&nbsp;/&nbsp;）所在的分割区以及它的格式（&nbsp;<BR>
second&nbsp;extended,&nbsp;minix&nbsp;等等）在下面的例子中，你也得知道你的&nbsp;/usr/src/linux&nbsp;<BR>
source&nbsp;tree&nbsp;在那个分割区，它的格式，以及它一般会挂在那儿。&nbsp;<BR>
&nbsp;<BR>
在这个例子中，&nbsp;根目录&nbsp;/&nbsp;是&nbsp;/dev/hda1&nbsp;，而持有&nbsp;/usr/src/linux&nbsp;的分割区是&nbsp;<BR>
/dev/hda3&nbsp;，&nbsp;一般会挂在&nbsp;/usr&nbsp;下。它们都是&nbsp;second&nbsp;extended&nbsp;档案系统。可以运作&nbsp;<BR>
的核心映像叫做&nbsp;zImage&nbsp;，放在&nbsp;/usr/src/linux&nbsp;底下。&nbsp;<BR>
&nbsp;<BR>
这个主意是这样的，假若有一个可以运作的核心映像叫做&nbsp;zImage&nbsp;在&nbsp;/usr/src/linux&nbsp;<BR>
下，可能可以把它用在新的磁片上。另外一个不一定会更好的变通办法（这跟你的系统&nbsp;<BR>
怎麽组成的有关）在说明这个例子之後会讨论到。&nbsp;<BR>
&nbsp;<BR>
首先，从&nbsp;boot/root&nbsp;磁片或者是&nbsp;rescue&nbsp;磁片开机，然後将持有可运作核心的分割区&nbsp;<BR>
挂上来：&nbsp;<BR>
&nbsp;<BR>
mkdir&nbsp;/mnt&nbsp;<BR>
mount&nbsp;-t&nbsp;ext2&nbsp;/dev/hda3&nbsp;/mnt&nbsp;<BR>
&nbsp;<BR>
如果&nbsp;mkdir&nbsp;指令显示该目录已经存在，忽略掉不必理会它。现在，cd&nbsp;到持有可运作核&nbsp;<BR>
心的地方（注意：&nbsp;/mnt&nbsp;+&nbsp;/usr/src/linux&nbsp;-&nbsp;/usr&nbsp;=&nbsp;/mnt/src/inux&nbsp;）。把一张格式&nbsp;<BR>
化过的磁片放进&nbsp;a:&nbsp;磁碟机，（确定不是你的&nbsp;boot/root&nbsp;磁片！），把映像档倾倒到&nbsp;<BR>
磁片里去，然後配置你的根目录分割区。&nbsp;<BR>
&nbsp;<BR>
cd&nbsp;/mnt/src/linux&nbsp;<BR>
dd&nbsp;if=zImage&nbsp;of=/dev/fd0&nbsp;<BR>
rdev&nbsp;/dev/fd0&nbsp;/dev/hda1&nbsp;<BR>
&nbsp;<BR>
cd&nbsp;到根目录&nbsp;/&nbsp;并且卸下标准&nbsp;/usr&nbsp;分割区：&nbsp;<BR>
&nbsp;<BR>
cd&nbsp;/&nbsp;<BR>
umount&nbsp;/mnt&nbsp;<BR>
&nbsp;<BR>
你现在应该可以从这张磁片正常的开机了。在这次开机後不要忘记执行&nbsp;lilo&nbsp;（或是其&nbsp;<BR>
它无论你曾经做错的什麽事）！&nbsp;<BR>
&nbsp;<BR>
如同前面曾经提过的，还有另外一种很普遍的变通方式。如果情况是你有一个可以运作&nbsp;<BR>
的核心在放在&nbsp;/&nbsp;（例如&nbsp;/vmlinuz&nbsp;），你也可以使用它。假定所有的条件都跟上面的&nbsp;<BR>
例子一样，而我的核心映像是&nbsp;/vmlinuz&nbsp;，只要对上面的例子做这些改变：&nbsp;<BR>
&nbsp;<BR>
把&nbsp;/dev/hda3&nbsp;改成&nbsp;/dev/hda1（&nbsp;/&nbsp;分割区），把&nbsp;/mnt/src/linux&nbsp;改成&nbsp;/mnt&nbsp;，并且&nbsp;<BR>
把&nbsp;if=zImage&nbsp;改成&nbsp;if=vmlinuz&nbsp;。至於前面有关注意如何推导出&nbsp;/mnt/src/linx&nbsp;的那&nbsp;<BR>
个部分可以忽略。&nbsp;<BR>
&nbsp;<BR>
7.6.&nbsp;系统表示”&nbsp;Warning:&nbsp;bdflush&nbsp;not&nbsp;running”&nbsp;<BR>
&nbsp;<BR>
这可以算是一个相当严重的问题。从&nbsp;1.0&nbsp;版以後的核心开始（我记不清楚确实的版本&nbsp;<BR>
了，但大概是在&nbsp;1994&nbsp;年&nbsp;4&nbsp;月,&nbsp;20&nbsp;日左右），有个会周期性地更新档案系统缓冲区的&nbsp;<BR>
程式叫做″&nbsp;update&nbsp;”被升级或取代掉了。&nbsp;<BR>
&nbsp;<BR>
取得″&nbsp;bdflush&nbsp;″的原始程式码（你应该可以从你取得核心的地方找到），然後编译&nbsp;<BR>
它（你可能会希望在旧版的核心下执行编译及安装）。它会以″&nbsp;update&nbsp;″为名安装它&nbsp;<BR>
自己，而在此之後你的新核心应该会运作良好。&nbsp;<BR>
&nbsp;<BR>
7.7.&nbsp;系统显示关於&nbsp;obsolete&nbsp;routing&nbsp;requests&nbsp;的奇怪讯息&nbsp;<BR>
&nbsp;<BR>
取得新版的&nbsp;route&nbsp;程式，并且重新编译旧的要件。&nbsp;/usr/src/linux/route.h&nbsp;（这是&nbsp;<BR>
/usr/src/linux&nbsp;下的一个档案）已经做了修改。&nbsp;<BR>
&nbsp;<BR>
8.&nbsp;□诀和技巧&nbsp;<BR>
&nbsp;<BR>
8.1.&nbsp;重导&nbsp;make&nbsp;或是&nbsp;patch&nbsp;指令的输出&nbsp;<BR>
&nbsp;<BR>
如果你想要记录这些″&nbsp;make&nbsp;″或是″&nbsp;patch&nbsp;″&nbsp;指令到底做了些什麽，你可以把萤幕&nbsp;<BR>
的输出重导到一个档案去。首先，要知道你用的是是那一种&nbsp;shell：″&nbsp;grep&nbsp;root&nbsp;<BR>
/etc/passwd″&nbsp;然後寻找看起来像″&nbsp;/bin/csh&nbsp;″一类的东西。&nbsp;<BR>
&nbsp;<BR>
如果你使用的是&nbsp;sh&nbsp;或是&nbsp;bash&nbsp;，″&nbsp;(command)&nbsp;2&gt;&amp;1&nbsp;|&nbsp;tee&nbsp;(output&nbsp;file)&nbsp;。″将会&nbsp;<BR>
把一份&nbsp;make&nbsp;的输出放到″&nbsp;(output&nbsp;file)&nbsp;″这个档案去。&nbsp;<BR>
&nbsp;<BR>
如果是&nbsp;csh&nbsp;或&nbsp;bash，你应该使用″&nbsp;(command)&nbsp;|&amp;&nbsp;tee&nbsp;(output&nbsp;file)&nbsp;″这个语法。&nbsp;<BR>
&nbsp;<BR>
如果是&nbsp;rc（注意：你应该不会是用&nbsp;rc&nbsp;），语法是″&nbsp;(command)&nbsp;&gt;[2=1]&nbsp;<BR>
|&nbsp;tee&nbsp;(output&nbsp;file)&nbsp;。&quot;&nbsp;<BR>
&nbsp;<BR>
9.&nbsp;&nbsp;Misc&nbsp;<BR>
&nbsp;<BR>
9.1.&nbsp;&nbsp;Author&nbsp;<BR>
&nbsp;<BR>
The&nbsp;original&nbsp;revision&nbsp;was&nbsp;-0.1&nbsp;on&nbsp;3&nbsp;October&nbsp;1994&nbsp;by&nbsp;Brian&nbsp;Ward&nbsp;<BR>
(<A HREF="mailto:[e-mail]).">[e-mail]).</A>&nbsp;&nbsp;Please&nbsp;send&nbsp;me&nbsp;any&nbsp;comments,&nbsp;additions,&nbsp;<BR>
corrections,&nbsp;or&nbsp;computers.&nbsp;&nbsp;Corrections&nbsp;are,&nbsp;in&nbsp;particular,&nbsp;the&nbsp;most&nbsp;<BR>
important&nbsp;to&nbsp;me!&nbsp;<BR>
&nbsp;<BR>
Even&nbsp;though&nbsp;I&nbsp;try&nbsp;to&nbsp;be&nbsp;attentive&nbsp;as&nbsp;possible&nbsp;with&nbsp;mail,&nbsp;please&nbsp;<BR>
remember&nbsp;that&nbsp;I&nbsp;get&nbsp;a&nbsp;lot&nbsp;of&nbsp;mail&nbsp;per&nbsp;day,&nbsp;so&nbsp;it&nbsp;may&nbsp;take&nbsp;a&nbsp;little&nbsp;<BR>
time&nbsp;to&nbsp;get&nbsp;back&nbsp;to&nbsp;you.&nbsp;Especially&nbsp;when&nbsp;emailing&nbsp;me&nbsp;with&nbsp;a&nbsp;question,&nbsp;<BR>
please&nbsp;try&nbsp;extra&nbsp;hard&nbsp;to&nbsp;be&nbsp;clear&nbsp;and&nbsp;detailed&nbsp;in&nbsp;your&nbsp;message.&nbsp;I'd&nbsp;<BR>
like&nbsp;to&nbsp;thank&nbsp;everyone&nbsp;who's&nbsp;given&nbsp;me&nbsp;feedback.&nbsp;<BR>
&nbsp;<BR>
9.2.&nbsp;&nbsp;History&nbsp;and&nbsp;other&nbsp;forms&nbsp;of&nbsp;this&nbsp;document&nbsp;<BR>
&nbsp;<BR>
I&nbsp;originally&nbsp;wrote&nbsp;this&nbsp;in&nbsp;ASCII,&nbsp;then&nbsp;I&nbsp;put&nbsp;some&nbsp;TeX&nbsp;around&nbsp;it,&nbsp;and&nbsp;<BR>
then&nbsp;horrified&nbsp;the&nbsp;TeX&nbsp;so&nbsp;that&nbsp;I&nbsp;could&nbsp;convert&nbsp;the&nbsp;TeX&nbsp;into&nbsp;SGML&nbsp;with&nbsp;<BR>
a&nbsp;perl&nbsp;script.&nbsp;Because&nbsp;of&nbsp;the&nbsp;original&nbsp;in&nbsp;TeX,&nbsp;the&nbsp;first&nbsp;version&nbsp;of&nbsp;<BR>
this&nbsp;document&nbsp;that&nbsp;appeared&nbsp;on&nbsp;sunsite&nbsp;had&nbsp;two&nbsp;section&nbsp;numbers&nbsp;with&nbsp;<BR>
each&nbsp;section&nbsp;(It&nbsp;wouldn't&nbsp;have&nbsp;looked&nbsp;that&nbsp;bad&nbsp;if&nbsp;they&nbsp;weren't&nbsp;<BR>
different.).&nbsp;&nbsp;I&nbsp;also&nbsp;realize&nbsp;that&nbsp;it's&nbsp;kind&nbsp;of&nbsp;nonstandard&nbsp;to&nbsp;make&nbsp;<BR>
revision&nbsp;numbers&nbsp;negative,&nbsp;but&nbsp;oh&nbsp;well.&nbsp;And&nbsp;if&nbsp;any&nbsp;of&nbsp;the&nbsp;above&nbsp;sounds&nbsp;<BR>
kind&nbsp;of&nbsp;stupid,&nbsp;I&nbsp;don't&nbsp;blame&nbsp;you.&nbsp;<BR>
&nbsp;<BR>
9.3.&nbsp;&nbsp;To&nbsp;do&nbsp;<BR>
&nbsp;<BR>
The&nbsp;``Tricks&nbsp;and&nbsp;tips''&nbsp;section&nbsp;is&nbsp;a&nbsp;little&nbsp;small.&nbsp;I&nbsp;hope&nbsp;to&nbsp;expand&nbsp;on&nbsp;<BR>
it&nbsp;with&nbsp;suggestions&nbsp;from&nbsp;others.&nbsp;<BR>
&nbsp;<BR>
So&nbsp;is&nbsp;``Additional&nbsp;packages.''&nbsp;<BR>
&nbsp;<BR>
More&nbsp;debugging/crash&nbsp;recovery&nbsp;info&nbsp;needed.&nbsp;<BR>
&nbsp;<BR>
9.4.&nbsp;&nbsp;Contributions&nbsp;<BR>
&nbsp;<BR>
A&nbsp;small&nbsp;part&nbsp;of&nbsp;Linus'&nbsp;README&nbsp;(Re:&nbsp;kernel&nbsp;hacking&nbsp;options)&nbsp;is&nbsp;<BR>
inclusive.&nbsp;&nbsp;(Thanks,&nbsp;Linus!)&nbsp;<BR>
&nbsp;<BR>
<A HREF="mailto:[e-mail]">[e-mail]</A>&nbsp;(Ulrich&nbsp;Callmeier):&nbsp;patch&nbsp;-s&nbsp;and&nbsp;xargs.&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
<A HREF="mailto:[e-mail]">[e-mail]</A>&nbsp;(Daniel&nbsp;Quinlan):&nbsp;corrections&nbsp;and&nbsp;additions&nbsp;in&nbsp;<BR>
many&nbsp;sections.&nbsp;<BR>
&nbsp;<BR>
<A HREF="mailto:[e-mail]">[e-mail]</A>&nbsp;(Nat&nbsp;MAKAREVITCH):&nbsp;mrproper&nbsp;<BR>
&nbsp;<BR>
The&nbsp;people&nbsp;who&nbsp;have&nbsp;sent&nbsp;me&nbsp;mail&nbsp;with&nbsp;questions&nbsp;and&nbsp;problems&nbsp;have&nbsp;been&nbsp;<BR>
helpful,&nbsp;too!&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
9.5.&nbsp;&nbsp;Copyright&nbsp;notice&nbsp;and&nbsp;copying&nbsp;<BR>
&nbsp;<BR>
Copyright&nbsp;(c)&nbsp;Brian&nbsp;Ward,&nbsp;1994,&nbsp;1995.&nbsp;<BR>
&nbsp;<BR>
This&nbsp;document&nbsp;may&nbsp;be&nbsp;distributed&nbsp;in&nbsp;any&nbsp;medium&nbsp;as&nbsp;long&nbsp;as&nbsp;it&nbsp;and&nbsp;this&nbsp;<BR>
notice&nbsp;remain&nbsp;unaltered.&nbsp;Permission&nbsp;is&nbsp;granted&nbsp;for&nbsp;translation&nbsp;into&nbsp;<BR>
any&nbsp;language,&nbsp;so&nbsp;long&nbsp;as&nbsp;the&nbsp;translator's&nbsp;name&nbsp;is&nbsp;added&nbsp;to&nbsp;the&nbsp;<BR>
document.&nbsp;There&nbsp;is&nbsp;no&nbsp;warranty&nbsp;on&nbsp;this&nbsp;document&nbsp;and&nbsp;its&nbsp;contents;&nbsp;no&nbsp;<BR>
one&nbsp;may&nbsp;be&nbsp;held&nbsp;liable&nbsp;for&nbsp;any&nbsp;unfortunate&nbsp;outcome&nbsp;of&nbsp;its&nbsp;content.&nbsp;<BR>
&nbsp;<BR>
Commercial&nbsp;redistribution&nbsp;is&nbsp;allowed&nbsp;and&nbsp;encouraged;&nbsp;however,&nbsp;it&nbsp;is&nbsp;<BR>
strongly&nbsp;recommended&nbsp;that&nbsp;the&nbsp;redistributor&nbsp;contact&nbsp;the&nbsp;author&nbsp;before&nbsp;<BR>
the&nbsp;redistribution,&nbsp;in&nbsp;the&nbsp;interest&nbsp;of&nbsp;keeping&nbsp;things&nbsp;up-to-date.&nbsp;The&nbsp;<BR>
&nbsp;<BR>


<CENTER><H1>BBS水木清华站∶精华区</H1></CENTER>



</BODY>

</HTML>