On Thu, Aug 26, 2004 at 08:24:31AM +0200, Sven Luther wrote: > On Thu, Aug 26, 2004 at 01:41:28AM -0400, Rick Thomas wrote: > > > > > > I noticed that near the end, the script does an e2fsck of the > > "root.img" file. This seems to indicate that the image is > > completely hosed, and e2fsck responds by (essentially) resetting it > > to an empty ext2 filesystem. This explains why the root.img is the > > way it is (empty except for "lost+found"). But it doesn't explain > > why the image filesystem is broken in the first place.
Well, now that we know this was caused by genext2fs, there's finally some progress. I won't be able to test boot floppies from friday to monday, but if the monday floppies are created with the fixed genext2fs, I'll continue testing then. > Do you know if the 2.6 floppies root.img suffer from the same problem ? Could > you check ? If I remember correctly, the 2.6 images use a compressed ram filesystem which I can't mount on any of my machines. I don't know if that's the result of a hosed filesystem or that I need to reconfigure my kernel. I couldn't mount them from a fresh sarge install with both the 2.4 and the 2.6 kernel. Am I doing something wrong, could someone verify if the 2.6 floppies are mountable? Also, the 2.6 floppies only give a tux with red cross after a while, is there any progress on that front? Best regards, Wouter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
