Frans Pop wrote:
Could you check with the following command that the initrd created in your
daily builds indeed contains the wrong devices:
$ zcat tmp/cdrom_gtk/initrd.gz | cpio -i --list -v | grep dev/
[EMAIL PROTECTED]:~/src/d-i/installer/buildzcat tmp/cdrom_gtk/initrd.gz | cpio
-i --list
tags 401603 + pending
# lowering severity as the fix is already implemented for daily builds
severity 401603 important
thanks
On Wednesday 06 December 2006 10:05, Joey Hess wrote:
If I run the build by hand (in fakeroot), it's crw-r--r-- all the way
through, and is ok in the initrd. The next
On Monday 04 December 2006 20:57, Frans Pop wrote:
With some help from Colin, I managed to find as most probably cause
that /dev/console and /dev/null have incorrect file attributes in the
gtk initrd:
I cannot reproduce this error on my own machine, so I suspect it is
something local on
Package: debian-installer
Severity: serious
Since about a week (switch to 2.6.18?) the installgui option on netinst
CDs fails to boot correctly. It fails to enable the framebuffer and you
end up in a messed up newt interface.
It also fails to correctly respond to a BOOT_DEBUG=3 boot parameter
4 matches
Mail list logo
