It's coming back to me, because I'm pretty sure I had gotten this to work at one time... I put a hard link in my /tftpboot directory to the images in /usr/share/systemimager/boot/x86_64/myimage/kernel and initrd.img and verified those files listed in /tftpboot are indeed the same size. Then I booted and once again I see BusyBox so what I'd line to know is where it even came from! Furthermore when I do ls /dev I don't even see sda, which I know is there. -mark
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 > ------------------------------------------------------------------------- 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 sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
