What's the best way to add a custom kernel into autoyast so that the kernel can be installed along with the rest of the OS - instead of installing, replacing the kernel, and rebooting?
I've attempted to add my RPM to our CD-on-the-hard-disk image, but that ran afoul of a checksum (probably because it needed some sort of overall gpg signature - how does one create that for the repository?). I also attempted to set up an additional installation source with just my RPM's in it to be used along with the CD copy, but that gives an error about being "rejected by user" - whoever the "user" is - before it attempts to install any RPM's. I've tried sniffing the network traffic between the server and the machine being installed, but that didn't reveal much more than some file transfers and a lot of setting binary mode and going into extended passive mode. Is there some way I can get a shell on the machine being installed, while it's being installed, so I can try some strace's? I've considered just setting up a chroot script off of autoyast. It seems easier, but there's some internal resistance on that, so it may not be a great option for me. :) Has anyone already done this? I've googled about it a lot, and found a lot of people asking this same question, but I didn't find much in the way of answers. Thanks! -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
