Linux Format forums

Re: Cloning an install to a different CPU

kgolding — Thu Mar 07, 2013 9:40 pm

Author: kgolding

Posted: Thu Mar 07, 2013 9:40 pm

Thanks nelz - I think just deleting the rules file will do the trick for me.

Kevin

Re: Cloning an install to a different CPU

nelz — Thu Mar 07, 2013 9:39 pm

Author: nelz

Posted: Thu Mar 07, 2013 9:39 pm

That's easily fixed. Either delete /etc/udev/rules.d/70-persistent-net.rules or use the latest udev which no longer names network interfaces like this.

Re: Cloning an install to a different CPU

kgolding — Thu Mar 07, 2013 9:26 pm

Author: kgolding

Posted: Thu Mar 07, 2013 9:26 pm

Hello Guy, the servers run headless so there is no dependency on graphics - thankfully!

I expect the biggest pain will be udev stealing the network eth0 and eth1 devices as being on the Master and then allocating eth1 & eth2 to the new PCs (as they all have twin network cards).

Kevin

Re: Cloning an install to a different CPU

guy — Thu Mar 07, 2013 11:09 am

Author: guy

Posted: Thu Mar 07, 2013 11:09 am

What about other device-specific things that might be rolled into the install, such as display drivers? Could that cause problems?

Re: Cloning an install to a different CPU

kgolding — Tue Mar 05, 2013 12:08 pm

Author: kgolding

Posted: Tue Mar 05, 2013 12:08 pm

So it shouldn't be an issue then

Thank you for the reassurance.

Re: Cloning an install to a different CPU

nelz — Tue Mar 05, 2013 9:52 am

Author: nelz

Posted: Tue Mar 05, 2013 9:52 am

No, because all the software will be compiled for a generic x86 or x86_64 CPU. The only time this becomes an issue is if you have compiled your own software with more CPU-specific flags.

Cloning an install to a different CPU

kgolding — Tue Mar 05, 2013 9:21 am

Author: kgolding

Posted: Tue Mar 05, 2013 9:21 am

Hello,

I want to create a Master installation of a Debian based system, and to then clone it to new PC's as and when required.

As I'll only be doing this once or twice a month, my plan is:

1. Create a Master installation in a Virtual Machine which I can keep updated.
2. Boot new PC's using a live CD, partition the drives, set up RAID and then rsync the Master installation to the new PC.
3. Reboot the new PC and make any minor configuration changes.

Once the new PC's have left me for production use, they will not need to be upgraded save the usual apt-get updates.

My concerns is that my VM server has an AMD CPU, but the new PC's are likely to be Intel CPU's - will this cause a problem?

All the best,

Kevin