Tiny Core Base > Final Releases
Tiny Core v5.0
Juanito:
--- Quote from: chattrhand on September 16, 2013, 03:34:30 PM ---My extensions working also with v5.0 are:
abiword-2.8
ace-of-penguins
fluff
gaiksaurus
getflash11
gimp
gnumeric
GNUPaint
gnupg2
KeePassX
PidginInternetMessenger
TCInstall
Terminal
Viewnior
XChatIRC
Xpdf
--- End quote ---
Did you really test all of these with tc-5.x (for example fluff and gimp will not work with tc-5.x)?
helasz:
Hi All,
According to zlib's home page (http://www.zlib.net/) version 1.2.7 has some rare bug, they took away even the source for that version. It seems to be reasonable to update that package.
Juanito:
It depends - we'd have to weigh "very rare bug" against what updating zlib might break...
Zendrael:
Hi!
Core 5.0 (CorePlus) is working in my machine (Vortex86 MX+ SoC) but is much slower than CorePlus 4.7.7.... Loads extensions slower and after retoring mydata.tgz (which has 113kb) takes another long time to start Xvesa!
Besides that, is working ok!
Thanks!
wt:
--- Quote from: Juanito on September 16, 2013, 11:18:07 PM ---
--- Quote from: wt on September 16, 2013, 03:28:36 PM ---I don't see a core64.gz anymore.
--- End quote ---
It's rootfs.gz + modules64.gz you need
--- End quote ---
I am starting tinycore in a Qemu VM. Qemu doesn't appear to support launching with multiple initrds, so I had to manually combine the file like I did in my post above. I assumed that since core.gz was there that core64.gz should also be there.
FTR, originally, I thought that the gz files had to be aligned in the constructed initramfs file (thus the dd instead of catting). Turns out that is incorrect. I was able to do the following to create the core64.gz file:
--- Code: ---cat modules64.gz rootfs.gz > core64.gz
--- End code ---
That's simple enough that I don't practically care about having core64.gz. However, I would have expected core64.gz to exist for consistency since core.gz exists for the 32-bit stuff.
Also, why are my code blocks in these forum posts showing up with that annoying "newbielink:javascript:void(0); [nonactive]" before the block? Can I fix that somehow?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version