/[gentoo]/xml/htdocs/doc/en/gentoo-x86-tipsntricks.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-x86-tipsntricks.xml

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

Revision 1.5 Revision 1.6
14submitted tips and tricks for reference purposes. 14submitted tips and tricks for reference purposes.
15</abstract> 15</abstract>
16 16
17<license/> 17<license/>
18 18
19<version>1.2</version> 19<version>1.3</version>
20<date>April 11, 2004</date> 20<date>August 01, 2004</date>
21 21
22<chapter> 22<chapter>
23<title>Introduction</title> 23<title>Introduction</title>
24<section> 24<section>
25<title>Preliminary</title> 25<title>Preliminary</title>
58<b>Fixing Errors/Issues</b> 58<b>Fixing Errors/Issues</b>
59</p> 59</p>
60 60
61<ul> 61<ul>
62 <li><uri link="#checking-disks">Extensive Testing of your Disks</uri></li> 62 <li><uri link="#checking-disks">Extensive Testing of your Disks</uri></li>
63 <li>
64 <uri link="#recover">Recovering from a malfunctioning installation</uri>
65 </li>
63</ul> 66</ul>
64 67
65</body> 68</body>
66</section> 69</section>
67</chapter> 70</chapter>
365# <i>mke2fs -j -c /dev/hda3</i> 368# <i>mke2fs -j -c /dev/hda3</i>
366</pre> 369</pre>
367 370
368</body> 371</body>
369</section> 372</section>
373<section id="recover">
374<title>Recovering from a malfunctioning installation</title>
375<body>
376
377<p>
378If for some reason your Gentoo installation fails, you don't have to redo the
379installation all over again. Instead, you can safely "go" to the point where you
380think you made a mistake (or where you think the instructions are flawed) and
381try a different approach.
382</p>
383
384<p>
385First of all you need to chroot back into your Gentoo Linux environment. Follow
386the instructions again, but ignore the partitioning steps as your partitions are
387already created and even populated. You can therefore immediately mount those
388partitions at <path>/mnt/gentoo</path>. You should also ignore the steps about
389stage extraction and modifying <path>make.conf</path> - you don't want to
390overwrite your files do you?
391</p>
392
393<p>
394Once chrooted inside your Gentoo Linux environment, immediately go to the step
395where you think you should try a different approach. Don't redo all the steps
396like bootstrapping and such unless that is the place where you think things
397went wrong.
398</p>
399
400<p>
401For instance, if you believe that you have a wrongly configured
402<path>grub.conf</path>, you can immediately fire up your editor to update
403<path>/boot/grub/grub.conf</path>.
404</p>
405
406<p>
407Once you have tried a different approach for your situation, you should consider
408how much of the subsequent steps you need to perform again. If the subsequent
409steps are depending on your change, you will need to redo those.
410</p>
411
412<p>
413For instance,
414</p>
415
416<ul>
417 <li>
418 if you have changed a variable inside <path>make.conf</path> you will need
419 to do all subsequent compiling since those depend on the settings inside
420 <path>make.conf</path>
421 </li>
422 <li>
423 if you have altered <path>/boot/grub/grub.conf</path> you can immediately
424 exit the chrooted environment and reboot as no subsequent steps are
425 depending on <path>grub.conf</path>
426 </li>
427 <li>
428 if you have recompiled your kernel you only need to make sure that your
429 bootloader configuration points to the correct kernel image (double-check
430 that you mounted your <path>/boot</path>!), then you can exit the chrooted
431 environment and reboot
432 </li>
433 <li>
434 if you have altered <path>/etc/fstab</path> you can exit the chrooted
435 environment and reboot
436 </li>
437</ul>
438
439<p>
440As you can see, for most recovery operations you can immediately reboot. Only in
441certain cases will you need to redo the subsequent installation steps.
442</p>
443
444</body>
445</section>
446
370</chapter> 447</chapter>
371 448
372</guide> 449</guide>

Legend:
Removed from v.1.5  
changed lines
  Added in v.1.6

  ViewVC Help
Powered by ViewVC 1.1.20