Tiny Core v15.0

[Juanito]

Team Tiny Core is proud to announce the release of Core v15.0
http://www.tinycorelinux.net/15.x/x86/release
http://www.tinycorelinux.net/15.x/x86_64/release

Changelog for 15.0:
* kernel updated to 6.6.8
* glibc updated to 2.38
* gcc updated to 13.2.0
* binutils updated to 2.41
* e2fsprogs base libs/apps updated to 1.47.0
* util-linux base libs/apps updated to 2.39.2
* zlib base lib updated to 1.3
* busybox updated to 1.36.1
* tce-functions/setdrive/setup: use : in chown
* tce-audit: add md5check action from bdantas
* tce-audit: md5check update from bdantas
* tce-load: sudo touch from polikuo
* update-everything: handle missing or extraneous dep files from bdantas
* tce-update: allow tcedir/optional to be a symlink from bdantas
* update-everything: add safety checks from bdantas
* busybox CONFIG_FEATURE_EDITING_HISTORY changed 150 -> 1000

[GNUser]

Congratulations to the team on another solid release!

Just one cosmetic thing: /etc/os-release in corepure64.gz (I tested CorePure64-15.0.iso only) needs to be updated:

Code: [Select]

$ cat /etc/os-release
NAME=TinyCore
VERSION="15.0beta1"
ID=tinycore
VERSION_ID=15.0beta1
PRETTY_NAME="TinyCoreLinux 15.0beta1"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:tinycore:tinycore_linux:15.0beta1"
HOME_URL="http://tinycorelinux.net/"
SUPPORT_URL="http://forum.tinycorelinux.net/"
BUG_REPORT_URL="http://forum.tinycorelinux.net/"With current /etc/os-release, boot message says 15.0beta1 is booting when I am in fact booting version 15 final release.

[Juanito]

I'm not sure what happened there, hopefully OK now..

[GNUser]

Hi Juanito. Yes, looks good now Thanks!

[Dies Irae]

Hi,

first, thanks for TinyCoreLinux. And of course the 15th release!!!

I signed up to the forum as fast as I could (I *hate signing up* but I've been a daily driver for some 4 years by now).

Why, did i hurry? It would be horrible if TinyCore 15 release ISO would be forever bugged with the broken busybox 1.36.1 !!

WHAT is broken? it is what I call the 'double prompting' (or dual prompting) bug.
It is not always consistent but happens for every linux that I or others have tried (that includes folk in the busybox irc channel). There is however a sure way to replicate the bug consistently:

tce-load -wil links

this will install links2 browser.  Start it (command-line), and just use CTRL+Z to send the job to the background. Et voila: 2 prompts with about 1 second in between (it is of course fun to execute partial commands...).
On other machines i currently use 1.36.0 (the ready static compiled release) for this reason.

please, something, anything. don't let 15 ISO go into history with the dual prompting bug!

[patrikg]

When I read this, I think of the shell's "readline", and that are using in app links.

[andyj]

Gtk3-dev for 32-bit doesn't look for colord now, but it is looking for tiff-dev, which isn't in the repository. In 32-bit land I think it wants libtiff-dev.

[Juanito]

I believe that was due to an error in the gdk-pixbuf2-dev dep file, which was corrected a few days back - the gtk3-dev tree file does show any instances of tiff-dev.

[andyj]

This is what I'm seeing:

Code: [Select]

tc@box:~$ cd /etc/sysconfig/tcedir/optional/
tc@box:/etc/sysconfig/tcedir/optional$ rm gtk3-dev.tcz.dep
rm: remove 'gtk3-dev.tcz.dep'? y
tc@box:/etc/sysconfig/tcedir/optional$ tce-load -iwl gtk3-dev
gtk3-dev.tcz.dep OK
Downloading: tiff-dev.tcz
Connecting to distro.ibiblio.org (152.19.134.43:80)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum: tiff-dev.tcz.md5.txt: No such file or directory
Error on tiff-dev.tcz
tc@box:/etc/sysconfig/tcedir/optional$


[gadget42]

downloaded http://www.tinycorelinux.net/15.x/x86_64/release/TinyCorePure64-15.0.iso yesterday. (yes, good checksum)
today i had time to write it to a thumbdrive and it fails to bring up the gui and reports "failed in waitforX"
tried it in both a lenovo y580 and a thinkstation a20 with the same results
rewrote the stick just to double-check and had no change/improvement
rewrote the stick back to tcl14 just to prove my stick and methods

mostly i wanted to get this posted in case someone else has the same problem(so they know they aren't alone).

will investigate more as additional time becomes available.

as always, huge kudos and thanks to the whole tcl team!

[Juanito]

Did you check your local copy of gdk-pixbuf2-dev.tcz.dep?

[Juanito]

Instead of startx, enter the first line of .xsession to troubleshoot.

[Rich]

Hi gadget42

... i had time to write it to a thumbdrive and it fails to bring up the gui and reports "failed in waitforX" ...

At that time you are at the command prompt. If you now enter:

Code: [Select]

startxDoes the GUI come up? If it does, it's a timing problem, and
here are two ways of addressing it.

You can insert a time delay as described here:
https://forum.tinycorelinux.net/index.php/topic,26391.msg170331.html#msg170331

Or you can set up a loop that waits for your graphics card as described here:
https://forum.tinycorelinux.net/index.php/topic,26391.msg170335.html#msg170335

[andyj]

Did you check your local copy of gdk-pixbuf2-dev.tcz.dep?

That was it. Thanks.

[Dies Irae]

When I read this, I think of the shell's "readline", and that are using in app links.

What precisely is the issue if I may ask? What are the 'app links' ?

As for the broken busybox 1.36.1 shell (the double prompt bug),
In cases where users can not remaster the iso (for what-ever reason, such as their vps host only allowing official distribution media, or simply because they find it complicated enough already to just dd the iso onto their usbstick), I see no way how to replace it and work around the issue.

By the time we get our first and seemingly only chance to slip something in (the httplist boot parameter), busybox shell is already in use.

IF there is no way to fix it, that it is to late to change the official iso, I fear those users will have to resort to an additional separate static busybox-ash that is not version 1.36.1 for their prompt (though a bunch of native tools and scripts are set to 'busybox ash' and thus wouldn't trigger their separate standalone busybox ash, I think. I'm just trying to think of solutions here...  (in case it is to late to fix the release/iso)).

Edit: Or learn to wait a good second before typing your next command (in case your current prompt just suddenly ends (holding the first part of what you typed) and new prompt appears).