All of lore.kernel.org
 help / color / mirror / Atom feed
From: whitnl73@juno.com
To: haltec@kvinet.com
Cc: linux-newbie@vger.kernel.org
Subject: Re: cloning a system
Date: Sat, 12 Apr 2003 18:33:33 -0400 (EDT)	[thread overview]
Message-ID: <20030412.195848.8.2.whitnl73@juno.com> (raw)
In-Reply-To: <20030412090618.A197@lnx2.w8mch.ampr.org>

On Sat, 12 Apr 2003, Hal MacArgle/usr/local/bin/tartar wrote:

> Greetings: Years ago when HD's were less than 1gB I used the dd route
> to clone a drive for backup but never had the reason to check and see
> if it was a valid idea.. Later, I think on this list, someone pointed
> out that the dd route was not a good idea - think it may have been
> Lawson IIRC..

If your BIOS doesn't support the Enhanced BIOS call and the packet-call
interface (invented in 1998) lilo is going to have to use CHS
addressing, and differeces in geometry and bad sectors are liable to
play hob with it.
>
> I did note that the cloned drive, even though formatted larger than
> the source drive ended up the "same" size as the source.. I can't
> find my notes but seem to remember using the following:
> dd if=/dev/hda of=/dev/hdc bs=8192
>
> Approaching senility in the brain department I'm hoping someone will
> pick up on this and write a mini-HOWTO as I think it's a needed
> project.. At 0400 this morning I wondered if the best way would be to
> boot the machine with BasicLinux, into ramdisk, and then invoke dd
> from it - presuming Steven put dd in BL.. Not sure.

/usr/local/bin/tartar:
#!/bin/bash
##copy a directory or partition
tar -C "$1" -cOl . | tar -C "$2" -xpf -

mount <source device> /mnt/source
mount <target device> /mnt/targat

tartar /mnt/source /mnt/target
...
if your BIOS is old enough to need a /boot partition, mount it on the
target / (I'll call that /mnt/target) after you copy it, and install
lilo:

lilo -r /mnt/target
>
> Somewhere along my former testing I seem to remember /proc giving a
> problem but that may have been using another routine.. Sometime in
> the future someone may figure a way to RAID our normal brain. <grin>
>
> I hope someone keeps this thread alive..
>
>     Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
>                 Proprietary  Formats  Unacceptable
>

Lawson
--
---oops---



________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2003-04-12 22:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 16:23 Intel 82595FX clone NIC problems James Miller
2003-04-11 16:27 ` James Miller
2003-04-11 17:22 ` Ray Olszewski
2003-04-11 17:52   ` James Miller
2003-04-11 18:31     ` Ray Olszewski
2003-04-11 19:29       ` James Miller
2003-04-11 20:08         ` Ray Olszewski
2003-04-11 20:24           ` James Miller
2003-04-12  9:13           ` ichi
     [not found]   ` <BKEGKPICNAKILKJKMHCAMEDCCGAA.Riley@Williams.Name>
2003-04-11 19:21     ` cloning a system Ray Olszewski
2003-04-12  8:54       ` ichi
2003-04-12 18:27         ` Ray Olszewski
2003-04-12 13:06       ` Hal MacArgle
2003-04-12 22:33         ` whitnl73 [this message]
2003-04-13  8:22         ` ichi

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=20030412.195848.8.2.whitnl73@juno.com \
    --to=whitnl73@juno.com \
    --cc=haltec@kvinet.com \
    --cc=linux-newbie@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.