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

Bug#582776: marked as done (initramfs-tools: pointless generation of an initrd for initrd-free custom kernels)

Your message dated Wed, 30 Mar 2011 13:39:24 +0200
with message-id <20110330113924.GB14386@stro.at>
and subject line Re: Bug#582776: initramfs-tools: pointless generation of an initrd for initrd-free custom kernels
has caused the Debian Bug report #582776,
regarding initramfs-tools: pointless generation of an initrd for initrd-free custom kernels
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 owner@bugs.debian.org
immediately.)


-- 
582776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582776
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: initramfs-tools
Version: 0.94.4

While installing a locally-built kernel (which doesn't require an initrd), I
found that /etc/kernel/postinst.d/initramfs-tools was nevertheless generating
an initrd for that kernel.

This causes breakage here. I'm using lilo and a slightly-modified
version of the example symlink_hook script provided by kernel-package; if an
initrd is present, the symlink name is different. (I'm using the symlinks so
that I don't have to edit lilo.conf.)

(I also have a stock kernel installed for occasional testing purposes.
Mostly, I just use my custom kernels.)

I find this sufficient to handle packages generated by kernel-package:

--- /etc/kernel/postinst.d/initramfs-tools~	2010-04-08 04:53:09.000000000 +0100
+++ /etc/kernel/postinst.d/initramfs-tools	2010-05-23 15:06:44.114662432 +0100
@@ -11,6 +11,10 @@
 	if [ -n "${KERNEL_PACKAGE_VERSION}" ]; then
 		bootdir=$(dirname "$2")
 		bootopt="-b ${bootdir}"
+		# check whether an initrd is needed
+		if ! grep -q '^CONFIG_BLK_DEV_INITRD=y$' /boot/config-"$1"; then
+			exit 0
+		fi
 	else
 		# official Debian linux-images take care themself
 		exit 0

-- 
| Darren Salt            | linux at youmustbejoking | nr. Ashington, | Toon
| using Debian GNU/Linux | or ds    ,demon,co,uk    | Northumberland | back!
| + http://www.youmustbejoking.demon.co.uk/ & http://tartarus.org/ds/

If you cast your bread upon the waters, it will return soggy.

--- End Message ---
--- Begin Message --- 
Version: 0.98

On Sun, 23 May 2010, Darren Salt wrote:

> While installing a locally-built kernel (which doesn't require an initrd), I
> found that /etc/kernel/postinst.d/initramfs-tools was nevertheless generating
> an initrd for that kernel.
> 
> This causes breakage here. I'm using lilo and a slightly-modified
> version of the example symlink_hook script provided by kernel-package; if an
> initrd is present, the symlink name is different. (I'm using the symlinks so
> that I don't have to edit lilo.conf.)
> 
> (I also have a stock kernel installed for occasional testing purposes.
> Mostly, I just use my custom kernels.)
> 

fixed in Squeeze initramfs-tools by Stephen Powell:
postinst hook: respect INITRD variable


thus closing, thank you for the report.

-- 
maks

--- End Message ---
Reply to: