The best place to "fix" this is in the system you're using as a source for the clone. What good is cloning, if, after every clone, you have to go in and make hand modifications?
Change your source system to use by-path. Then you won't have a problem with any of the clones. And, since you're just cloning, and can't get through the second boot, scratch this clone and recreate it with the corrected source. It's not worth fighting, when you need to fix the source system anyway. -- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 12/8/08 4:17 PM, "Tom Duerbusch" <[EMAIL PROTECTED]> wrote: > I hit the same problem as others (reference back in November), but I knew that > a solution already exists.. > > OK, so where is it? As in on your website? > > Tom Duerbusch > THD Consulting > > "You need to boot a rescue system with the disks for the problem system > attached and change /etc/fstab to by-path. We wrote a script to do this for > you -- check sinenomine.net for a copy." > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
