Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on November 15, 2009, 06:10:26 PM
-
The First Release Candidate of v2.6 (tinycore_2.6rc1.iso), is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates
tinycore_2.6rc1.iso
tinycore_2.6rc1.iso.md5.txt
Change log for v2.6rc1:
* Updated bzImage for smaller size (upx'ed)
* Updated rebuildfstab to drop extra mount points.
* New select utility replaces dialog
* Dropped dialog, use dialog.tcz extension (posted)
* Updated xsetup.sh
* Updated mktclocal
* Updated tc-terminal-server
* Updated cpanel to add Apps Audit
* Updated missing link libpng.so
* Updated blkid, libblkid, and libuuid
* Dropped cryptohome support.
* Updated tc-config
* Updated rc.shutdown
* Busybox mount and losetup replaces GNU versions
* Fixed bug in flwm_topside_restart
* Updated flwm menu .wmx to reflect recent changes.
Notes:
Be sure to update your kernel, with new smaller, boots faster, bzImage.
I decided to drop dialog as it is quite big and only used by three
programs, which are rarely used. Also, dialog screen gets
easily messed up when booting with xsetup.
Cryptohome was dropped by team decision.
Note also; the distribution files are also availble:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates/distribution_files
-
I guess you know that "update" uses dialog. Can you include it as an extension? Thanks.
edit: opps....missed the top of the post, sorry
-
* Dropped dialog, use dialog.tcz extension (posted)
It has been available in the repository since 2009/11/09. See dialog.tcz.info file.
-
* Dropped dialog, use dialog.tcz extension (posted)
It has been available in the repository since 2009/11/09. See dialog.tcz.info file.
I just compiled 1.1-20080819, but it's 12 K larger, so your's should work fine. Thanks.
I guess we're really moving into gui land, when 64 K is too much to spend for a dialogue box.
(although I don't know about the xsetup issue).
-
* Updated blkid, libblkid, and libuuid
Good news, now we can drop hal_support.tczl which is replacing libblkid, and libuuid needed by HAL. Thanks!
-
Sytem is freezing randomly after startup or do not start at all, stops somewhere at different points. USB stick, boot parameters and PC is the same used with 2.5 with no problem.
-
Similar, but not quite the same problem here. I'm booting in VirtualBox, like I usually test these with before I go "live", same configuration I used for all previous versions, and I get "ACPI: Unable to load the System Description Tables", and takes a LOT longer to boot than 2.5 did. 2.5 didn't give any errors, either.
-
Is it something to do with libblkid/libuuid being updated in the base and duplicated in the hal_support extension maybe?
I used 2.6rc1 for a couple of hours earlier without seeing any problems.
-
Is it something to do with libblkid/libuuid being updated in the base and duplicated in the hal_support extension maybe?
No, nothing to do with hal_support extension. It is the clean stock 2.6rc1 without loading any extensions.
-
Is it something to do with libblkid/libuuid being updated in the base and duplicated in the hal_support extension maybe?
Doubtful, there isn't even a hard drive in this virtual machine, it's for testing liveCD's before I actually install/use them in a real machine.
-
From dmesg, I see a lot of errors of the form:
loop0: rw=0, want=66, limit=16
isofs_fill_super: bread failed, dev=loop0, iso_blknum=16, block=32
ISO 9660 Extensions: RRIP_1991A
attempt to access beyond end of device
It's not clear to me (yet) whether this is due to the new block size in the latest squashfs extension, using tcz made with both the old and new squashfs extensions, busybox mount, info from the updated libblkid or what...
-
is cryptohome going to be moved out into an optional package?
-
Juanito - Do you see those same errors with TC 2.5? On the chance that the error you are seeing is related to 4096 block size, we have a full online backup of the tcz repo we can easily revert to.
spence91 - for now cryptohome has simply been removed from base. I will see if there is a way to work it into being supported by an extension. It is probably better security practice to encrypt a mountable file within /home or a partition rather than encrypt the entire /home anyway since with cryptohome all your sensitive data is left mounted and unencrypted for the entire session. And that is not the case with an encrypted file/partition. We also have encrypted backup for those that want their persistent files in /home encrypted.
-
I get no dmesg items when mounting squashfs with prior block size, I do when using the new block size.
-
Rats.
I will reinstate the backup repo. It will be available in a few minutes.
Sorry everyone for the inconvenience, and I will post the extensions that are not part of the backup repo tonight.
-
4096 repo is reinstated.
I jumped the gun with switching away from it.
-
tinycore_v2.6rc1a is now posted. The only change is GNU mount replaces busybox mount.
-
2.6rc1a is still freezing randomly as 2.6rc1
-
Bmarkus, is that still with no extensions being loaded?
And booting from usb? And using UUID labels instead of device names?
-
Bmarkus, is that still with no extensions being loaded?
And booting from usb? And using UUID labels instead of device names?
What do you mean using UUID labels instead of device names ?
-
http://tinycorelinux.com/faq.html#pendrives
That is, if boot parameters are used.
-
I'm using an 512k stick with two primary partititions:
1 - 64M FAT
2 - rest is EXT3 which contains only an empty /tce and /lost+found
2.6rc1a is booted first with 'tinycore waitusb=5' When started, tried to install LXDE with appbrowser which got frozen half way. Restartring it with 'tinycore waitusb=5' during loading extensions I see this message:
mount: wrong fs type, bad option, bad superblock on =dev/loop7, missing codepage or helper program, ...
occured while loading: /mnt/sdb2/tce/gnome-icon.-theme.tcz
Press Enter key
ENTER doesn't work.
It is freezing randomly at different phases, for example now the last message is 'Setting Timezone' when restarted.
-
Thanks.
I will test something tonight, I think I may know what will fix it if 2.5 works fine with that set of extensions.
-
Thanks.
I will test something tonight, I think I may know what will fix it if 2.5 works fine with that set of extensions.
Sounds good. Same set, same USB, same PC works fine with 2.5
-
And booting from usb? And using UUID labels instead of device names?
This is how I boot - i.e. usb and uuid - and I don't see any problems