/[gentoo]/xml/htdocs/doc/en/faq.xml
Gentoo

Diff of /xml/htdocs/doc/en/faq.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.36 Revision 1.37
43<li><uri link="#doc_chap3_sect10">How to I disable devfs?</uri></li> 43<li><uri link="#doc_chap3_sect10">How to I disable devfs?</uri></li>
44<li><uri link="#doc_chap3_sect11">How do I get a /dev/mouse that doesn't go away when I reboot (when using devfs)? </uri></li> 44<li><uri link="#doc_chap3_sect11">How do I get a /dev/mouse that doesn't go away when I reboot (when using devfs)? </uri></li>
45<li><uri link="#doc_chap3_sect12">Grub can't find stage x.y?</uri></li> 45<li><uri link="#doc_chap3_sect12">Grub can't find stage x.y?</uri></li>
46<li><uri link="#doc_chap3_sect13">My ASUS CUV4X-D won't boot and it freezes during various stages of kernel loading and hardware detection.</uri></li> 46<li><uri link="#doc_chap3_sect13">My ASUS CUV4X-D won't boot and it freezes during various stages of kernel loading and hardware detection.</uri></li>
47<li><uri link="#doc_chap3_sect14">If I have Gentoo 1.4_rc1 can I upgrade to 1.4_rc2, 1.4_final/_rc3 without reinstalling?</uri></li> 47<li><uri link="#doc_chap3_sect14">If I have Gentoo 1.4_rc1 can I upgrade to 1.4_rc2, 1.4_final/_rc3 without reinstalling?</uri></li>
48<li><uri link="#doc_chap3_sect15">My kernel doesn't boot (properly), what should I do now?</uri></li>
48</ul> 49</ul>
49</body> 50</body>
50</section> 51</section>
51<section> 52<section>
52<title>Package Management</title> 53<title>Package Management</title>
80<li><uri link="#doc_chap5_sect3">How do I set up an International Keyboard Layout?</uri></li> 81<li><uri link="#doc_chap5_sect3">How do I set up an International Keyboard Layout?</uri></li>
81<li><uri link="#doc_chap5_sect4">DNS name resolution works for root only. </uri></li> 82<li><uri link="#doc_chap5_sect4">DNS name resolution works for root only. </uri></li>
82<li><uri link="#doc_chap5_sect5">Why is KDE not reading /etc/profile? </uri></li> 83<li><uri link="#doc_chap5_sect5">Why is KDE not reading /etc/profile? </uri></li>
83<li><uri link="#doc_chap5_sect6">Why can't my user use their own crontab? </uri></li> 84<li><uri link="#doc_chap5_sect6">Why can't my user use their own crontab? </uri></li>
84<li><uri link="#doc_chap5_sect7">How do I get numlock to start on boot?</uri></li> 85<li><uri link="#doc_chap5_sect7">How do I get numlock to start on boot?</uri></li>
86<li><uri link="#doc_chap5_sect8">How do I have my terminal cleared when
87I log out?</uri></li>
85</ul> 88</ul>
86</body> 89</body>
87</section> 90</section>
88<section> 91<section>
89<title>Maintenance</title> 92<title>Maintenance</title>
326 <body> 329 <body>
327 In fact there is no difference between the 1.4 releases <b>after they&apos;ve installed</b>. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based. 330 In fact there is no difference between the 1.4 releases <b>after they&apos;ve installed</b>. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based.
328 As such 1.4rc1 machine for example, that does <c>emerge sync; emerge -u world</c> is <b>exactly the same</b> as a machine with 1.4rc2 installed, after it does <c>emerge sync; emerge -u world</c>. The true differences lie in the installer. 331 As such 1.4rc1 machine for example, that does <c>emerge sync; emerge -u world</c> is <b>exactly the same</b> as a machine with 1.4rc2 installed, after it does <c>emerge sync; emerge -u world</c>. The true differences lie in the installer.
329 </body> 332 </body>
330 </section> 333 </section>
334 <section>
335 <title>My kernel doesn't boot (properly), what should I do now?</title>
336 <body>
337 <p>
338 You don't need to redo every step of the installation, but only the
339 kernel-stuff and all associated steps. Suppose you have installed Gentoo
340 on <path>/dev/hda1</path> (/boot) and <path>/dev/hda3</path> (/) with
341 <path>/dev/hda2</path> being the swap space:
342 </p>
343 <pre caption = "Reconfiguring the kernel">
344<comment>Boot from the LiveCD and wait until you receive a prompt</comment>
345<comment>We first mount all partitions:</comment>
346# <i>mount /dev/hda3 /mnt/gentoo</i>
347# <i>mount /dev/hda1 /mnt/gentoo/boot</i>
348# <i>swapon /dev/hda2</i>
349# <i>mount -t proc none /mnt/gentoo/proc</i>
350<comment>Then we chroot into our Gentoo environment and configure the kernel:</comment>
351# <i>chroot /mnt/gentoo /bin/bash</i>
352# <i>env-update &amp;&amp; source /etc/profile</i>
353# <i>cd /usr/src/linux</i>
354# <i>make menuconfig</i>
355<comment>Now (de)select anything you have (de)selected wrongly at your</comment>
356<comment>previous attempt. Then quit and compile your kernel:</comment>
357# <i>make dep &amp;&amp; make bzImage modules modules_install</i>
358<comment>Now copy over your bzImage file, overwriting your previous one:</comment>
359# <i>cp arch/i386/boot/bzImage /boot</i>
360<comment>If you use LILO, rerun lilo -- GRUB users should skip this:</comment>
361# <i>/sbin/lilo</i>
362<comment>Now exit the chroot and reboot.</comment>
363# <i>exit</i>
364# <i>umount /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i>
365# <i>reboot</i>
366 </pre>
367 <p>
368 If on the other hand the problem lays with your bootloader configuration,
369 follow the same steps, but instead of configuring/compiling your kernel you
370 should reconfigure your bootloader (recompilation isn't necessary).
371 </p>
372 </body>
373 </section>
331</chapter> 374</chapter>
332 375
333<chapter> 376<chapter>
334 <title>Package Management</title> 377 <title>Package Management</title>
335 <section> 378 <section>
632 numlock default</c> and numlock will be activated on the next 675 numlock default</c> and numlock will be activated on the next
633 reboot. 676 reboot.
634 </p> 677 </p>
635 </body> 678 </body>
636 </section> 679 </section>
680 <section>
681 <title>How do I have my terminal cleared when I log out?</title>
682 <body>
683 <p>
684 To have your terminal cleared, add <c>clear</c> to your
685 <path>~/.bash_logout</path> script:
686 </p>
687 <pre caption = "Clearing the terminal during logout">
688$ <i>echo clear &gt;&gt; ~/.bash_logout</i></pre>
689 <p>
690 If you want this to happen automatically when you add a new
691 user, do the same for the <path>/etc/skel/.bash_logout</path>:
692 </p>
693 <pre caption = "Making new users their terminal clear on logout">
694# <i>echo clear &gt;&gt; /etc/skel/.bash_logout</i></pre>
695 </body>
696 </section>
697
637 698
638</chapter> 699</chapter>
639 700
640<chapter> 701<chapter>
641 <title>Maintenance</title> 702 <title>Maintenance</title>

Legend:
Removed from v.1.36  
changed lines
  Added in v.1.37

  ViewVC Help
Powered by ViewVC 1.1.20