(Created page with "''a.k.a. I like my Linux how I like my women... <s>easy to set up</s>flexible.'' This is a script to backup and/or transfer a working Funtoo installation onto a fresh install (o...")

Line 1:

Line 1:

−

== Idea ==

+

''a.k.a. I like my Linux how I like my women... <s>easy to set up</s>flexible.''

−

Hey guys I think that starting a Funtoo News letter or information source, an official Blog may suite our purposes better, would be a great idea for keeping the community informed about the things going on in the world of Funtoo. I think we could provide a lot of information once instead of answering the same questions over and over again. It would also be a good time to bring out the best that Funtoo has to offer. Here are just a few ideas that I have concerning frequency and content.

+

This is a script to backup and/or transfer a working Funtoo installation onto a fresh install (on the same or a different host).

−

+

−

== Frequency ==

+

−

I think that it would be good to at least to start out with once a month and then as content increases to go to bi weekly or even based on the subject.

+

It won't speed up an install and it doesn't make it easier, but with it you can do a single reboot

−

+

and have a complete working system without tedious config file editing.

−

== Content ==

+

−

I think we should be real open handed about the subject matter but closed handed on the quality. What I mean by that is I think we should include things from developer interviews all the way to user reviews (maybe a Q&A section), and really anything that strikes our fancy and is Funtoo related. I also think that the quality of the content needs to be enforced. Maybe having a couple of people read each article or issue objectively and then say yeah this is good before we ship it out. Tell me what you guys think? Is this a Good Idea?

Take a peek at the list of files in $HOST_FILES and edit them to the host's specification.

+

+

{{Info|You cannot expect every host to have the exact geometry or architecture as the original host. If, by some miracle, the two are exactly alike, go ahead and unpack the host tarball (probably into <tt>/tmp</tt>).}}

+

+

{{Info|The host tarball uses the prefix <tt>host/</tt> instead of the regular <tt>etc/</tt>. This is for your protection (and a limitation of the script... but mostly protection).}}

+

+

Chroot in and run (I suggest in a screen, nohup or another VT):

+

{{Root|<nowiki># env-update; source /etc/profile

+

# emerge -uDN world</nowiki>}}

+

+

Wait (or finish configuration). Remember to make a kernel and <tt># boot-update</tt> (and installing the bootloader to MBR if necessary).

+

+

Add an identical user (it's not in the script, but you might want to save the output of <tt>$ groups</tt>) and unpack <tt>home-overlay.tar</tt>. If you have anything in <tt>usrlocal-overlay.tar</tt> you can unpack that too.

+

+

{{Info|If you're installing on a different architecture, the contents of <tt>/usr/local</tt> may be useless for your CPU.

+

If you're lucky, it may be all architecture-independent/interpreted scripts, or nothing at all.}}

+

+

If all goes well, reboot (and remove the install environment)!

Latest revision as of 14:19, November 17, 2010

a.k.a. I like my Linux how I like my women... easy to set upflexible.

This is a script to backup and/or transfer a working Funtoo installation onto a fresh install (on the same or a different host).

It won't speed up an install and it doesn't make it easier, but with it you can do a single reboot
and have a complete working system without tedious config file editing.