Tiny Core Linux 13.0 released for older or lower-end x86 hardware

Tiny Core Linux 13.0 has just been released for 32-bit and 64-bit x86 systems with a recent Linux 5.15.10 kernel, and various upgrades to the packages.

Tiny Core Linux is a lightweight (~22MB ISO) Linux distribution with an FLTK (Fast Light Toolkit)/FLWM (Fast Light Windows Manager) desktop and based on the Core Project that integrates a recent Linux kernel, vmlinuz, and a root filesystem with low footprint libraries such as busybox. It’s mostly interesting for older or low-end hardware that may be slow and/or unusable with more common Linux distributions like Ubuntu or Debian.

Tiny Core Linux 13.0 Desktop
Tiny Core Linux 13.0 in Virtualbox

Tiny Core Linux 13.0 main changes:

  • 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
  • tc-config: Move nodhcp static_ip earlier, from andyj

TinyCore boot screen

I’ve quickly tried the 32-bit ISO in VirtualBox and was offered to boot it with a GUI or command line, but an option for slow devices waiting for USB for a period of time. The desktop environment (shown in the first screenshot above) is very basic with just five icons are the bottom. The only application installed is the Terminal, but you can add more including Firefox through the menu.

Tiny Core Linux 13

Right after the first boot, the system used around 30MB of RAM and 30MB of storage.

While the recent announcement is about Tiny Core Linux 13.0 for x86 systems specifically, there are also versions for the Raspberry Pi boards with PiCore v13.1 released last November 2021 compiled with either armv6, armv7, or Aarch64 flags. You’ll find the x86 and Arm images by browsing 13.x release directory.

More details may be found in the forum’s announcement.

Share this:

Support CNX Software! Donate via PayPal or cryptocurrencies, become a Patron on Patreon, or buy review samples

ROCK Pi 4C Plus
Subscribe
Notify of
guest
The comment form collects your name, email and content to allow us keep track of the comments placed on the website. Please read and accept our website Terms and Privacy Policy to post a comment.
14 Comments
oldest
newest
Sander
Sander
8 months ago

Funny: that screens looks an orginal X screen, like on SUNs, in 1989 or so.

tmunzer
tmunzer
8 months ago

For those not already familiar with Tiny Core, for using it with IOT device, there is one very interesting characteristic : after boot everything run only on memory and unless specified explicitly reboot always unmodified. No risk of system corruption caused by power interruption. For an interesting example see projet Picore Player.

avra
avra
8 months ago

You have not mentioned the main feature for embedded developers, which is that TinyCoreLinux effectively solves the problem of power off caused file system corruptions on embedded devices like Pi. Just search for options available for Persistent Home directory.

tkaiser
tkaiser
8 months ago

> power off caused file system corruptions on embedded devices like Pi

A simple commit=600 addition in /etc/fstab reduces that risk already by at least 120 times (and dramatically reduces wear and tear on the SD card at the same time).

avra
avra
8 months ago

I was not talking about reducing the risk. I was talking about eliminating it.

xander
xander
8 months ago

A journaling fs solves poweroff/crash issues.
Immutability just makes security patching more cumbersome.

itchy n scratchy
itchy n scratchy
8 months ago

Maybe something to try on my alix board…

Arnd Bergmann
8 months ago

I was curious about the minimum hardware requirements but couldn’t find anything on the website, and the wiki is currently not reachable.

Trying the minimum configuration in qemu showed that it works with

qemu-system-i386 -cdrom Core-13.0.iso -cpu 486 -M isapc -m 64M

It needs around 64MB of RAM to boot, anything under 59MB does not even get to a shell but after it boots, around 26MB is available. The 486 ISA PC is about as low as the kernel supports, only an FPU is required from the CPU.

itchy n scratchy
itchy n scratchy
8 months ago

Sounds good then for my alix

Chasx
Chasx
8 months ago

If you have an Alix you might also consider Alpine Linux (or a minimal Debian). I have a couple of Orange Pi Zeroes at home (ARM Cortex A7, 256 MB RAM) that I equipped with a custom kernel loading an Alpine image from SD Card. This complete OS image is loaded to RAM (initramfs) and contains all packages for operating as WLAN access point with some additional features (like wireguard for providing a secure connection to my server) and because it runs from RAM there is no wear and tear on the SD card (it’s not mounted after booting, just… Read more »

itchy n scratchy
itchy n scratchy
8 months ago

Hmmmm sounds weird to mee without a persistent overlay…

With ALIX there are no worries about wearing SD cards… More panic of wearing the last supplies of CF cards available…

Tuff Pro
Tuff Pro
8 months ago

I know that surely somewhere is using a 486 PC because there’s always someone for that, but is something like a 486 being used today?

I know that this Distro want to be Tiny but do they gain something by targetting a 486 CPU?

David Willmore
David Willmore
8 months ago

Typo: 22MB SIO

Should that be ISO?

itchy n scratchy
itchy n scratchy
8 months ago

No that targets the famous Standards International Organisation also known as Organisation Internationale de Normalisation 😀

Advertisement