dann frazier wrote: > On Fri, Mar 16, 2007 at 12:28:05AM -0700, Bernard Li wrote: >> Hi dann: >> >> On 3/14/07, dann frazier <[EMAIL PROTECTED]> wrote: >> >>> This is probably a distro-specific udev config, so kernel-rev only >>> isn't enough info. Right answer is to use the distro's udev config. >> I guess this would work with UYOK, but is there a way to also "solve" >> this for the default ramdisk that we ship with SystemImager? > > for the benefit of the list, my suggestion on IRC was to use a recent > version of udev in the ramdisk and transfer udev config files from the > image before starting it up. >
Dann, the idea to copy the distro specific udev configuration is great, but it's not so simple to realize. The main problem is that potentially a generic udev config can require a lot of packages, and we can't include all the possible dependencies into the initrd or in the BOEL binaries... moreover a lot of udev configs seem to be based on specific distro configuration paths (like /etc/sysconfig for RH and SuSE), so we should find a way to resolve also these kind of dependencies... IMHO the simplest way to fix the disk naming issue is a post-install script that detects from the udev config of the installed image which "naming style" will be used. Depdending on this naming style the script fixes /etc/fstab, /boot/grub/menu.lsf (or /etc/lilo.conf), etc... Regards, -Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
