On Tue, 2008-01-15 at 12:00 +1100, [EMAIL PROTECTED] wrote: > > mksquashfs /casper/chroot /casper/filesystem.squashfs > -noappend > > -always-use-fragments > > > > core dumps after finding empty sym-links and bad files > > What version of mksquashfs are you using? If you're using > Ubuntu Gutsy then I > expect it is mksquashfs version 3.2-r2. > > This should not crash on empty symlinks, but there is a bug in > it that means it > may crash on files which are unreadable (either because of > permissions or I/O > error). > > This was fixed in the latest 3.3 version available from > http://squashfs.org.uk, > and if you download that you should not have any more > problems. > > If you use the latest version, and you want the filesystems to > work on Gutsy, > you have to specify -b 64K -no-sparse to mksquashfs to force > it to generate a > filesystem compatible with the version of Squashfs in Gusty.
I hoped no one would respond and blushing could be avoided I mounted proc and sys in my chroot then left them mounted, exited and did the mksquashfs and got the core dump. unmount then build works fine. If anyone is interested here is a link to the stuff I'm playing with https://wiki.ubuntu.com/BootToRAM James -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
