From: Tommy Moore <tmoore@cmrc.org>
To: "blinux-list@redhat.com" <blinux-list@redhat.com>
Subject: Re: transfering linux system to another hard drive
Date: Tue, 4 Dec 2001 16:45:51 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.33.0112041641340.25799-100000@neptune.aoml.noaa.gov> (raw)
In-Reply-To: <Pine.LNX.4.43.0112041616450.6816-100000@toccata.grg.afb.net>
Nope if you make the new partition on the second drive and copy data from
the first all you do is boot in with boot disk when you changed hdb to hda
and run lilo.
Have done this multiple times and its allways worked.
you may need to acc lba32 to the top of lilo.conf so that it'll work with
all drives but once you've done that you should be set to tgo.
I'd rather spend 5 minutes doing this than to spend 20 doing a reinstall.
You can't do this on a running system though you have to do this from boot
and root disks.
Just fdisk the new drive the way you like and format new partition and
then mount the drives on different mount points and then do a cp -ap .
/new_drive
from with in the / directory of old drive and everything should work.
Remember to reboot between the format and fdisk process though.
Tommy
On Tue, 4 Dec 2001, Janina Sajka wrote:
> Yes, all the hardware except the drive is the same. But, that's just the
> point. Am I wrong about this? Aren't their drive specific params to an
> install?
>
> Second, is installation really that hard? Seems it should be cleaner to
> simply install then move the data, including appropriate /etc
> configurations, back over. Certainly seems more secure and less
> experimental to me.
>
> But, I've been wrong before.
>
> On Tue, 4 Dec 2001, Tommy Moore wrote:
>
> > Hi thre.
> > Why shouldn't someone back up the system like what she wants to do if
> > dropping it on to a different drive.
> > She is after all going to use the same machine and even if she wasn't in a
> > lot of cases it would still work.
> > Would save her a lot of work in the process.
> > All she's doing is getting a larger drive from what I understand.
> >
> > Tommy
> >
> >
> >
> >
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://listman.redhat.com/mailman/listinfo/blinux-list
> >
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak
` Janina Sajka
` Tommy Moore
` Janina Sajka
` Cheryl Homiak
` Janina Sajka
` Angelo Sonnesso
[not found] ` <Pine.LNX.4.43.0112050813440.8581-100000@toccata.grg.afb.ne t>
` Brent Harding
` Tommy Moore [this message]
` Rafael Skodlar
` Brent Harding
` Rafael Skodlar
` L. C. Robinson
` Brent Harding
[not found] ` <Pine.LNX.4.43.0112041616450.6816-100000@toccata.grg.afb.ne t>
` Brent Harding
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=Pine.LNX.4.33.0112041641340.25799-100000@neptune.aoml.noaa.gov \
--to=tmoore@cmrc.org \
--cc=blinux-list@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).