Mitch Sako wrote: > I'm getting this message when I run si_prepareclient. I'm using > released 4.0.2-1 RPMs. Monolithic (no modules or initrd) kernel, UYOK > configuration. Do I need a dummy initrd? > > > Starting or re-starting rsync as a daemon..... > done! > This client is ready to have its image retrieved. You must now run > the "si_getimage" command on your imageserver. > Your client has been successfully prepared. Boot kernel (copied from > this Linux distribution) and an initrd.img (generated by the > initrd_template package) can be found in /etc/systemimager/boot. > > Automatically create configuration file for systemconfigurator: > >> /etc/systemconfig/systemconfig.conf > FATAL: unable to detect an initrd for "2.6.24.3 "! > WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf > (needed by systemconfigurator)
Well... yes, this is a quite rare configuration. I think just creating an empty file in /boot/initrd.img-2.6.24.3 would be enough. But I've never tested it (in particular during the first reboot I don't know if your boot loader likes to load an empty initrd). Let us know... -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
