If I understand correctly udev will use the kernel name by default, when no matching rule with a NAME action is found, but I can't find any rule that matches hard disks and reNAMEs a device node, neither in the systemimager default, nor in my ubuntu client. And as I already said they are using the same kernel. So by using the same kernel the original name should already be the same and never be changed by udev.
Am I missing something here? And speaking of "ugly hacks", instead of replacing everything in rules.d/*, couldn't I just add a rule like: KERNEL=="hda", NAME="sda" KERNEL=="hdb", NAME="sda" to my (virtual) golden clients udev-rules, so that the original image already has the "correct" devices? If this works I believe this would be a better hack (tm), since it would only affect my golden client and it would make it more similar to the real clients. Thanks, Thomas Krause -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Andrea Righi Gesendet: Freitag, 20. Juli 2007 12:49 An: [email protected] Betreff: Re: [sisuite-users] Yet another SDA/HDA problem Thomas Krause wrote: > 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 shouldnt 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 /dev/[hs]da naming depends on the udev configuration. Theoretically to fix this problem the SI environment should be able to use the same udev configuration of your image. Unfortunately it's not so easy to find a solution for this problem. A simple copy of /etc/udev/ into the initrd.img is not a clean solution (ugly hack), because the udev configuration of your image could use binaries, packages, etc that will be not available from the busybox environment. Maybe you could try to replace all the occurrences of "hd" with "sd" in /usr/share/systemimager/boot/i386/standard/initrd_template/etc/udev/rules.d/ * (saving the original files!) and re-create a kernel+initrd.img with si_mkbootpackage... My $0.02... -Andrea ------------------------------------------------------------------------- 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 ------------------------------------------------------------------------- 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
