Re: Bug#425056: strange default for link_in_boot in config script
On Sat, 22 Sep 2007 16:29:13 +0200, Ralf Neubauer <ralf@strcmp.de> said:
> I have the same problem with linux-image-2.6.21-2-686 In
> /var/lib/dpkg/info/linux-image-2.6.21-2-686.config I found the
> suspicious lines
>> Predefined values:
> my $version = "2.6.21-2-686";
> my $link_in_boot = "YESB"; # Should be empty, mostly
> my $no_symlink = ""; # Should be empty, mostly
> linux-image-2.6.18-5-686.config still contains
>> Predefined values:
> my $version = "2.6.21-2-686";
> my $link_in_boot = ""; # Should be empty, mostly
> my $no_symlink = ""; # Should be empty, mostly
This is likely because something went and ran
sed -e 's/=I/$(INITRD)/g' on the postinst template; without first
running sed -e 's/=IB/$(link_in_boot)/g'
> kernel-img.conf(5) (from etch) says
> link_in_boot
> Set to Yes if you want the symbolic link to the kernel
> image, namely, vmlinuz in /boot rather than the default
> /. The old, and very confusing, name image_in_boot is
> deprecated, since it is the symbolic link that is
> usually being relocated. Defaults to No.
> Has the default changed? I can't image a reason for doing this, as
> only people still using lilo should be affected at all. There was no
> mention of a changed default in any changelog or NEWS I searched.
> Is this a kernel-package bug?
Unlikely. kernel-package always runs the sed substitutions in
order.
manoj
--
The flow chart is a most thoroughly oversold piece of program
documentation. Frederick Brooks, "The Mythical Man Month"
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: