Bug#99079: confusing messages
On Tue, May 29, 2001 at 12:35:06AM +0200, Marcello Nuccio wrote:
> Package: boot-floppies
> Version: 2.3.3
> Severity: normal
>
> (sorry for my broken english, please ask if it's not clear)
>
> During the installation, a few warnings informs the user that empty
> files /etc/ld.so.conf, lilo.conf and exim.conf were created.
> >From the messages, it's not clear if this is a problem and if some
> action should be taken.
I believe there was some confusion about what warnings debootstrap
should generate, and how dbootstrap should interpret them. This
is either fixed, or soon will be.
> Later, just before the time zone selection dialog, the error
> "could non stat localtime" was displayed for a couple of seconds.
> Anyway the installation proceeds without problem until the reboot.
This has been fixed in CVS.
> During reboot, I first noticed that the kernel (2.2.19) was compiled
> with gcc 2.7.2.3: this is no more the recommended version, use egcs
> or gcc-2.95 instead!
If this is indeed an issue, it is a kernel bug.
> After boot end, the following message is displayed several times:
> /bin/sh: /sbin/termwrap: No such file or directory.
> /bin/sh: exec: /sbin/termwrap: cannot execute: No such file or directory.
> INIT: Id "1" respawning too fast: disabled for 5 minutes.
This has since been fixed as well.
> I then switched to tty2 and executed "dpkg-reconfigure base-config"
> (I got this from /etc/inittab). I was able to complete base installation
> (actually a network installation through my home-lan connected to the
> Internet via a dial-up connection). The only problem, was after the
> insertion of the root password and the normal user account: the program
> seems freezed for a few minutes. Launching top on tty3, I discovered
> that many processess were executed in sequence:
>
> sh -e /var/lib/dpkg/info/base-config.config reconfigure 0.61
> egrep -q ^.*:.*:NUMBER /etc/passwd
> (with a different NUMBER every time)
>
> anyway, after a few minutes the installation continues.
This has since been optimized.
> hope this helps,
> marcenuc
I think that only the kernel problem is still an issue. All the
rest should be fixed with the next release. Feel free to file a
bug against the kernel package if you wish.
Matt
Reply to: