public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "James R. Van Zandt" <jrv@vanzandt.mv.com>
To: blinux-list@redhat.com
Cc: blinux-list@redhat.com
Subject: Re: Transfering linux system to a new hard drive
Date: Sun, 16 Dec 2001 17:13:16 -0500 (EST)	[thread overview]
Message-ID: <m16FjX2-00012rC@vanzandt.mv.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0112031636300.2150-100000@maranatha.chartermi.net> (message from Cheryl Homiak on Mon, 3 Dec 2001 17:03:43 -0600 (CST))

I've read several good suggestions.  I would rank them this way:

1) Temporarily install your new drive in some other machine, connect
   it to your network, partition and format it, and copy your
   partitions over the network.  The second machine would not have to
   be running Linux - you could use a speakup rescue disk, provided it
   could access the network.  (It would not matter if it was an older
   version.)  This way, you could move all the data without having to
   power your existing box down.

2) Temporarily connect another machine to your network and copy the
   partitions into free space there.  Replace the drive, do a minimal
   install, and copy back.  You would not have to open up the second
   machine (and it could be a notebook).  However, you would have to
   do the minimal install and copy the data twice.

3) Power down, install the new drive as hdb in addition to the old
   one, reboot to Linux, partition and format the new drive, copy,
   then power down and remove the old drive.  For the middle step, you
   could remove the old drive while leaving it connected
   electrically.  In fact, that would let you give it a twist at
   power-up to help it spin up.

Best of luck!

	- Jim Van Zandt




  parent reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Henry Yen
   ` Rafael Skodlar
 ` Rafael Skodlar
 ` Andor Demarteau
 ` James R. Van Zandt [this message]
   ` Vividata OCR Shop Ron Marriage
     ` Roger Butenuth
       ` John J. Boyer
   ` Ron Marriage
   ` Ron Marriage
     ` Henry Yen
     ` John J. Boyer
       ` Henry Yen
         ` John J. Boyer
           ` lobap
           ` Janina Sajka
     [not found]         ` <Pine.LNX.4.33.0112281403001.2919-100000@localhost.localdom ain>
           ` John G. Heim (26 2-9887)
       ` Janina Sajka
     ` Roger Butenuth
     ` Janina Sajka
       ` Ron Marriage
     [not found]     ` <Pine.LNX.4.43.0112291000490.537-100000@toccata.grg.afb.net >
       ` Brent Harding
         ` Janina Sajka

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=m16FjX2-00012rC@vanzandt.mv.com \
    --to=jrv@vanzandt.mv.com \
    --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).