On Tue, Jun 01, 2004 at 10:21:48AM -0500, Stephen R Marenka wrote: > I think this may be genext2fs bug #232023. > > Preliminary testing seems to support this. If I create a filesystem using > dd and ext2fs and copy a broken initrd to it via loopback: the new image > seems to be fine. > > Which brings me to d-i, the mac/nativehd-initrd.gz and cdrom22-initrd.gz > images are so afflicted. I plan on copying them to a fresh filesystem > and testing them, but that doesn't help what's in the archive. > > Unfortunately, the only build workaround that I'm aware of requires > root. > > dd > mke2fs > sudo mount -o loop > sudo cp > sudo umount > gzip > > Ideas welcome.
Do you have enough space and kernel support to use cramfs as a workaround? -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
