squashfs-lzma “linux-live-script”

[curaga]

The 7zip algorithm for gzip only affects compression, increasing both time and ratio (but still being about as fast as bzip2 to compress, and with no speed decrease decompressing). Because the stream is standard, 7zip compressed gzip streams can be decompressed with any compliant implementation.

Oh, and we already have such advdef in advcomp.tce can be used to recompress gzipped files with the 7zip algorithm for smaller files. It's used both for extensions and the base image.

[TraperJohn]

I thought that lzma used 7zip compression with a slightly different format.
 ???Then I don't understand: how come lzma is not up to squashfs 4 yet if 7zip is ?
I guess that 7zip is the way to go .
Thanks.

[curaga]

This is a bit confusing, I agree

7zip is a program, and a format. When talking about the program 7zip, they have a more efficient gzip algorithm there than in gzip. The 7zip format instead uses lzma compression.

[TraperJohn]

O

[jpeters]

What is tc using for its backup.tgz ?  I manually tried cpio and tar ...neither worked.   

[curaga]

backup.tgz is a regular gzipped tarball, perhaps yours is corrupted?

[jpeters]

backup.tgz is a regular gzipped tarball, perhaps yours is corrupted?

It unpacked okay with tar, but after repacking with 'tar -czf', the file would disappear when booting and load norestore,  I did this several times, with the same result, and had to add files and backup from within tc for it to work.   Also, when I moved  a 'myfiles.tgz' it created a circular dir structure (link to ".") that appears to be impossible to delete.  

edit: I'm thinking maybe there's an issue with the file or file location being in use, since I was also getting "Stale NFS file handle" issues when simply trying to move "tinycore.tgz.bak" to "tinycore.tgz"  I think I had to do something like first move it to another folder,  

[TraperJohn]

I got back from vacation and back to work .
After are discussion I mounted the tinycore iso, decompressed the tinycore.gz and expanded the CPIO'ed tinycore.
Now I see the typical linux fs but where is the tce, tcz and other images I expected ?
I thought TC used compressed  images in tce, tcz formats on the iso.
Don't get me wrong I am used to one big fs to edit like in the core lzm of Slax but when you were talking about replacing applications you noted the  tce, tcz extensions.
 ???So now I'd like to know what you were talking about?

[jpeters]

Extensions are kept in a separate folder that can be pointed to in  boot options  (eg, tce=/hdax/tcz).  That way, they'll load even if you change to a an updated boot folder.  Check out the intro help docs.  

[TraperJohn]

But are the applications installed in to the fs or mountable during boot from tce...?
If they are the latter then I'd expect to see some of them in the iso already.

[jpeters]

But are the applications installed in to the fs or mountable during boot from tce...?
If they are the latter then I'd expect to see some of them in the iso already.

The iso contains grub, the kernel and pristine setup that can be rebooted at any time using
the "norestore, base" bootoptions. All the rest is modular, using extensions in a separate folder.    
See wiki, remaster, for info regarding opening tinycore.gz.

[TraperJohn]

What's the name of the separate folder?

[jpeters]

your choice (see my previous post) . Please read the intro help docs 

[TraperJohn]

The iso contains

boot with sub directories isolinux, bzImage (the kernel), and tinycore.gz (the compressed CPIOed fs/linux-stuff).

boot options...

"norestore, base" bootoptions.

All the rest is modular, using extensions in a separate folder.

???separate folder??

[jpeters]

http://www.tinycorelinux.com/concepts.html