On Thu, 2010-08-26 at 18:59 +0200, Holger Levsen wrote:
> Hi,
>
> and I can still not preseed that warning away, that no bootloader has been
> detected...
>
> (Which is bad, as the .32-bpo is installed as part of the base system when
> this has been upgraded by d-i, but before the bootloader installation...)
I think we've discussed this before. linux-base is supposed to be quiet
during a fresh system installation. It uses this heuristic:
# No upgrade work is necessary during a fresh system installation.
# But since linux-base is a new dependency of linux-image-* and did
# not exist until needed for the libata transition, we cannot simply
# test whether this is a fresh installation of linux-base. Instead,
# we test:
# - does /etc/fstab exist yet (this won't even work without it), and
# - are any linux-image-* packages installed yet?
sub is_fresh_installation {
if (-f '/etc/fstab') {
for (`dpkg-query 2>/dev/null --showformat '\${status}\\n' -W 'linux-image-*'`) {
return 0 if / installed\n$/;
}
}
return 1;
}
If you think this gives the wrong answer, please propose an alternative.
Note that if you hack the lenny installer to install a backported kernel
and suppress the libata transition code in linux-base, this may result
in configuration files that use unstable device names. You should
consider using the testing installer instead.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part