Version: unspecified (using KDE 4.4.5) OS: Linux Compression of the given rootfs using squashfs and extraction using unsquashfs with various options. Reproducible: Didn't try
Can you attach a sample file, or link to instructions on how to build/extract them?
See man page of mksquashfs and unsquashfs from squashfs-tools package -- http://www.digipedia.pl/man/doc/view/mksquashfs.8/ http://www.digipedia.pl/man/doc/view/unsquashfs.8/ optionally ark should ask the root passwd (using kdesu or kdesudo) to see all the contents for that particular rootfs. After compression, it should change the ownership of the image to the user ark is currently running as. Warning -- This program has a strange obsession with the squashfs-root directory, this is the email I wrote to the author - " ... However there's a major problem, the executables have a strange obsession with the squashfs-root directory. Whenever you - mksquashfs <directory> In the image made, the first thing will be the squashfs-root directory, there's no way you can change that... you can't change it's name or have the OS tree put in the archive directly. This results in major consequences when unsquashing the FS to a folder which has a tree with mounted block devices. For e.g, if I wanna extract the contents to /mnt/debian which has the directory /home and /mnt mounted.
At first, I'm more comfortable with adding read-only support for squashfs images to Ark (in the case we do add support for it, as I'm still not 100% convinced it is a valid use case for Ark), just like we do for ISO images -- there are too many important options for mksquashfs, and if someone is really creating a filesystem image with it, it can be safely assumed that the person is skilled at using a terminal. There's one problem, though, in that there is no mimetype for squashfs images, so it is not easy to associate Ark to these files and make it open them. Last but not least, I didn't understand this section you've written: > optionally ark should ask the root passwd (using kdesu or kdesudo) > to see all the contents for that particular rootfs. Can you explain this further?
(In reply to comment #3) > At first, I'm more comfortable with adding read-only support for squashfs > images to Ark (in the case we do add support for it, as I'm still not 100% > convinced it is a valid use case for Ark), just like we do for ISO images -- > there are too many important options for mksquashfs, and if someone is really > creating a filesystem image with it, it can be safely assumed that the person > is skilled at using a terminal. > > There's one problem, though, in that there is no mimetype for squashfs images, > so it is not easy to associate Ark to these files and make it open them. > > Last but not least, I didn't understand this section you've written: > Yup, that is true. But I was wondering if it could help us get around the squashfs-root directory, anyway, we have a work around for that. > > optionally ark should ask the root passwd (using kdesu or kdesudo) > > to see all the contents for that particular rootfs. > > Can you explain this further? Many contents in the squashfs image are owned by root or often have o-rwx permission. Asking for password is necessary for certain files cause of the permission.
Another thing that came to my mind when I was filing a bug for a new mime type was that, compared to conventional archives, squashfs has some major advantage - 1) Multithreaded compression using xz -- something which no other program does. 2) It's a mountable FS (using loop). Thus ark may have a feature to mount the squashfs image somewhere. This makes it a tempting FS not only for compressing OSs, but also general data.
application/vnd.squashfs has since been registered as the MIME type for squashfs files.
Now that there is a MIME type for squashfs files, what is holding this back? As for type-2 AppImages, these are squashfs files appended to ELF files. So one needs to parse the ELF header to find out how long the ELF is, and open the squashfs with the corresponding offset. Let me know if you need more information on this. Type-2 AppImage spec: https://github.com/AppImage/AppImageSpec/blob/master/draft.md#type-2-image-format Code: https://github.com/AppImage/libappimage/blob/5d032421aef066e6e1c05b30a8006f0c84a02b71/src/libappimage_shared/elf.c#L120
(In reply to probono from comment #7) > Now that there is a MIME type for squashfs files, what is holding this back? squashfs support in libarchive. I see you already filed https://github.com/libarchive/libarchive/issues/792 a long time ago, so we probably already discussed this elsewhere (can't remember now).
*** Bug 413531 has been marked as a duplicate of this bug. ***
p7zip seems have limited support for squashfs, but when listing the contents of the following test file (7z l -slt houdini_z.sfs), p7zip warns that "There are data after the end of archive". Test file: https://github.com/redchenjs/aur-packages/raw/master/anbox-image/houdini_z.sfs