From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Transferring an existing install to new disk
Date: Wed, 12 Nov 2008 11:56:16 -0600 [thread overview]
Message-ID: <87vdusomkf.fsf@newsguy.com> (raw)
In-Reply-To: 20081112162010.45b5d21d@zaphod.digimed.co.uk
Neil Bothwick <neil@digimed.co.uk> writes:
> On Wed, 12 Nov 2008 09:51:12 -0600, Harry Putnam wrote:
>
>> > So boot your existing Gentoo setup as usual, then follow the handbook
>> > to install on the new disk. You do not have to boot from a live CD to
>> > install Gentoo, and suitable working Linux environment will do the
>> > job, and an existing Gentoo installation is more than suitable.
>>
>> There still seems to be some misunderstanding.
>>
>> I want to build up a fresh install somewhere besides my existing
>> desktop OS (gentoo). Leave the existing setup alone for now.
>
> Which is what a chroot install does.
>
>> Get the fresh install up to speed so it is a fresh and new
>> approximation of my desktop OS.
>
> Ditto.
>
>> And finally overwrite the desktop OS with the newly built one.
>
> Overwrite? Where does the new disk come into it then?
New as in new to the built up install. Perhaps a better choice would
have been `different disk'
>
>> It sounds like what you are describing is just a new install using an
>> exiting gentoo os instead of install disk.
>>
>> But the result would be a new install with nothing setup... on the
>> desktop which is not what I want.
>
> Obviously, you would set everything up, but it would be made easier by
> the fact you are running on the target machine, and everything is in
> place. There's no copying entire systems over, just change the bootloader
> config when it's ready.
Ok, I see where your going here.... remove the notion of `new' disk.
I don't have room for a new disk on the target machine, hence the idea
of overwriting.
But just talking about this much seems to indicate I'd be better off
braving up and trying to clean up my existing install.
Note a different thread where I've started on that mission:
Subject: How to fix a hefty (emerge) blocking problem
To be posted shortly
next prev parent reply other threads:[~2008-11-12 17:56 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 [this message]
2008-11-12 17:58 ` Dale
2008-11-13 10:54 ` Peter Humphrey
2008-11-12 19:55 ` [gentoo-user] " Michele Schiavo
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=87vdusomkf.fsf@newsguy.com \
--to=reader@newsguy.com \
--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