nstead. The reason is the lack of flexibility in
the automatic scripts, like e.g. missing serial support in extlinux. Or
the ability to keep a few special kernels in /boot without adding all of
them to the boot menu.
Might be just me. Just wanted to register an interest in keeping the
link_in_boot fe
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
On Sat, 22 Sep 2007 16:29:13 +0200, Ralf Neubauer <[EMAIL PROTECTED]> 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.
Ben Hutchings writes:
> This has nothing to do with where the kernel images are (they are always
> installed in /boot), but only to do with where the symlinks are created.
> The default is to create them in /, but I recall there is an option (now
> deprecated) to create them in /boot.
Not relat
On Sun, 2011-02-13 at 20:24 +0100, Bjørn Mork wrote:
> Ben Hutchings writes:
>
> > This has nothing to do with where the kernel images are (they are always
> > installed in /boot), but only to do with where the symlinks are created.
> > The default is to create them in /, but I recall there is an
5 matches
Mail list logo
