System resurrection - Revision history

Drobbins at 19:10, 21 April 2012

2012-04-21T19:10:01Z

Oleg at 14:46, 20 April 2012

2012-04-20T14:46:15Z

404 Error: /* Critical System Packages */

2011-03-24T00:50:13Z

‎Critical System Packages

Oleg at 18:12, 23 March 2011

2011-03-23T18:12:19Z

Rh1: /* Critical System Packages */

2011-03-23T17:42:51Z

‎Critical System Packages

Rh1: /* Critical System Packages */

2011-03-23T17:41:35Z

‎Critical System Packages

Drobbins: /* Restoring the binary packages on the broken system */

2011-03-23T17:18:56Z

‎Restoring the binary packages on the broken system

Drobbins: add categories

2011-03-23T17:17:53Z

add categories

Drobbins: /* Building binary packages */

2011-03-23T17:11:45Z

‎Building binary packages

Drobbins: more editing

2011-03-23T17:10:52Z

more editing

← Older revision		Revision as of 19:10, 21 April 2012
Line 134:		Line 134:
	[[Category:Internals]]		[[Category:Internals]]
	[[Category:Portage]]		[[Category:Portage]]
		+	[[Category:HOWTO]]

@@ Line 77: / Line 77: @@
 At this point, you can set up bind mounts (see <tt>/mnt/rescue</tt> example earlier in this document for those steps), <tt>chroot</tt> inside <tt>/mnt/broken</tt>, and perform a few tests to determine if your issue has been resolved.
 = Critical System Packages =
 Several packages at the heart of your Funtoo system, these mainly are:

@@ Line 105: / Line 105: @@
 |Python
 |dev-lang/python
-|Portage written in python. It is a vital package for Funtoo/Gentoo.
+|The Python interpreter is the heart of Portage as is written in Python (the same is also true for various second line utilities).
 |}

@@ Line 102: / Line 102: @@
 |sys-libs/zlib
 |This library contain several lossless compression/decompression routines.It is used by many other components on a Funtoo system like the bzip2/bunzip2 commands (app-arch/bzip2) for example (xz archive utilities depends on another standalone set of libraries).
 |}

@@ Line 97: / Line 97: @@
 |C Library
 |sys-libs/glibc
-|The C library contains an implementation of a wide range of commonly needed functionalities like memory allocation, strings manipulation, I/O operations and so on. It is maybe of one most critical system components as nearly everything on a Funtoo system depends on this component (including the Python interpreter which executes the vairous Python scripts at the heart of the Funtoo core utilities and package management system).
+|The C library contains an implementation of a wide range of commonly needed functionalities like memory allocation, strings manipulation, I/O operations and so on. It is maybe one of the most critical system components as nearly everything on a Funtoo system depends on this component (including the Python interpreter which executes the vairous Python scripts at the heart of the Funtoo core utilities and package management system).
 |-
 |Z library

@@ Line 93: / Line 93: @@
 |GNU Compiler collection (GCC)
 |sys-devel/gcc
-|GCC is a collection of compilers or several languages (FORTRAN, Java, C and C++, plus some libraries like the Standard Template Library or ''STL''). A wide spectrum of software in a Funtoo system is written in C/C++.
+|GCC is a collection of compilers for several languages (FORTRAN, Java, C and C++, plus some libraries like the Standard Template Library or ''STL''). A wide spectrum of software in a Funtoo system is written in C/C++.
 |-
 |C Library

@@ Line 47: / Line 47: @@
 === Chroot/Emerge Method ===
-The first step can be used for lightly damaged systems that still have a functional Portage and to which you can still <tt>chroot</tt> and perform all basic Linux commands. To use this method, you would mount your broken system to <tt>/mnt/broken</tt> using steps similar to the way we set up <tt>/mnt/rescue</tt>, above.
+This first approach can be used for lightly damaged systems that still have a functional Portage and to which you can still <tt>chroot</tt> and perform all basic Linux commands. To use this method, you would mount your broken system to <tt>/mnt/broken</tt> using steps similar to the way we set up <tt>/mnt/rescue</tt>, above.
 Before or after chrooting, copy the binary packages created in the step above in the exact same location on your broken system (e.g. in <tt>/usr/portage/packages/'''sys-devel'''</tt> in the case of <tt>'''sys-devel'''/gcc</tt>).

← Older revision		Revision as of 17:17, 23 March 2011
Line 111:		Line 111:
	'''P2:''' Same problem as described in P1 but I use another machine on my network or a public mirror on the Internet <br>		'''P2:''' Same problem as described in P1 but I use another machine on my network or a public mirror on the Internet <br>
	'''S2:''' See the solution given in S1 but with providing the IP of the machine you are downloading for.		'''S2:''' See the solution given in S1 but with providing the IP of the machine you are downloading for.
		+
		+	[[Category:Internals]]
		+	[[Category:Portage]]

@@ Line 38: / Line 38: @@
 <pre>
-# emerge --buildpkgonly  sys-devel/gcc
+# emerge --buildpkgonly sys-devel/gcc
 </pre>

@@ Line 1: / Line 1: @@
-Although it is always possible to resurrect a machine back to life by reinstalling it, it is not always suitable to reinstall from scratch and sometimes the best is to try to fix a broken system even with as a last resort option before a full system reinstallation. Here are some ideas on how to resurrect a dead Funtoo system without reinstalling everything from scratch.
+Although it is always possible to resurrect a machine back to life by reinstalling it, it is not always suitable to reinstall from scratch. Sometimes the best approach is to try to repair, or "resurrect," a broken system so that is it fully functional again. This document will show you how to resurrect a broken Funtoo system without reinstalling everything from scratch.
 == Building binary packages ==
@@ Line 5: / Line 5: @@
 The best approach for critical system repair is to boot on a SystemRescueCD or other similar LiveCD, and use this as working platform to resurrect your system.
-For creating binary packages, you can use any of the following options for a source environment:
+For creating binary packages, you can use any of the following for a ''source environment'':
-* Use the most recent Funtoo stage3 for your architecture.
+* Use the most recent Funtoo stage3 for your architecture
-* If available, use a recent system backup (e.g. snapshot if you use a BTRFS or ZFS filesystem or LVM volume, or a tar or cpio backup of your hard drive)
+* If available, use a recent system backup (tar or cpio archive) or snapshot
-On a working Linux system, which can be either your broken system booted with a LiveCD, or another system on your network, you will want to build a chroot environment using the "source environment" you selected above, and use this as a platform for building binary packages to restore your system. Once these packages are created, they can be copied to your broken system and installed using the steps later in this document.
+On a working Linux system, which can be either your broken system booted with a LiveCD, or any type of Linux system on your network with similar processor, you will want to build a chroot environment using the "source environment" you selected above, and use this as a platform for building binary packages to restore your system. Once these packages are created, they can be copied to your broken system and installed using the steps later in this document.
 The binary package creation environment would typically be set up as follows:
@@ Line 27: / Line 27: @@
 </pre>
-No matter of the way you jump in a functional Funtoo/Gentoo environment, the magic command to create a binary package archive once inside is <tt>quickpkg</tt>. <tt>quickpkg</tt> will capture the package in the exact form it is actually deployed on the environment and create an archive of it placed in <tt>/usr/portage/packages/<package-category>/<package-name>-<package-version>.tbz2</tt>.
+No matter of the way you jump in a functional Funtoo/Gentoo environment, the magic command to create a binary package archive once inside is to use the <tt>quickpkg</tt> command. <tt>quickpkg</tt> will capture the package in the exact form it is actually deployed on the environment and create an archive of it placed in <tt>/usr/portage/packages/<package-category>/<package-name>-<package-version>.tbz2</tt>.
 In the following example capture everything installed within the "source environment" that is related <tt>sys-devel/gcc</tt> (4.4.5 is present on the system) is captured in a single archive named gcc-4.4.5.tbz2 located in <tt>/usr/portage/packages/sys-devel</tt>: