tinycore_v4.1rc1

[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).

[roberts]

Please re-read the announcement of 4.1rc1 as it clearly states:

"Change log since v4.0" and not 4.0.2, i.,e the change log is since the last major release v4.0. If you review the change logs of the miror releases of 4.0.1 and 4.0.2 you will find that they are included in the change log of 4.1 as stated in the announcement.

This was done as many users do not bother with minor releases as witness by the number of reads of their announcements.

[roberts]

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.

Enhanced to suppress. Completed. Thanks

[bmarkus]

Add /etc/protocols to base. It is short. Its lack is causing frequent problem at least for me even if it is available in the iana extension. Current setup is insequevent, as /etc/services is in base. For details see

http://forum.tinycorelinux.net/index.php/topic,11551.0.html

[gerald_clark]

I compiled the lxc utilities and ran the lxc-checkconfig.
The following are not set in the kernel config:
CONFIG_CGROUP_NS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_FILE_CAPABILITIES=y

[curaga]

http://bugs.lxc.tl/issues/39

The NS option was removed in 3.0. Are the security options essential?

[gerald_clark]

I will continue development without them and let you know if there are any big problems.
Thanks.

[roberts]

Add /etc/protocols to base. It is short. Its lack is causing frequent problem at least for me even if it is available in the iana extension. Current setup is insequevent, as /etc/services is in base. For details see

http://forum.tinycorelinux.net/index.php/topic,11551.0.html

I believe curaga answered this request in the above referenced thread.
If your use of perl requires iana-etc.tcz then it is an extension perl that needs /etc/protocols. The base does not need it. It is the policy if the base does not need such then it is best served via extension.

If there is a timing issue with some startup script(s), then move iana-etc.tcz high up on your onboot.lst or add iana-etc.tcz to perl.tcz.dep which will ensure that iana-etc.tcz will load before perl.

Would be better to have the maintainer of the Perl extension update the info file with a note about /etc/protocols and the iana-etc extension.

[bmarkus]

Robert,

this is not Perl related at all. It comes up time to time with other extensions. I just faced it two days ago for example creating go language pack. In fact, this is a generic stuff one can expect be in any LINUX system. And small.

But OK, it is your baby. WIll use iana extension. ut in such case please do remove /etc/services from base, iana-etc.tcz provides it.

 

[bmarkus]

Just a final note. We are talking about a 6k file. It can be a reduced version with few lines of common protocols like IP, TCP, UDP and ICMP and use iana-etc.tcz when a full set is needed. Same way as already implemented for /etc/services.

Having a minimal /etc/protocols in base in 99% no need to install iana-etc.tcz as /etc%services is already there, so one can avoid annecessary overhead. TC is about efficiency.

Anyhow, I do not want to waste more time for 1k where no any real argument to omit except 'just'.

[roberts]

Since your 6k file is obviously different than iana 25k file please email me your proposed file and the team and I will consider.