Your message dated Thu, 23 Apr 2009 15:31:01 -0500
with message-id <[email protected]>
and subject line Re: Bug#525316: kernel installation script thinks grub is
installed when it isn't (s390 platform, zipl is installed)
has caused the Debian Bug report #525316,
regarding kernel installation script thinks grub is installed when it isn't
(s390 platform, zipl is installed)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
525316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525316
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kernel-package
Version: 11.015
Severity: minor
During installation of a kernel image package created on and for the
s390 architecture by kernel-package version 11.015, I get the
following messages:
========================================================================
Selecting previously deselected package linux-image-2.6.26-custom2-s390.
(Reading database ... 27959 files and directories currently installed.)
Unpacking linux-image-2.6.26-custom2-s390 (from
linux-image-2.6.26-custom2-s390_1_s390.deb) ...
Done.
Setting up linux-image-2.6.26-custom2-s390 (1) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
You already have a ZIPL configuration in /etc/zipl.conf
Do we really want to run bootloader zipl?
Configuring linux-image-2.6.26-custom2-s390
--------------------------------------------
The default boot loader for this architecture is zipl, which is present.
However, you have not explicitly requested the boot loader zipl should be run in
the configuration file /etc/kernel-img.conf, and you seem to have grub
installed, and have set a postinst hook (which is used to hook in grub after a
kernel image installation). At this point, it is perfectly likely that this
system is using grub as a bootloader, and not the builtin default of zipl. If
that is the case, running zipl instead of grub might make the machine
unbootable. I need to know whether to run the default bootloader zipl, or just
let the postinst hook script update grub later. The default is to run zipl.
Run the default bootloader?
========================================================================
The contents of /etc/kernel-img.conf are as follows:
========================================================================
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = yes
do_bootfloppy = no
do_initrd = yes
link_in_boot = yes
========================================================================
I don't know why the installation script thinks that grub is installed.
The /boot/grub directory does not exist, and the package management
system says that grub is not installed.
If I reply "Y" to the install question, the kernel seems to install OK;
but the install script should have just run zipl without asking any
questions, as far as I can tell. The package was created by the
following commands. At the time these commands were issued, there
were two installed kernel images: linux-image-2.6.26-1-s390, and
linux-image-2.6.26-2-s390, both of which are stock Debian kernels,
linux-image-2.6.26-2-s390 was the default kernel, and
linux-image-2.6.26-1-s390 was the currently running kernel.
kernel-package and its prerequisites have been previously installed.
I was logged in as root.
========================================================================
aptitude install linux-source-2.6.26
aptitude clean
cd /usr/src
tar -xjf linux-source-2.6.26.tar.bz2
rm linux-source-2.6.26.tar.bz2
cd linux-source-2.6.26
cp -a /boot/config-2.6.26-2-s390 .config
cd arch/s390/lib
vi div64.c
[change "alr %1,%2\n" to "ahi %1,1\n", file it] <== manual patch
for a bug. See bug number 523942 for details.
cd /boot
aptitude purge linux-image-2.6.26-2-s390 linux-image-s390
ln -s vmlinuz-2.6.26-1-s390 vmlinuz
ln -s initrd.img-2.6.26-1-s390 initrd.img
rm initrd.img.old
rm vmlinuz.old
zipl
cd /usr/src/linux-source-2.6.26
make menuconfig
[Exit without making any configuration changes]
make-kpkg clean
make-kpkg --append-to-version -custom2-s390 --revision 1 --initrd kernel_image
========================================================================
Finally, the kernel image package was installed with
========================================================================
cd ..
dpkg -i linux-image-2.6.26-custom2-s390_1_s390.deb
========================================================================
This seems somewhat similar to bug number 515138.
--- End Message ---
--- Begin Message ---
Version: 12.001
Hi,
In recent versions of kernel-package, this is not an issue --
kernel-package no longer imposes a hard coded policy on users with
respect torunning boot loaders; the users can manage it theseves either
by setting a postinst hook in /etc/kernel-img.conf:
postinst_hook = update-grub
postrm_hook = update-grub
Or, alternately, by dropping scripts into the directories
/etc/kernel/{pre,post}inst.d
manoj
--
Honk if you hate bumper stickers that say "Honk if ..."
Manoj Srivastava <[email protected]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--- End Message ---
