Tiny Core Base > Release Candidate Testing

tinycore_v4.1rc1

(1/3) > >>

roberts:

The First Release Candidates of Tiny Core & Micro Core v4.1 are now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release_candidates

tinycore_4.1rc1.iso     tinycore_4.1rc1.iso.md5.txt
microcore_4.1rc1.iso   microcore_4.1rc1.iso.md5.txt

Change log since v4.0:
* Updated pcmciautils-018
* Updated sudo-1.7.7
* Updated freetype-2.4.7
* Updated imlib2-1.4.5
* Updated libpng-1.2.46
* Updated tc-config new boot code pretce for raid and lvm support.
* Updated tce-setdrive improved error handling.
* Updated tc-terminal-server for new kernel.
* Updated appbrowser improved screen dispay handling.
* Updated appsaudit Updates for base version check.
* Updated version now supports options -c -l -s (check, long display, and short display).
* Updated tc-config for microcore without X.
* Updated udev rules to correct reported permission issues on usb devices.
* Updated select to accept input from stdin.
* Updated tc-functions getKeyEventDevice
* Updated tc-config for better detection of /dev/rtc and handling of loadcpufreq.
* Updated rebuildfstab for better cdrom scanning and to eliminate boot errors.
* Updated filetool.sh for initial use of SAFE backup option.
* Updated tce-setup for processing extensions on cd - new boot code 'cde'
          which results in scanning cd for additional extensions to load.
          This should eliminate the cd boot errors and is used in new multicore.

Note: Microcore users need new Xprogs.tcz and Xlibs.tcz

gerald_clark:
Tested pretce bootcode and Documented same in wiki.
Putting tce on LVM
http://wiki.tinycorelinux.net/wiki:pretce

netnomad:
hi gerald_clark,

is it possible to use lables or UUID for the pretce
f.e.
pretce=LABEL=tc/pre tce=dm0 with a device that is labeled with "tc"?
let's assume that tc is not in the lvm, that it's a normal partition...
or is it possible to label a logical volume!?
but perhaps this pre-loading or this search for pretce is only successful on a normal partition?

very interesting development to improve the use of tinycore,
f.e. to manage the very last space on a limited storage-medium.
i really like that idea to do so much with so few tools and a minimum infrastructure,
thank you all!

gerald_clark:
No. Pretce cannot use labels or UUIDs. 

It runs early and is intended to load drivers and initializers from your boot directory needed to access your tce directory.

The object is to provide a method of using the released initrd without having to do a remaster with additional drivers and a modified tc-config.

Another use ( other than LVM ) would be tce on a md RAID.

maro:
Here are some observations (or questions) after comparing TC 4.1rc1 with 4.0.2:

* It might be worth to ensure in '/usr/bin/version' in the case of a failed 'wget' call that the output message is either suppressed of adjusted accordingly.
* I could not detect any change in '/etc/udev/rules.d' which I would have expected due to Updated udev rules to correct reported permission issues on usb devices.
* I could not detect any change in '/usr/bin/select' which I would have expected due to Updated select to accept input from stdin.
* I could not detect any change in '/etc/init.d/tc-functions' which I would have expected due to Updated tc-functions getKeyEventDevice.
* I could not detect any change in '/usr/sbin/rebuildfstab' which I would have expected due to Updated rebuildfstab for better cdrom scanning and to eliminate boot errors.
* I could not detect any change in '/usr/bin/filetool.sh' which I would have expected due to Updated filetool.sh for initial use of SAFE backup option.
* I could not detect any change in '/usr/bin/filetool.sh' which I would have expected due to Updated tce-setup for processing extensions on cd - new boot code 'cde'.I assume that some points are due to belated change notices, but I thought I mention them nevertheless just to make sure that enhancements that were announced are indeed in the release candidate (or the final release).

Navigation

[0] Message Index

[#] Next page