Whilst this didn't turn out to be a d-i bug, it did occur to me there is
a lack of robustness within d-i, and a real bug here would have been a
nightmare to find. The sequence of events was something like:
* at boot-time, /var/lib/dpkg/info/*.templates are parsed to generate a
Steven Chamberlain, le Thu 21 Aug 2014 14:00:06 +0100, a écrit :
d-i images may be very small, but I haven't found it practical on
embedded systems, which may not even have working VGA or networking;
That's fine. I actually don't usually use VGA or network on servers, but
simply a serial port.
Steven Chamberlain ste...@pyro.eu.org (2014-08-21):
* cdebconf command_get was being called with an option name not found in
its templates.dat; it returns an error message string, but the caller
(main-menu) tries to interpret it as an actual debconf setting before
failing
This indeed looks
Hi,
Any ideas why debian-installer/main-menu would fail to display, with
this error:
WARNING **: Internal error! Cannot find debian-installer/main-menu doesn't
exist in menu.
This is a kfreebsd-i386 d-i image I've built myself from
debian-installer Git and udebs from jessie. I've never seen
Steven Chamberlain ste...@pyro.eu.org (2014-08-20):
Hi,
Any ideas why debian-installer/main-menu would fail to display, with
this error:
WARNING **: Internal error! Cannot find debian-installer/main-menu doesn't
exist in menu.
This is a kfreebsd-i386 d-i image I've built myself from
On 20/08/14 22:38, Cyril Brulebois wrote:
Steven Chamberlain ste...@pyro.eu.org (2014-08-20):
Any ideas why debian-installer/main-menu would fail to display, with
this error:
WARNING **: Internal error! Cannot find debian-installer/main-menu doesn't
exist in menu.
This is a kfreebsd-i386 d
6 matches
Mail list logo
