Dan Stromberg wrote:
Dan Stromberg wrote:
Hi folks.
I'm having some trouble with a SLES 10.1 install, but we'll be doing the same thing with openSUSE 10.3 shortly.
Basically, we're adding a bunch of RPM's via a post install script, and some of those RPM's are miffed that the kernel we're installing with isn't the same as the kernel that we end up with after the install.
So we're wanting to change our installs to use the same kernel, to see if we can get those RPM's added via the same mechanism we're using for most of our RPM's (in a post install chroot script), rather than needing to add them via an rc script.
However, when I changed the kernel and initrd for the installer to be the as what we're installing, the installer no longer appears to be running. Instead, we get a grub menu via PXE like usual, but the installer just boots to the previous-installed OS on disk.
We were using a kernel and initrd from off the CD image, and that was working fine. All I changed was the kernel and initrd.
Is there some kernel command line option I need to add for a more generic kernel, to make it usable for during an install?
Thanks!
BTW, our pxelinux.cfg has, for example:
label SLES-2900 kernel vmlinuz-2.6.16.46-0.12-smp append initrd=initrd-2.6.16.46-0.12-smp install=ftp://10.3.163.253/ftp10-2/sles10-sp1/CD1/ splash=silent showopts console=tty0 autoyast=ftp://10.3.163.253/ftp10-2/SLES-10.1-Dell-2900-autoyast.xml
Is there something missing to make a general purpose kernel usable for installs?
I opened up and compared some initrd's, and found that the one for installing is pretty different, which is probably why a generic initrd is giving a generic boot, not an install. I think we're probably going to just want to install some of our rpm's from an rc script. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org