The attached patch fixes the problem with imaging where you
boot the node using an initrd.img created by UseYourOwnKernel.pm.
The problem is
parted reports that the partition you're (re)-create is being used, causing
SystemImager to bail. This is potentially caused by the fact that the
/dev/ files are rsynced from the live system to the initrd.img. I have
replaced this by the MAKEDEV command which creates the special devices in
/dev.
Currently I am
only creating devices for hda and sda, I am probably missing cciss and a bunch
others, so if you can give me a list, that'd be great (it doesn't hurt to create
more devices than is necessary here...). Also, it is possible to do
MAKEDEV hd sd (and it'll create everything: a, b, c, ...)
Brian, can I
check this into 3.6.x?
Thanks,
Bernard
Index: lib/SystemImager/UseYourOwnKernel.pm
===================================================================
--- lib/SystemImager/UseYourOwnKernel.pm (revision 3394)
+++ lib/SystemImager/UseYourOwnKernel.pm (working copy)
@@ -92,9 +92,9 @@
close(FILE);
#
- # Copy over /dev
+ # Use MAKEDEV to create special devices for hard disks
#
- $cmd = qq(rsync -a /dev/ $staging_dir/dev/);
+ $cmd = qq(MAKEDEV -d $staging_dir/dev hda sda);
!system( $cmd ) or die( "Couldn't $cmd." );
#
