In order to avoid GRUB reinstallation problem you should create GHOST boot diskette with -id option or choose it in GHOST option tab (options--> IMAGE/TAPE---->IMAGE DISK switch ). -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx]On Behalf Of Brian D. McGrew Sent: Friday, January 21, 2005 5:35 PM To: General Red Hat Linux discussion list Subject: RE: Imaging Software/Hardware for use with Redhat WS Version 3 I agree with Ed 100%, however, I have successfully used Ghost 2003 to replicate Redhat 7.3 onto many identical Dell boxes. The only problem that I ran into was after the restore was done, I had to boot from the CD in rescue mode, mount / and /boot and reinstall grub (I forget the command line option I used) but other than that, it did work. -brian Brian D. McGrew { brian@xxxxxxxxxxxxx || brian@xxxxxxxxxxxxxxxxxxx } --- > YOU! Off my planet! -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Ed Wilts Sent: Friday, January 21, 2005 7:30 AM To: General Red Hat Linux discussion list Subject: Re: Imaging Software/Hardware for use with Redhat WS Version 3 On Fri, Jan 21, 2005 at 02:43:36PM +0000, Andrew.Bridgeman@xxxxxxxxxxxxxx wrote: > I have now built a standard Redhat WS version 3 machine that runs all of > our cae and cad software. I need to put the same image of this machine on > to over 20 more new machines that are arriving Monday. I have a copy of > Norton Ghost 2003 and Version 9 but i am not sure how well it will image > Redhat. > Can anyone recommend a way of imaging my machines that they have used in > the past whether it is software or hardware imaging, any help is much > appreciated. The recommended approach is to build the systems with Kickstart. That guarantees that you'll get the right kernel and other packages (e.g. glibc) for the right architecture over time - for example, if you image an P4-based system to an Athlon-based system, you probably won't even boot (I had the same issue with a Ghost image on my Windows desktop at work - a hyperthreading-enabled image wouldn't boot on my P3). If a vendor throws a different Ethernet adapter at you, you'll still work with a Kickstart'ed system. If you image and the adapter changes - and vendors have been known to change Ethernet adapters even within the same product line - your network may not start. Ditto with graphics cards. Kickstarts can be done fairly quickly over the network and can include a mix of vendor-provided and your own packages. You have total control over what the target systems look like. If you really want to image the systems, you can look at Mondo Rescue - it can make an exact copy of your system that can then be restored to another system, even if the disk sizes are different. However, it won't do anything about fixing up the hardware inconsistencies, network addressing, etc. http://www.mondorescue.org Setting up a Kickstart-ready environment is a bit of work up front but it will last you through many more hardware generations than a disk-image environment will. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:ewilts@xxxxxxxxxx Member #1, Red Hat Community Ambassador Program -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list *********************************************************************************** Information contained in this email message is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the postmaster@xxxxxxx and destroy the original message. *********************************************************************************** -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
