take a look at this one http://relax-and-recover.org/
the RPM is in EPEL rear.noarch
it should give you the best of both worlds.
the problem with using dd is you occasionally get bit drift which can
cause you problems latter. and Rsync wont install grub on your mbr or
format the partitions. rear
On 01/29/2013 10:48 AM, Yasha Karant wrote:
We have a limited, small, number of IEEE 802.3 connected hardware
platform identical workstations to clone -- no 802.11 nor any shared
(remote, distributed) disk storage (at this time). My plan was to get
one fully operational and configured, and
On Wed, Jan 30, 2013 at 10:48:55AM -0500, Lamar Owen wrote:
On 01/29/2013 10:48 AM, Yasha Karant wrote:
We have a limited, small, number of IEEE 802.3 connected hardware
platform identical workstations to clone -- no 802.11 nor any
shared (remote, distributed) disk storage (at this time). My
В Срд, 30/01/2013 в 09:16 -0800, Konstantin Olchanski пишет:
On Wed, Jan 30, 2013 at 10:48:55AM -0500, Lamar Owen wrote:
On 01/29/2013 10:48 AM, Yasha Karant wrote:
We have a limited, small, number of IEEE 802.3 connected hardware
platform identical workstations to clone -- no 802.11 nor
We have a limited, small, number of IEEE 802.3 connected hardware
platform identical workstations to clone -- no 802.11 nor any shared
(remote, distributed) disk storage (at this time). My plan was to get
one fully operational and configured, and then clone the hard drive
image onto the
I've done cloning for many years with tar:
On the source machine, boot from an SL live CD and mount the source's root
file system. Make a tar file of this system with a command like:
cd /mnt/wherever
tar -cSf - . | ssh someuser@somewhere 'cat mysystem.tar'
Then, on the target, boot the live
On 01/29/2013 09:56 AM, Steve Gaarder wrote:
I've done cloning for many years with tar:
On the source machine, boot from an SL live CD and mount the source's
root file system. Make a tar file of this system with a command like:
cd /mnt/wherever
tar -cSf - . | ssh someuser@somewhere 'cat
There are advantages and disadvantages of the methodology you use. I
have the following questions:
1. The SL live CD presumably requires a manual configuration of the
network -- this university uses /22 IPv4 subnets (we have not made the
full conversion to IPv6, although we support IPv6
On 01/29/2013 10:43 AM, Yasha Karant wrote:
There are advantages and disadvantages of the methodology you use. I
have the following questions:
1. The SL live CD presumably requires a manual configuration of the
network -- this university uses /22 IPv4 subnets (we have not made the
full
On 01/29/2013 08:55 AM, Mark Stodola wrote:
On 01/29/2013 10:43 AM, Yasha Karant wrote:
There are advantages and disadvantages of the methodology you use. I
have the following questions:
1. The SL live CD presumably requires a manual configuration of the
network -- this university uses /22
target
hard drive. The hard drive on A is /dev/sda, call it Ahd. A is shut down
power off. Bhd is installed into an available bay on A, A is booted, and
Bhd appears as /dev/sdb in A. Using dd on A, clone /dev/sda to /dev/sdb .
Mount on A the partition of /dev/sdb that contains /etc (there
and configured, and then clone the hard
drive image onto the remaining machines one hard drive at a time.
I clone SL systems using both methods - dd (mdadm raid1, actually) and
rsync.
The down side of cloning with dd is that all UUIDs become cloned (root
filesystem, etc)
and that can cause some
On 2013/01/29 10:20, Bluejay Adametz wrote:
target
hard drive. The hard drive on A is /dev/sda, call it Ahd. A is shut down
power off. Bhd is installed into an available bay on A, A is booted, and
Bhd appears as /dev/sdb in A. Using dd on A, clone /dev/sda to /dev/sdb .
Mount on A the
(at this time). My plan was to
get one fully operational and configured, and then clone the hard
drive image onto the remaining machines one hard drive at a time.
I clone SL systems using both methods - dd (mdadm raid1, actually) and
rsync.
The down side of cloning with dd is that all UUIDs become
14 matches
Mail list logo