public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michele Schiavo <gentoo@micheleschiavo.it>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Transferring an existing install to new disk
Date: Wed, 12 Nov 2008 20:55:27 +0100	[thread overview]
Message-ID: <1226519727.4390.5.camel@speriment.uzz.local> (raw)
In-Reply-To: <87d4h1pfaz.fsf@newsguy.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1789 bytes --]

I did it last week.

in some place untar che last stage3-xxx

mount --bind proc, dev, usr/portage, passwd, group ecc
copy inside current make.conf, make.profile
chroot inside the new stage.

when finish i make a big tar of everyone in the new chroot.
reboot with live cd, move all my old system in /old, untar the new
system on the rootfs.

if something is missing in the new system , you have the original file
of configuration in /old

P.S. sometime i make something like stage4 from livecd and i store it in
a USB HD.

If something is going wrong, in 20 min i can restore all my system.




Il giorno mer, 12/11/2008 alle 01.35 -0600, Harry Putnam ha scritto:

> I should know how to do this but so many changes have happened
> recently and I haven't done anything like this for a very long time.
> 
> My desktop version of gentoo is pretty far out of date.  And I think
> there have been enough changes that I don't even want to try to get it
> cleaned up.  
> 
> Rather, I'd like to build up a newly installed gentoo to the point
> where it has all the stuff I want.  But do it inside a vmware virtual
> machine. 
> 
> I'm trying to keep my working desktop in place until such time as the
> vmware gentoo setup is ready
> 
> Once that install is up to speed with all my preferred apps in place.
> And any kinks worked out...
> Only then use it to overwrite my desktop OS.  Or reformat that disk
> and move the vmware gentoo version to it.
> 
> The vmware gentoo would be guest on a windows XP pro machine.
> 
> I'd like to hear any comments concerning what problems I might run
> into or whether the plan is likely to be a serious mess.
> 
> Also wouldn't mind seeing a rough outline of how to make that kind of
> move. 
> 
> 
> 

[-- Attachment #1.1.2: Type: text/html, Size: 2098 bytes --]

[-- Attachment #1.2: stage4_uzzmaster.sh --]
[-- Type: application/x-shellscript, Size: 7810 bytes --]

[-- Attachment #2: Questa è una parte del messaggio firmata digitalmente --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2008-11-12 19:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12  7:35 [gentoo-user] Transferring an existing install to new disk Harry Putnam
2008-11-12  7:59 ` Dirk Uys
2008-11-12  9:52   ` Garry Smith
2008-11-12 10:22     ` Daniel Pielmeier
2008-11-12 14:54   ` Alan Mackenzie
2008-11-12 17:50     ` Dale
2008-11-12 17:58       ` Paul Hartman
2008-11-12 18:20         ` Dale
2008-11-13  8:18     ` Dirk Uys
2008-11-12 10:35 ` Neil Bothwick
2008-11-12 14:03   ` [gentoo-user] " Harry Putnam
2008-11-12 14:53     ` Neil Bothwick
2008-11-12 15:51       ` Harry Putnam
2008-11-12 16:20         ` Neil Bothwick
2008-11-12 17:56           ` Harry Putnam
2008-11-12 17:58         ` Dale
2008-11-13 10:54       ` Peter Humphrey
2008-11-12 19:55 ` Michele Schiavo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1226519727.4390.5.camel@speriment.uzz.local \
    --to=gentoo@micheleschiavo.it \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox