Core v4.4rc3

[roberts]

The third release candidate of Core 4.4 is ready for public testing:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release_candidates

The major theme for Core v4.4 is a kernel & modules update and tag searching.

Changelog for 4.4rc1:

* Minor kernel update to 3.0.21 to support the following:
** ax25 / ham radio support
** kexec
** efficeon agp patch
** r6040 mii fix
** isa libata enabled for very old laptops
** xts, gf128mul for truecrypt uses
** resolves the kernel panic issue when mounting CIFS shares.
* Updated tc-config with syslog/rsyslog patch
* Updated Xprogs.tcz: scmbrowser and smc-fetch.sh tweaks

Update instructions, from the release candidate area:
1. Copy over new vmlinuz
2. Copy over new core.gz
3. Copy over new Xprogs.tcz
4. boot into new system

if You have/use X then
AppsAduit -> Dependencies -> Build Reporting Database -> Fetch Missing

or if you only use Core (no X) or Xorg did not start and only have a system prompt use:
tce-audit builddb
tce-audit fetchmissing

=====================
Change log for 4.4rc2

* Updated search.sh added -t option for tag search.
* Updated provides.sh for CLI use.
* Updated appbrowser for new tag search.
* Updated ab keyword is now a tag search.
* Updated tce-size with date check on sizefile update.
* Updated tce-setup fixed when base boot code is used with missing /tmp/tce/optional directory.
* Updated tce-setdrive with a required readlink.
* Updated filetool.sh with a required readlink when used after tce-setdrive.
* Recompressed modules to save space.
* Added ssb module to base.

Note: Xprogs.tcz has been updated and is in the release candidate area.

=========================
Change log for 4.4rc3
* Updated busybox 1.19.4 plus patches to fix busybox tftpd vulnerability.
* Updated tc-terminal-server to accomodate busybox tftpd vulnerability.
* Updated scm-search -t for tag searching.
* Updated scmbrowser for tag searching.
* Updated filetool.sh improved invalid device handling.
* Updated tce-setdrive now sets default backup device without a reboot.
* New boot code, e.g., iso=sdb1 booting from a single ISO file to load embedded extensions.
* New fromISOfile script for after boot support of a single ISO file embedded extensions.
* Updated rebuildfstab fixed pid checking.
* Updated exittc and filetool spelling.

Note: Xprogs.tcz has been updated and is in the release candidate area.
Note: Feature freeze.

[roberts]

Starting with v4.4rc3 it is now possible to load the embedded extensions inside an iso image file.
Booting from an iso as supplied by various boot loaders, eg YUMI, the embedded extensions were not readily available.

The new fromISOfile now provides for full X/GUI+ experience.

It can be used as a boot code:
boot: tc iso=sdb1
This short version will scan sdb1 for isos and if one is found will attempt to mount and process it.

Optionally one can use the full path to avoid the scanning delay with:
boot: tc iso=/mnt/sdb1/multiboot/ISOS/TinyCore-4.4.iso

After boot is also supported. If the system booted from an iso file and you are at:
$
they use either the short/scan style or fullpath
$ sudo fromISOfile /mnt/sdb1
$ startx

Once you have it working and you have set your tce directory, tce-setdrive
then you can add fromISOfile to /opt/bootsync.sh as

/usr/bin/fromISOfile  /mnt/sdb1/multiboot/ISOS/TinyCore-4.4.iso

This will result in the familair X/GUI from a single ISO image file.

[uggla]

I propose a tce.installed fix:

http://forum.tinycorelinux.net/index.php/topic,12339.msg69994.html#msg69994

Regards
Uggla

[vinnie]

but this features is only able to start tinycore or can act as "boot loader" for any bootable ISO?

[curaga]

It's only for loading extensions from an iso file, in the running session.

[curaga]

Seems fromiso doesn't support label/uuid?

[bernhard]

[...] or can act as "boot loader" for any bootable ISO?

you could use memdisk (http://www.syslinux.org/wiki/index.php/MEMDISK) for that purpose ...

[AbNoRMiS]

from version to version remains forgotten and nobody needed cde/optional/libiconv.tcz.dep with zero size
and i have a question, can't understand for what instlist-files are used?  i can't find anything about it

[netnomad]

hi roberts,

with the actual release candidate my ethernet-card works flawless now.

b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet
b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
b44 ssb0:0: eth0: Flow control is off for TX and off for RX

thank you.

[ixbrian]

from version to version remains forgotten and nobody needed cde/optional/libiconv.tcz.dep with zero size
and i have a question, can't understand for what instlist-files are used?  i can't find anything about it

The instlist files are used by tc-install when running from Core Plus.    When you select the categories of extensions to install from tc-install (such as "Wireless Firmware", "Wireless", etc) these ".instlist" files contain the list of extensions that will be installed for each category. 

[AbNoRMiS]

thanks for clarifying, now it's clear
i always installed tc manually and never used tc-install
and therefore could not understand what is this

[vinnie]

It's only for loading extensions from an iso file, in the running session.

Uhm I misread!

you could use memdisk (http://www.syslinux.org/wiki/index.php/MEMDISK) for that purpose ...

effectively I remember I had tried some time ago, trying to start [remaster] iso from tinycore.
now that you reminded me, what was exactly happening is that it started without the extensions.

So that means I can start other distros using tinycore as bootloader for derived and not derived?

[gerald_clark]

Tiny core is not working as a bootloader.
Your bootloader is loading the tinycore kernel and initrd.
With the new iso=option, tinycore can now find the tce directory inb that iso.

[mladen]

Thank You for 4.4rc3 Roberts !

With  `fromISOfile`  I get just what I needed when try to experiment with cde boot option - a possibility to boot a system to a customizable starting X/GUI configuration, without using .tcz or .scm extensions from standard /tce directory.

You were quite right with:
  " On a usb install you should be using a normal live tce directory and not cde.
    cde is intended for cdrom and isohybrid for delivery of read-only extensions due to the
    factoring out of X/GUI from the initrd strting with version 4.2"
in 4.4rc2 conversation:

[AbNoRMiS]

error permissions issued during the backup

tc@box:~$ filetool.sh -b
sed: can't create temp file '/opt/.filetool.lstrjEe5X': Permission denied
Backing up files to /mnt/sda1/tce/mydata.tgz Done.

sed (string 158) haven't permissions to delete the empty lines

Code: [Select]

sed -i /^$/d /opt/.filetool.lstsudo should be used

Code: [Select]

sudo sed -i /^$/d /opt/.filetool.lst