QubesOS/qubes-linux-kernel
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Do not create the failsafe boot entry anymore

Browse Source 
I don't think we need it anymore with the new Dom0 kernel --
it was mainly introduced so that people could easily get
around not-working-nouveau driver in the previous Dom0 kernel,
but it seems to work just fine out of the box with this new kernel.

Having this additional boot traget just introduces some mess,
that can confuse users. And users can still boot using original
Fedora kernel if something goes wrong.
This commit is contained in:
Joanna Rutkowska 2010-06-18 12:42:06 +02:00
parent fb58bbd020
commit 40bf8407f1
1 changed files with 2 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
kernel.spec
View File

@ -241,18 +241,12 @@ exit 1
fi
%post
/sbin/new-kernel-pkg --mkinitrd --depmod --dracut\
--banner="Dom0 failsafe boot (no Xen) for %{kernelrelease}"\
--install %{kernelrelease}
/sbin/new-kernel-pkg --package %{name}-%{kernelrelease} --dracut\
/sbin/new-kernel-pkg --package %{name}-%{kernelrelease}\
--mkinitrd --depmod --dracut\
--kernel-args="max_loop=255"\
--multiboot=/boot/xen.gz --banner="Qubes"\
--make-default --install %{kernelrelease}
#/sbin/new-kernel-pkg --remove-args=rhgb --update %{kernelrelease}
/sbin/new-kernel-pkg --remove-args=quiet --update %{kernelrelease}
if [ -e /boot/grub/grub.conf ]; then
# Make it possible to enter GRUB menu if something goes wrong...
sed -i "s/^timeout *=.*/timeout=3/" /boot/grub/grub.conf