Recent Posts

61

Release Candidate Testing / Re: Core v17.0beta1

« Last post by aus9 on January 25, 2026, 09:09:09 AM »

this is question on a TCE if I look at
http://tinycorelinux.net/17.x/x86_64/tcz/glibc_add_lib.tcz.list

SNIP
/lib/libmvec.so.1
SNIP
/usr/lib/libmvec.so

I am not sure the sym link is working correctly. Feel free to correct my inference

Code: [Select]

ls -al  /usr/lib/libmvec.so
lrwxrwxrwx 1 root root 44 Jan 25 21:20 /usr/lib/libmvec.so -> /tmp/tcloop/glibc_add_lib/usr/lib/libmvec.so

tc@box:/tmp/tcloop/glibc_add_lib/usr/lib$ ls -al libmvec.so
lrwxrwxrwx 1 root root 22 Dec 11 19:43 libmvec.so -> ../../lib/libmvec.so.1
tc@box:/tmp/tcloop/glibc_add_lib/usr/lib$ ls ../../lib/libmvec.so.1
../../lib/libmvec.so.1

# the real file
ls -al /lib/libmvec.so.1
lrwxrwxrwx 1 root root 42 Jan 25 21:20 /lib/libmvec.so.1 -> /tmp/tcloop/glibc_add_lib/lib/libmvec.so.1

submitqc is not seeing it a sym link...it claims that even though I have glibc_add_lib.tcz in the dep file
submitqc is still reporting I am missing libmvec.so.1
I am suggesting we have too many sym links ...that is the real file in ram drive is a sym link and then you have a sym link to a sym link. Maybe an install script to resolve?

thanks for reading

62

TCE Bugs / seatd & copy2fs.flg

« Last post by M-A-X on January 25, 2026, 08:40:40 AM »

Installing seatd on MicroCorePure64 in persistent/copy mode works without any troubles.
However after rebooting the computer the executable program disappears from the bin directory while the tce.install script for seatd is still there.

Root cause of the problem may be related to the seatd installation script which seems to be not compatible with the copy2fs.flg

Anybody else seeing this problem?

63

General TC Talk / Re: Building Another Logger

« Last post by Rich on January 24, 2026, 08:03:39 PM »

Hi MTCAT

... before I could resize sda5, I had to expand the "extended" partition sda2 to it's largest possible size of ~ 120 GB, after doing that, it was no problem to expand sda5 as well and now I have sda5 as ~ 120 GB, so that should be good now.

A DOS partition table only has space for 4 primary partitions.

If you want more than 4 partitions, you need one of those
partitions to be created as an  extended  partition.

An extended partition acts as a container for multiple logical
partitions. One of my machines has 12 partitions on its drive.

Since the extended partition is a container, you can't make
the logical partitions inside it larger than the container. That
is why you had to expand the extended partition first.

Since you use gparted, you will see choices of Primary, Logical, and
Extended when creating partitions on a device.

64

General TC Talk / Re: Building Another Logger

« Last post by Rich on January 24, 2026, 07:44:04 PM »

Hi MTCAT

... With Lubuntu fired up, do you think it would be correct to simply make a directory called data in the uppermost directory level on the CF-card? ...

If you want to do this using Lubuntu, you should probably do something like this:

Code: [Select]

mount TinycoreStorageDevice
cd TinycoreStorageDevice/home/tc/
ln -s /mnt/sda5/data data
chown 1001:50 data
This assumes  /mnt/sda5/data  is still correct for the new system.

I'm not familiar with Lubuntu, so you may have to perform some
of those commands as root or using  sudo.

65

Raspberry Pi / fastfetch for piCore (aarch64)

« Last post by geev03 on January 24, 2026, 04:17:27 PM »

A few people have asked about getting fastfetch on piCore, since it’s available on most other distros but missing here. I’ve compiled fastfetch 2.58.0 natively on piCore 16.0 aarch64 (Raspberry Pi 400), and it runs perfectly.

If you want a lightweight system‑info tool with a nice logo and fast output, this works out of the box.

Upstream: https://github.com/fastfetch-cli/fastfetch
Version: 2.58.0
License: MIT
Architecture: aarch64 (Raspberry Pi)

The extension includes:fastfetch

Code: [Select]

tc@box:~/fastfetch-2.58.0/build$ ./fastfetch --logo raspberrypi
   `.::///+:/-.        --///+//-:`     tc@box
 `+oooooooooooo:   `+oooooooooooo:     ------
  /oooo++//ooooo:  ooooo+//+ooooo.     OS: TinyCoreLinux 16.0 aarch64
  `+ooooooo:-:oo-  +o+::/ooooooo:      Host: Raspberry Pi 400 Rev 1.0
   `:oooooooo+``    `.oooooooo+-       Kernel: Linux 6.12.25-piCore-v8
     `:++ooo/.        :+ooo+/.`        Uptime: 1 hour, 5 mins
        ...`  `.----.` ``..            Shell: sh
     .::::-``:::::::::.`-:::-`         Theme: Adwaita [GTK3]
    -:::-`   .:::::::-`  `-:::-        Icons: Adwaita [GTK3]
   `::.  `.--.`  `` `.---.``.::`       Cursor: Adwaita
       .::::::::`  -::::::::` `        Terminal: /dev/pts/2
 .::` .:::::::::- `::::::::::``::.     CPU: BCM2711 (4) @ 1.80 GHz
-:::` ::::::::::.  ::::::::::.`:::-    Memory: 473.41 MiB / 3.71 GiB (12%)
::::  -::::::::.   `-::::::::  ::::    Swap: 0 B / 1.99 GiB (0%)
-::-   .-:::-.``....``.-::-.   -::-    Disk (/): 250.00 MiB / 3.34 GiB (7%) - ts
 .. ``       .::::::::.     `..`..     Disk (/mnt/mmcblk0p2): 484.52 MiB / 13.24
   -:::-`   -::::::::::`  .:::::`      Local IP (eth0): 192.168.1.194/24
   :::::::` -::::::::::` :::::::.      Locale: C
   .:::::::  -::::::::. ::::::::
    `-:::::`   ..--.`   ::::::.
      `...`  `...--..`  `...`
            .::::::::::
             `.-::::-`


66

General TC Talk / Re: Building Another Logger

« Last post by MTCAT on January 24, 2026, 12:24:30 PM »

Hi Rich,

As seen in the image below, there's a symbolic link which connects /home/tc/data to /mnt/sda5/data.




With Lubuntu fired up, do you think it would be correct to simply make a directory called data in the uppermost directory level on the CF-card? (as regular user in Lubuntu), just trying to prepare the playing field ahead of time as much as possible for TinyCore.

Thanks,

David

67

General TC Talk / Re: Building Another Logger

« Last post by MTCAT on January 24, 2026, 12:06:13 PM »

Hi Rich,

Thanks for the help with the images and code insertions, will give that a try.

With the help of Gparted on my Slackware desktop, I was able to delete the swap partition (sda1) but even with doing that, before I could resize sda5, I had to expand the "extended" partition sda2 to it's largest possible size of ~ 120 GB, after doing that, it was no problem to expand sda5 as well and now I have sda5 as ~ 120 GB, so that should be good now.

Thanks,

David

68

Release Candidate Testing / Core v17.0beta1

« Last post by Juanito on January 24, 2026, 10:18:34 AM »

Team Tiny Core is pleased to announce that Tiny Core 17.0 Beta1 is available for public testing:

http://repo.tinycorelinux.net/17.x/x86/release_candidates/distribution_files
http://repo.tinycorelinux.net/17.x/x86_64/release_candidates/distribution_files

This is an beta level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.

We appreciate testing and feedback.

Changelog for 17.0 beta1:
* kernel updated to 6.18.2
* glibc updated to 2.42
* gcc updated to 15.2.0
* binutils updated to 2.45.1
* e2fsprogs base libs/apps updated to 1.47.3
* util-linux base libs/apps updated to 2.41.2

* provides.sh: Update scripts to work with https mirrors from mbartlett21
* tce-update: Undo changes around fetchzsync from mbartlett21
* tc-functions: Update https checking from mbartlett21
* tc-functions: Change subshell from mbartlett21
* update-everything: Add /usr/local/bin to PATH from mbartlett21
* shutdown.sh: handle empty lines in /opt/.xfiletool.lst from mbartlett21
* 50-udev-default.rules: expanded input device permissions from bdantas

69

Alpha Releases / Re: Tiny Core 17.0 Alpha 1 Testing

« Last post by Paul_123 on January 24, 2026, 09:15:20 AM »

1.37.0 was marked stable 16months ago, but it was not really that stable.  While git shows commits, The maintainer went quiet on his mailing list, but he is just recently back.  But has not said anything related to the next stable version, or a bugfix 17.1.

70

TCE Bugs / Missing extensions in 16.x/86

« Last post by linic on January 24, 2026, 09:03:17 AM »

Hi,

I have been running some tests with my custom mirror and found missing extensions for 16.x/x86.

Using rsync, I mirrored rsync.ibiblio.org::tinycorelinux/ and used a custom recursive script to copy extensions
using their .tcz.dep from the mirror folder to an empty folder.

I tested manually with a browser that they're not referenced at http://tinycorelinux.net/16.x/x86/tcz/

So, the following are referenced but missing:

Code: [Select]

evas-dev.tcz evas.tcz gmpc.tcz tiff-dev.tcz audiofile.tcz opusfile-dev.tcz sdl2.tcz

More details:

Code: [Select]

$ grep -rne evas-dev.tcz --include=*.tcz.dep
ecore-dev.tcz.dep:2:evas-dev.tcz
python-ecore-dev.tcz.dep:3:python-evas-dev.tcz
python-edje-dev.tcz.dep:2:python-evas-dev.tcz
python-emotion-dev.tcz.dep:3:python-evas-dev.tcz
python-evas-dev.tcz.dep:3:evas-dev.tcz

$ grep -rne evas.tcz --include=*.tcz.dep
ecore.tcz.dep:1:evas.tcz
python-evas-dev.tcz.dep:1:python-evas.tcz
python-evas.tcz.dep:2:evas.tcz

$ grep -rne gmpc.tcz --include=*.tcz.dep
gmpc-locale.tcz.dep:1:gmpc.tcz
gmpc-tagedit.tcz.dep:1:gmpc.tcz

$ grep -rne tiff-dev.tcz --include=*.tcz.dep
GraphicsMagick-dev.tcz.dep:4:libtiff-dev.tcz
fox-dev.tcz.dep:6:libtiff-dev.tcz
gdal-dev.tcz.dep:3:libgeotiff-dev.tcz
gdk-pixbuf2-dev.tcz.dep:3:libtiff-dev.tcz
lcms2-dev.tcz.dep:2:libtiff-dev.tcz
libcamera-dev.tcz.dep:5:libtiff-dev.tcz
libgd-bin.tcz.dep:4:libtiff-dev.tcz
libgd-dev.tcz.dep:2:tiff-dev.tcz
libgeotiff-dev.tcz.dep:2:libtiff-dev.tcz
libwebp1-dev.tcz.dep:2:libtiff-dev.tcz
poppler07-dev.tcz.dep:5:libtiff-dev.tcz
sane-backends-dev.tcz.dep:2:libtiff-dev.tcz

$ grep -rne audiofile.tcz --include=*.tcz.dep
mpd-minimal.tcz.dep:2:audiofile.tcz

$ grep -rne opusfile-dev.tcz --include=*.tcz.dep
sdl2_mixer-dev.tcz.dep:4:opusfile-dev.tcz

$ grep -rne sdl2.tcz --include=*.tcz.dep
sdl2_ttf.tcz.dep:1:sdl2.tcz

Let me know if this is useful.
If it is useful, would running this "test" on 17.x/x86 be desirable at the moment (since it's in alpha)?

Thanks again for maintaining TCL!