[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[OT] RE: Replacing hda - Easiest Way?



> From: Johannes Wiedersich [mailto:johannes@physik.blm.tu-muenchen.de]
> Subject: Re: Replacing hda - Easiest Way?
> 
> On 2008-08-05 15:35, Stackpole, Chris wrote:
> > There have been some good suggestions, but none that I would really
> consider "the Easy way". I don't know your level of experience, but
for
> me "the Easy Way" is the one that can be done by almost anyone without
> tons of technical documentation.
> >
> > Here is what I have done in the past that worked perfect for me:
> > 1) Boot system off of Knoppix (or any other live CD with the
following
> tools).
> > 2) Use whatever partition manager you prefer to create your
partitions
> on the new drive (QTparted, Gparted, fdisk, ect).
> > 3) Use PartImage to copy the partitions over.
> http://en.wikipedia.org/wiki/PartImage
> 
> I don't really see, how partimage is more 'easy' than rsync -ax.
> partimage has a more guish interface, so requires more interaction. In
> order to use partimage, the partition has to be unmounted, ie you have
> to use a rescue medium, while rsync backups and restores your running
> system. (I more than once upgraded a system from stable to testing,
> didn't like it and just rsync'ed my backup to reboot into the 'old'
> kernel & stable system. )
> 
> > 4) Mount new hard drive and ensure mount points are correct (meaning
if
> old drive is hda and new drive is sda, change accordingly).
> > 5) Shutdown, remove old harddrive, boot into new drive!
> 
> > Done!
> 
> Works just as well, if you skip 1) and replace 3) by 'rsync -ax'.
> 
> The advantage of partimage might be that it might copy your mbr and
thus
> save you the effort of grub-install. (Don't remember exactly about
this;
> it won't hurt to run grub-install either way)
> 
> HTH, take care!
> 
> Johannes


*Since this particular topic is drifting from the OP, I am going to mark
my post as OT.


Yes, I will agree that rsync is easy to do if you already know the
command and what it is capable of. It is indeed a very powerful tool.
However, for someone who doesn't already know the command it can be a
bit overwhelming. At least that has been my experience in
watching/helping others with it.

My experience with partimage is that as long as you have an idea of what
you want to do, the gui will hold your hand and get done what you need
to get done. This is exactly what some people want when they first get
started; a nice simple layout to get them started. The advanced stuff
can wait till they are ready. Partimage has a lot of really cool
advanced stuff, but simply running partimage at the command line (given
it is installed of course) will simply bring up the nice gui.

I am of the opinion that you shouldn't blindly run commands on your
system that you have found out on the net. I am a big fan of researching
the command as well as the options. This usually requires reading
through the man pages and some Google searching. Rsync has 3463 lines of
documentation in the man pages alone. For someone like me who likes good
documentation to learn from, that is great! For someone who just wants
it to work, that is a PITA. 

Shachar Or and yourself are the only ones to suggest flags to use for
rsync. Even then, the full command wasn't even given which can only
confuse the inexperienced. Running 'rsync -ax' only kicks back the help
message. Doesn't really solve the problem that the user may think they
were attempting to solve.

I have nothing against rsync. To be quite honest, the majority of uses
for these two tools are completely different. I just think in this case
it is a bigger jump to dive into rsync for a new user then it is for
partimage. I would much prefer to give someone a tool that will help
guide them (hence, in my mind, easier) then a really powerful tool that
is way more then they need and above their head.

Anyway, maybe I am way off on this but before I blabber on and on I will
give the list a chance to see if everyone agrees or disagrees with me.
;-D

Have fun!
~S~


Reply to: