Mark Seger wrote: > I should probably know better but I don't, even though I've been using > SystemImager for a very long time and now I'm faced with a kernel that > can't see my hard drive and so need to get UYOK working. The > documentation implied that it just worked yet SI insists on loading > BusyBox. Is there some manual step I need to do in which to tell the it > to load MY kernel and initrd instead of BusyBox? > -mark
Mark, probably you misunderstand something... UYOK is a kernel, BusyBox is a set of unix utilities in userspace. Both the standard BOEL and UYOK kernels use BusyBox to create a UNIX environment into the initrd.img, so in practice you must always see the BusyBox shell. But let's focus on the real problem: you don't see your /dev/sda. Do you know which particular disk controller is installed in your client? Anyway, I would suggest to try also the BOEL kernel from SI 4.0.2 and re-create the autoinstall script with --autodetect-disks. -Andrea ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
