Tiny Core Linux
Tiny Core Base => TCB News => Alpha Releases => Topic started by: Juanito on December 27, 2021, 08:23:32 AM
-
Team Tiny Core is pleased to announce that Tiny Core 13.0 Alpha1 is available for public testing:
http://repo.tinycorelinux.net/13.x/x86/release_candidates/distribution_files
http://repo.tinycorelinux.net/13.x/x86_64/release_candidates/distribution_files
This is an alpha level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.
Since this is an alpha cut, we ask that only experienced users test. This cut is not for general use. The features in any alpha are not fixed and may change before a public release candidate is available.
We appreciate testing and feedback.
Changelog for 13.0 alpha1:
* kernel updated to 5.15.10
* glibc updated to 2.34
* gcc updated to 11.2.0
* binutils updated to 2.37
* e2fsprogs base libs/apps updated to 1.46.4
* util-linux base libs/apps updated to 2.37.2
* busybox updated to 1.34.1
* 50-udev-default.rules: add media permissions
* select: require that "break" used in awk scripts
* filetool.sh: prevent gratuitous change to .filetool.lst's timestamp from bdantas
* tce-update: if no directory specified for "list" or "query", default from bdantas
Note:
* some versions of firefox will not start with 13.0alpha1
-
I'm abusing Tiny Core 13.0 Alpha1 x86_64 as much as possible and have not managed to break anything yet. If I do find breakage, I'll report here (hopefully with a fix).
-
I'd like to test this on my router as well, but because the rt2800usb kernel module inside wireless-KERNEL.tcz still does not support my antennas out of the box (they use the RT5370 chipset), I have to recompile said kernel module before I can do any testing.
curaga:
Where can I find the 5.15.10 kernel source code with TCL patches? I cannot find it at http://tinycorelinux.net/13.x/x86_64/release/src/ or http://tinycorelinux.net/13.x/x86_64/release_candidates/
Juanito:
In the last day or two I sent TCL12 x86_64 updates and/or corrections for eiwd, wireguard-tools, and nftables. Had I known you were cooking up TCL13 alphas, I would have held off. I'm sorry for the bad timing.
-
In the last day or two I sent TCL12 x86_64 updates and/or corrections for eiwd, wireguard-tools, and nftables. Had I known you were cooking up TCL13 alphas, I would have held off. I'm sorry for the bad timing.
No problem - posted :)
-
Thanks, Juanito :)
I've only found two problems so far:
1. I am able to reproduce the firefox issue. I'm using an AppImage of firefox 72.0.1 and tabs immediately crash with "Gah. Your tab just crashed." Terminal says "Channel error: cannot send/recv"
2. These two items in the changelog are not actually present in rootfs64.gz:
* filetool.sh: prevent gratuitous change to .filetool.lst's timestamp from bdantas
* tce-update: if no directory specified for "list" or "query", default from bdantas
P.S. This is the most polished TCL pre-release that I've used to date. Except for firefox, every GUI and CLI I've tried is working perfectly. Hats off to you guys.
-
Hmm - it appears I built rootfs{,64}.gz, but didn't post them - posted now.
-
Yes, looks good now :)
-
Copied the kernel sources. May take a day or two for mirrors to sync.
-
Hi Core people,
Thank You for the next release of the best OS in the Solar system!
It would be nice to make tiny corrections to mplayer-cli.tcz.dep, now it misses
libXv
libXinerama
libXxf86dga
TinyCore 13.0 x86
Best regards and Happy New Year!
-
Hi jazzbiker
Those dependencies were pulled in by Xorg-7.7-bin and Xorg-7.7-lib in the TC10 x86 version. It seems Xorg-7.7 was
pulled in through this dependency chain:
libswscale3.tcz
libavutil3.tcz
libva.tcz
Xorg-7.7-3d.tcz
Xorg-7.7.tcz
As of TC11 it changed to:
libswscale4.tcz
libavutil4.tcz
libva2.tczwhich no longer pulls in Xorg-7.7-bin and Xorg-7.7-lib.
-
Hi Rich,
Sometimes I use mplayer outside X, for audio or even for video with fbdev as output video device. I didn't want to say that it is an issue, just tiny inconsistency, nothing more, corner case for freaks like me :) Can be omitted easily.
-
tcc.tcz works fine with linux-5.15_api_headers.tcz, but tcc.tcz.dep still recalls linux-5.10_api_headers.tcz...
-
Hi jazzbiker
tcc.tcz.dep updated.
-
Thanks, Rich!
Am I right posting extensions questions in this thread? I expect the repo content is being tested too.
Regards!
-
Hi jazzbiker
I would say they belong in TCE Bugs:
http://forum.tinycorelinux.net/index.php/board,17.0.html
-
It would be nice to make tiny corrections to mplayer-cli.tcz.dep
dep file adjusted - thanks for reporting this
-
At this point I've tested this on my personal laptop, family media player, and router. These three devices use very different sets of extensions. Everything is working perfectly.
FYI - Recent versions of firefox (e.g., newest version compiled by the developers and provided as a portable/distro-agnostic tarball here: https://www.mozilla.org/en-US/firefox/new/) work perfectly.
Juanito, I submitted a few new extensions for TCL13 x86_64. Please post at your convenience--no rush at all.
Happy new year, everybody!
-
I have two small patches I'd like to see in the new version. One is a change to a patch I submitted a few years ago. It moves the custom static IP configuration from wait4Server() to just after the loopback interface configuration. This way an IP can be configured as static regardless of where the extensions are loaded from. The other adds the optional ability to specify an absolute path for the .lst file when using a CD repository. One way this helps is in an environment with several VM's, one ISO image can be used for multiple VM's by using a .lst file loaded in an initrd. Here is an example of both in use:
DEFAULT pxe
LABEL pxe
KERNEL pxelinux.cfg/default-boot/vmlinuz32-13
INITRD pxelinux.cfg/default-boot/rootfs32-13a.gz,pxelinux.cfg/default-boot/modules32-13.gz,pxelinux.cfg/default-boot/my-www-data.gz
APPEND host=www-vm lst=/etc/sysconfig/www.lst printk.time=1 lang=en_US.UTF-8 cron rsyslog=192.168.3.11 quiet noswap nozswap nodhcp=static_ip cde tce=/ udev.children-max=24
On a separate note all the extensions I normally maintain compile without any overly unusual complications so I should have those ready to submit soon.
-
Applied the nodhcp patch, but the lst one feels very wrong. The list is supposed to be where the extensions are, it's quite a frankenstein setup for it to come from outside the iso when extensions are in the iso.
-
Hi, all.
I just send the new fltk extensions for x86_64. (fltk-xft, fltk-full)
I don't keep the headers because they are the same as fltk-1.3-dev.
Please post at your convenience when you rebuild the main extensions.
-
Posted - thanks
'pity there's not an fltk-wayland...
-
Posted - thanks
'pity there's not an fltk-wayland...
They will probably add it in version 1.4
https://www.fltk.org/str.php?L3371
BTW, it would be nice to update the main fltk-1.3, fltk-1.3-dev to 1.3.8 as well.
They are compatible, but not identical. (No Rush)
-
Applied the nodhcp patch, but the lst one feels very wrong. The list is supposed to be where the extensions are, it's quite a frankenstein setup for it to come from outside the iso when extensions are in the iso.
Why does the list of extensions to load HAVE to be physically tied to where the extensions are? A shared iso image source saves a lot of space, but is only feasible if the iso doesn't have to be remastered every time one of the .lst files changes. Any change to a shared iso image requires that every VM that uses it be powered down.
-
Your lst files change often without the extensions themselves changing? That's a really specific setup. Normally you'd imagine updates happening at the same time.
The static_ip patch is probably not used by anyone else either, but the lst one just makes no logical sense. As per the script, the lst files are supposed to be right next to the extensions, same media, same partition. For them to come from a different device altogether makes no sense. So I'll ask you to keep this one as a local patch.
Using an iso this way with many VMs may be more convenient than a shared NFS repo, I acknowledge that.
-
as previously mentioned @ http://forum.tinycorelinux.net/index.php/topic,23582.msg157321.html#msg157321
request i2c-gpio.ko module be added to the i2c tinycore modules extension
afair i2c-gpio.ko was missing in x86_64 , is there any reason for its absence ?
i have loaded 13 rc and had some issue starting chrome ,
it loaded but tabs would crash many missing .so , even linking .so to correct paths did not fix tab crash
i can provide more detailed info if its of use
..but dont curently have usb mouse to hand
also wrt base glibc
http://forum.tinycorelinux.net/index.php/topic,25446.0.html
The loader cache is one of the few exceptions. Adapting it to a non-FHS context is fruitful for Guix and for the other distros and packaging tools in a similar situation; perhaps it could become an option in glibc proper?
-
i have loaded 13 rc and had some issue starting chrome ,
it loaded but tabs would crash many missing .so , even linking .so to correct paths did not fix tab crash
Hi, mocore. Older browser versions are not working well with latest linux kernel and/or latest glibc. I had same issue with firefox and chromium. So I guess chrome is affected as well. This is not TCL's fault.
I just tried and the latest chrome is working fine with TCL13 alpha x86_64. Get the latest 64-bit .deb package here (https://www.google.com/chrome), unpack it (ar -x google-chrome-stable_current_amd64.deb), extract data.tar.xz , then run opt/google/chrome. It works without any fiddling.
-
;D
This is not TCL's fault.
;) this reminds me of "fix the problem not the blame" .www.youtube.com/watch?v=_yYu3KdRmJM
so im pointing no fingers , however any relevent links/info wrt what / why backwards compatablity brakes for some bin's would be enlightening!
-
Using an iso this way with many VMs may be more convenient than a shared NFS repo, I acknowledge that.
Yes, it's a lot easier to setup, and the extension source is read only which is a security bonus.
At least I didn't come away empty handed 8)
-
Hi, again.
@Juanito, would you mind taking a little time to re-configure the perl extension ?
We have discussed it in this post (http://forum.tinycorelinux.net/index.php/topic,24930.0.html) before, the "pager" problem.
I just check your note (http://tinycorelinux.net/13.x/x86_64/release/src/toolchain/compile_tc13_x86_64), it's not fixed.
tc@box: ~ $ grep ^pager /usr/local/lib/perl5/5.32/core_perl/Config_heavy.pl
pager='/usr/bin/less -isR'
-
as previously mentioned @ http://forum.tinycorelinux.net/index.php/topic,23582.msg157321.html#msg157321
request i2c-gpio.ko module be added to the i2c tinycore modules extension
afair i2c-gpio.ko was missing in x86_64 , is there any reason for its absence ?
Just an oversight, didn't see your earlier post either. However it's a bit late now, not sure I'm going to do a rebuild just for that.
-
would you mind taking a little time to re-configure the perl extension ?
We have discussed it in this post (http://forum.tinycorelinux.net/index.php/topic,24930.0.html) before, the "pager" problem.
I just check your note (http://tinycorelinux.net/13.x/x86_64/release/src/toolchain/compile_tc13_x86_64), it's not fixed.
In fact the current extension has not been recompiled since you mentioned the problem, but no problem, I'll add it to the list along with fltk.
-
afair i2c-gpio.ko was missing in x86_64 , is there any reason for its absence ?
Just an oversight, didn't see your earlier post either. However it's a bit late now, not sure I'm going to do a rebuild just for that.
hi curaga , thanks for the clarification
>not sure I'm going to do a rebuild just for that.
i guess you mean for 11x/12x ? , i posted hear because i was hoping (if posible) this module oversight might be corected in 13.x +
-
I mean the 13.x x86_64 kernel.
-
Hi xor
Your posts and replies have been moved to their own thread here:
http://forum.tinycorelinux.net/index.php/topic,25458.0.html