Hi, Christian. Thanks so much for the bug report. Can you provide a little more information about the system where you have built the debirf image, and the system on which you are having trouble booting it? In particular, can you provide:
- version of debirf used to build the image - architecture of build machine - architecture and release of the debirf image - any notable output during the debirf build log In fact, if you could pipe the entire build log to a file and attach it to this bug report, that might be useful. On Sat, Dec 26, 2009 at 10:05:43PM +0100, Christian Svensson wrote: > Screenshots (sorry, HTTPS certificate is invalid): > https://denzel.cmd.nu/~bluecommand/debrif-freeze.png > https://denzel.cmd.nu/~bluecommand/debrif-freeze-cont.png > > Between the first and second screenshot there is a delay of about 5-6 > minutes. I realize it might be a little more difficult, but text pastes of the output are much easier for reference purposes, if you can swing it. I gather that these are the two lines before the freeze: ###### Starting enhanced syslogd: rsyslogdCan't open or create /var/run/syslogd.pid. Can't write pid. ###### and this is the first line that appears when the boot continues?: ###### already started. ###### It looks like /etc/rc2.d/S01bootlogs is also having trouble accessing some files in /var/run (/var/run/motd, /var/run/dmesg). I wonder if some more cleanup of the image is needed before building the initrd. Thanks in advance for the extra info. jamie.
signature.asc
Description: Digital signature
