Re: Why xenU in grub.conf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, tournesol and all

The reason is that kernel-xenU of FC use the same post-intall-tools 
as native kernel. (Probably kdump also have the same issue.)
I also think this is unhappy.

I think the better %post is like the below.
(this is a sample code, not tested.)
If necessary, I'll make a patch. :-)

-------kernel.spec---------
%post xenU
[ ! -x /usr/sbin/module_upgrade ] || /usr/sbin/module_upgrade %{rpmversion}-%{release}-xenU
/sbin/new-kernel-pkg --package kernel-xenU --mkinitrd --depmod --noconfig --install %{KVERREL}xenU
[ ! -x /sbin/ldconfig ] || /sbin/ldconfig -X
----------------

--- new-kernel-pkg in mkinird -----

diff -uNrp mkinitrd-5.0.41/grubby/new-kernel-pkg mkinitrd-5.0.41.new/grubby/new-kernel-pkg
--- mkinitrd-5.0.41/grubby/new-kernel-pkg       2006-03-31 08:15:19.000000000 +0900
+++ mkinitrd-5.0.41.new/grubby/new-kernel-pkg   2006-06-14 01:01:48.000000000 +0900
@@ -81,7 +81,7 @@ usage() {
     echo "       [--initrdfile=<initrd-image>] [--depmod] [--rmmoddep]" >&2
     echo "       [--kernel-args=<args>] [--remove-args=<args>]" >&2 
     echo "       [--banner=<banner>] [--multiboot=multiboot]" >&2
-    echo "       [--mbargs=mbargs] [--make-default]" >&2
+    echo "       [--mbargs=mbargs] [--make-default] [--noconfig]" >&2
     echo "       <--install | --remove | --update> <kernel-version>" >&2
     echo "       (ex: `basename $0` --mkinitrd --depmod --install 2.4.7-2)" >&2
     exit 1
@@ -336,6 +336,9 @@ while [ $# -gt 0 ]; do
        --make-default)
            makedefault="--make-default"
            ;;
+       --noconfig)
+           nocfg=1
+           ;;
 
        --package)
            if echo $1 | grep '=' >/dev/null ; then
@@ -422,8 +425,8 @@ if [ ! -x $grubby ] ; then
 fi
 
 
-[ -n "$grubConfig" ] && [ -f "$grubConfig" ] && cfgGrub=1;
-[ -n "$liloConfig" ] && [ -f "$liloConfig" ] && cfgLilo=1;
+[ -n "$grubConfig" ] && [ -f "$grubConfig" ] && [ -n $nocfg ]&& cfgGrub=1;
+[ -n "$liloConfig" ] && [ -f "$liloConfig" ] && [ -n $nocfg ]&& cfgLilo=1;
 
 # if we have a lilo config on an x86 box, see if the default boot loader
 # is lilo to determine if it should be run

Best Regards,

Akio Takebe

>Hi forks
>
>Why xenU in grub.conf ? for what ?
>
>
>title Fedora Core (2.6.16-1.2122_FC5xenU)
>root (hd0,0)
>kernel /vmlinuz-2.6.16-1.2122_FC5xenU ro root=/dev/VolGroup00/LogVol00
>rhgb quiet
>
>
>
>
>
>
>
>
>
>tournesol
>
>--
>
>Fedora-xen@xxxxxxxxxx
>https://www.redhat.com/mailman/listinfo/fedora-xen

--

Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen

[Index of Archives]     [Fedora General]     [Fedora Music]     [Linux Kernel]     [Fedora Desktop]     [Fedora Directory]     [PAM]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux