Hey folks, So I guess I sorta solved my issue of yesterday... Well, at least I've gotten further.
Here's my situation. I used the mkbootpackage to make myself a directory (ben5) in /usr/share/systemimager/i386/boot/ that contains kernel, initrd.img, and boel-binaries.tar.gz. I compiled my own kernel because the one that came with the SI suite just didn't do it for me at all. On a prosppective client, I install fedora and then lilo, and get it so it can boot. I use the same kernel I've got on my golden server on this client to verify that the kernel is compiled well enough to boot the machine. I run 'updateclient --autoinstall --server myserver' and it goes and gets all the relevant files. I muck with lilo.conf a bit (b/c the one as generated doesn't work right - another story) and reboot. My boot gets a ways along, but when it gets to an rsync line, it segfaults. The return code of rsync's segfault is 139. When I poked around a bit, I found that ping also segfaults, same exit code. Because of these segfaults, certain sections of the boot script don't finish, and I'm left with a system that fauls its install. Any thoughts? -ben -- Ben Hartshorne email: [EMAIL PROTECTED] http://ben.hartshorne.net
pgplJtvUVxpgM.pgp
Description: PGP signature
