Subject: | |
From: | |
Reply To: | |
Date: | Sat, 1 Sep 2012 12:45:00 +0200 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Hi Stephen
Nice to hear that kernel-ml-NONPAE works with the LiveCD kickstart files.
I can give you some hints. If I have some more time, I will give it a try, too.
1. prevent kernel from being installed.
Since you have replace kernel with kernel-ml-NONPAE in sl6rolling-live-base.ks, I guess that an other package requires "kernel". And the package "kernel" is
installed as dependency.
The following command (run on the LiveDVD) may give some hints:
rpm -qa | while read rpm; do rpm -q --requires $rpm | grep "^kernel " && echo "*** $rpm ***"; done
Furthermore, does the rpm kernel-ml-NONPAE provides "kernel"?
rpm -q -provides kernel-ml-NONPAE
If this is the case, kernel should not be installed as dependency...?
2. Edit boot menu
The boot menu is customized in sl6rolling-live-base.ks. Look for the script /root/postnochroot-install. In fact $LIVE_ROOT/isolinux/isolinux.cfg is created.
Have a look at /isolinux/isolinux.cfg on your LiveDVD. It should be possible to remove all boot entries for "kernel" in /isolinux/isolinux.cfg with the help of
some "magic" sed-commands in /root/postnochroot-install.
Hope this helps.
BTW. if we (you) get the this working, I will try to add it to the SL Live kickstart files as an option....
Cheers,
Urs
On 08/31/2012 11:01 PM, Stephen Isard wrote:
> I wanted to run sl6 on a non-pae laptop using the ELRepo nonpae ml kernel, and thought that it might work to run the livecd-creator script with Urs Beyerle's
> sl6rolling-livedvd.ks kickstart file, just editing sl6rolling-live-base.ks to include the elrepo-kernel repository and changing the name of the "kernel"
> package to "kernel-ml-NONPAE". I'm pleased to report that this does in fact work; at least the resulting iso boots and starts up normally - I haven't tested
> it extensively.
>
> However, even without a mention of the ordinary sl6 kernel, the script installs the most recent one from sl-security and constructs a rather confusing boot
> menu with four separate kernel entries all labelled nonpae, some of which try to boot the standard pae kernel. This isn't fatal, but it's a bit messy.
>
> Can anyone suggest a way of getting the script to not install the standard kernel, or at least to label the boot menu entries in a more informative way?
>
> Stephen Isard
|
|
|