public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dieter Ries <clip2@gmx.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Cloning a system drive
Date: Sat, 06 Oct 2007 14:22:24 +0200	[thread overview]
Message-ID: <47077E00.7090404@gmx.de> (raw)
In-Reply-To: <5bdc1c8b0710051607j482e0b61q9cf9dd9f468a65f2@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

Mark Knecht schrieb:
> On 10/5/07, Drake Donahue <donahue95@comcast.net> wrote:
>> The Gparted live cd now has clonezilla incorporated, the claims for
>> clonezilla suggest it would be perfect for your purpose.
>> http://sourceforge.net/project/showfiles.php?group_id=115843&package_id=173828
>>
>> link may be fractured in transmission
> 
> Thanks to you and Dieter for responding.
> 
> It certainly looks like it's worth burning a CD and seeing what it looks like.
> 
> With respect to both of your answers I presume that with any solution,
> since this is my main Gentoo system drive, I need to not be running
> Gentoo from that drive when I do the clone, correct? Any solution
> would require me to boot from some other media?

Definitely. After reading what Drake wrote, I guess the GParted CD
should be your first choice, I remember I saw an earlier version of that
CD doing a great job in guessing a lost partition table.

The command I wrote initially is more or less a, slightly more CPU
intensive, copy command, which takes care of all the permissions etc
stuff, without making you any trouble. It has to be issued from a live
CD, in the example with your old HD mounted to /mnt/OLD and your new one
to /mnt/NEW.


> Also, I really don't need to change any partitions sizes but I'm
> unclear whether I am responsible for creating the partitions myself?
> It seems with Dieter's solution I have to do that. I'm unsure if they
> have to be exactly the same size, in the same location, etc. With the
> gparted solution maybe it does some (or all) of this for me?

Yes, it should.

> 
> Anyway, thanks for the link.
> 
> Cheers,
> Mark

cu
Dieter

-- 
3rd Law of Computing:
        Anything that can go wr
fortune: Segmentation violation -- Core dumped


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2007-10-06 12:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 20:58 [gentoo-amd64] Cloning a system drive Mark Knecht
2007-10-05 21:14 ` Dieter Ries
2007-10-05 22:46 ` Drake Donahue
2007-10-05 23:07   ` Mark Knecht
2007-10-06  1:00     ` Drake Donahue
2007-10-06 12:22     ` Dieter Ries [this message]
2007-10-06  1:53 ` [gentoo-amd64] " Duncan
2007-10-06  2:35   ` Richard Freeman
2007-10-06  2:43     ` Mark Knecht
2007-10-06 12:47       ` Duncan
2007-10-06 13:16         ` Mark Knecht
2007-10-07  3:58           ` Drake Donahue
2007-10-07  4:49             ` Peter Davoust
2007-10-07  9:33               ` Duncan
2007-10-07 18:34               ` Brian Litzinger
2007-10-08  9:17                 ` Beso
2007-10-08 16:17                   ` Brian Litzinger
2007-10-08 16:28                     ` Mark Knecht
2007-10-08 16:43                     ` Beso
2007-10-08 22:39                       ` Peter Davoust

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=47077E00.7090404@gmx.de \
    --to=clip2@gmx.de \
    --cc=gentoo-amd64@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