Date: Wed, 29 Nov 2000 07:45:40 -0800 From: Ron 'The InSaNe One' Rosson <insane@lunatic.oneinsane.net> To: freebsd-isp@freebsd.org Subject: Re: Drive Copy Message-ID: <20001129074540.A33079@lunatic.oneinsane.net> In-Reply-To: <Pine.BSF.4.10.10011290844500.13585-100000@bsdie.rwsystems.net>; from jwyatt@rwsystems.net on Wed, Nov 29, 2000 at 09:37:59AM -0600 References: <767440343.20001129142712@aexis-telecom.it> <Pine.BSF.4.10.10011290844500.13585-100000@bsdie.rwsystems.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I hate adding a me too.. but I am lurking and hoping for an answer.. I
have 2 identical machines getting ready to be deployed in two different
places and I would love to only have to tweak one system and then just
copy the drive over to the other systems drive.
TIA
James Wyatt (jwyatt@rwsystems.net) wrote:
> On Wed, 29 Nov 2000, Massimo Fubini wrote:
> > Use dd. For more information man dd.
> > For example if you want to copy a single partition you do:
> > dd if=/dev/origin_partiton of=/dev/destination_part
> >
> > It is easy and powerful.
>
> And incomplete. I know you can connect the drive, boot, and use the
> /stand/sysinstall utility to carve the drive up into partitions for
> filesystems and swap areas. If you want, it can newfs partitions so you
> can mount the new partitions and user tar/cpio to transfer files. What do
> you do to init the swap and set the boot sector/MBR stuff?
>
> While this stuff is fairly "simple" in that it requires just a few steps,
> it is pretty arcane to many folks, especially new unix admins. The risk of
> toasting your "real" drive is very nonzero as well. Since new drives are
> almost always larger, just dd-ing things is wasteful. Using dd requires
> that you understand the various disk devices fairly well too.
>
> This stuff is easy for many folks on this list, but not so obvious to the
> original poster. I'm sure we can get together and help him (and other
> lurkers) more than a "RTFM for dd, and it's easy". I've included a few of
> the other steps (sysinstall) above, but don't have all the answers. Can
> someone point to more information or reply to the list with more detailed
> steps and techniques?
>
> I've usually had to install FreeBSD (usually a newer version) onto the new
> drive, hand-build the devs (MAKEDEV or *careful* use of sysinstall), redo
> local changes and rebuild ports, and tar/cpio-transfer data files. - Jy@
>
> btw: Even dd is usually somewhat faster with a 'bs=100k' or so.
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isp" in the body of the message
>
--
------------------------------------------------------------------------------
Ron Rosson ... and a UNIX user said ...
The InSaNe One rm -rf *
insane@oneinsane.net and all was /dev/null and *void()
------------------------------------------------------------------------------
Providing computer solutions for the mentally impaired.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001129074540.A33079>