Hello again,
I have the following problem. My master client (Virtual Machine) uses
/dev/hda as hard disk. The other clients use /dev/sda. If I understand
correctly this shouldn't be a problem because the master script will correct
the necessary files. However for some reason the client hard disk shows up
as /dev/hda (instead of /dev/sda) during the SI installation scripts so that
the master script does not change the files. As soon as I boot into the new
installed kernel, the hard disk is available as /dev/sda again and the boot
(obviously) fails.
My first idea was that this was that the BOEL kernel detects the hard disk
differently than the kernel that the client has, so I configured SI to use
UYOK (without --my-modules switch to support more clients), but I have the
same problem.
Any ideas? I could probably use overrides or change some scripts to work
around this, but I want to avoid ugly hacks if possible.
The clients are Dell Optiplex GX110 with an Ubuntu 7.04 image.
Thanks,
Thomas Krause
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
