Recent Posts

61

Final Releases / Re: Tiny Core v16.2

« Last post by gadget42 on October 31, 2025, 09:21:47 AM »

admins/mods: if this needs moved and/or titled appropriately/suitably then by all means please do.

To Juanito/curaga/Rich/Any/All, thoughts? opinions? continued advancement of _maximum_planned_obsolescence_ ?
(seems tcl people recognize and embrace _extend_recycle_repurpose_reuse_ and have a good track record of overall hardware support longevity)

subject/topic:
Introducing architecture variants: amd64v3 now available in Ubuntu 25.10

for reference see:
https://discourse.ubuntu.com/t/introducing-architecture-variants-amd64v3-now-available-in-ubuntu-25-10/71312

and:
https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels

found-via/hat-tip/kudos:
https://dev1galaxy.org/viewtopic.php?id=7496

quoting: https://dev1galaxy.org/viewtopic.php?pid=58863#p58863

Those levels were invented a few years ago by "bigtech" to obsolete older hardware and force people to upgrade to newer PCs now that the switch from 32 bit to 64 bit is no longer enough to obsolete additional older hardware. It's sort of the next step after stopping support for 32 bit cpus.

IBM (Redhat) and Suse have already gone down this road, their recent releases don't work on older 64 bit cpus any more.

I see it as a good reason to become more independent from the corporate Linux world (primarily IBM/Redhat, but also Suse and Ubuntu) and focus on pure community run distros that don't have agendas and profit motives.

That said the way Ubuntu is currently approaching this for now is sensible, as they are building packages for the different levels, so for now they aren't obsoleting older 64 bit cpus, but the cinic in me makes me think that this is just a "boiling the frog slowly" approach to avoid a shitstorm, i.e. in a few years they will likely be discontinuing support for older variants.

BTW, wikipedia lists who is behind this:

In 2020, through a collaboration between AMD, Intel, Red Hat, and SUSE, three microarchitecture levels (or feature levels) on top of the x86-64 baseline were defined: x86-64-v2, x86-64-v3, and x86-64-v4. These levels define specific features that can be targeted by programmers to provide compile-time optimizations.

https://en.wikipedia.org/wiki/X86-64

62

Remasters / Remixes - Unofficial / Re: Bootable CD with multiple versions

« Last post by Rich on October 31, 2025, 09:09:29 AM »

Hi Dacicus
You are welcome.

63

TCE Bugs / jwm has big dependencies

« Last post by neonix on October 31, 2025, 08:09:08 AM »

 Why jwm.tcz require llvm19-lib.tcz (32.10 MB) and mesa.tcz (10.96 MB)?

All dependencies has 64.90 MB.

64

Remasters / Remixes - Unofficial / Re: Bootable CD with multiple versions

« Last post by Dacicus on October 31, 2025, 12:21:00 AM »

Thank you very much, Rich!  I will study this.

65

Off-Topic - Tiny Core Lounge / Re: Bots and Google

« Last post by Paul_123 on October 30, 2025, 12:48:06 PM »

I guess that's something for all that scraping that gets done.   Its a never ending battle to keep them tamed.  Some of it is good, it would just be nice if there were not hundreds of bots doing the same damn thing.  Just scanning the logs right now,  ClaudeBot, PetalBot, GoogleBot, AmazonBot, bingbot, ThinkBot, AwarioBot, DuckAssistentBot, GPTBot are all active.

Most do respect the robots.txt directive I have to limit rates.  I did tell Bytedance and TikTok Bots to knock it off......and so far they have respected the robots.txt

66

Off-Topic - Tiny Core Lounge / Bots and Google

« Last post by Rich on October 30, 2025, 10:33:44 AM »

While reading a response to a post I made, I decided to do
a search to see if the Google bots had catalog it yet.
These were the first two entries that popped up:


None of the following entries related to Tinycore. But when
I reached the bottom of the page, I was a little surprised
to find this:


Seven out of eight suggestions referred to Tinycore.

This was the post I made:
https://forum.tinycorelinux.net/index.php/topic,27848.msg180072.html#msg180072

67

Remasters / Remixes - Unofficial / Re: Bootable CD with multiple versions

« Last post by gadget42 on October 30, 2025, 09:16:31 AM »

and this is why THIS forum(and tcl) are absolutely awesome indeed!

huge kudos Rich!

68

Remasters / Remixes - Unofficial / Re: Bootable CD with multiple versions

« Last post by Rich on October 29, 2025, 05:21:44 PM »

Hi Dacicus
I figured it out.

This is the directory structure I created:

Code: [Select]

MkISO/
|-- ISO/
|   |-- V10/
|   |   |-- boot/
|   |   |   |-- core.gz
|   |   |   `-- vmlinuz
|   |   `-- tce/
|   |       |-- copy2fs.lst
|   |       |-- onboot.lst
|   |       `-- optional/
|   |-- V15/
|   |   |-- boot/
|   |   |   |-- core.gz
|   |   |   `-- vmlinuz
|   |   `-- tce/
|   |       |-- copy2fs.lst
|   |       |-- onboot.lst
|   |       `-- optional/
|   `-- boot/
|       `-- isolinux/
|           |-- boot.cat
|           |-- boot.msg
|           |-- f1
|           |-- f2
|           |-- f3
|           |-- f4
|           |-- isolinux.bin
|           |-- isolinux.cfg
|           `-- menu.c32
|-- MkISO*
|-- RecordCD*
`-- TC10TC15.iso
TC10TC15.iso will let you boot either Tinycore10.1 or Tinycore15.0 (32 bit, Xvesa).

The MkISO script creates TC10TC15.iso from the contents of the ISO/ directory.

The RecordCD script is used to burn the image to a CD. It also contains comments
on how to identify your CD drives dev address.

Everything under the V10/ directory is the contents of the Tinycore 10.1 CD minus the isolinux/ subdirectory.
Everything under the V15/ directory is the contents of the Tinycore 15.0 CD minus the isolinux/ subdirectory.
The optional/ directories are populated. I told the tree command to only go 4 directories deep.

The isolinux/ directory under the /boot/ directory was copied from the Tinycore 15.0 CD.

isolinux.bin needs to be writable so that mkisofs can update it (chmod 600 isolinux.bin).
isolinux.cfg needs to be writable if you wish to edit it (chmod 600 isolinux.cfg).

This is the isolinux.cfg file:

Code: [Select]

DEFAULT Version10
UI menu.c32
PROMPT 0
TIMEOUT 600
ONTIMEOUT Version10
F1 f1
F2 f2
F3 f3
F4 f4

MENU TITLE TinyCore
MENU MARGIN 10
MENU VSHIFT 5
MENU ROWS 5
MENU TABMSGROW 14
MENU TABMSG Press ENTER to boot, TAB to edit, or press F1 for more information.
MENU HELPMSGROW 15
MENU HELPMSGENDROW -3
MENU AUTOBOOT BIOS default device boot in # second{,s}...

LABEL Version10
MENU LABEL Boot TinyCore-10.1
TEXT HELP
Boot TinyCore with Embedded X/GUI extensions.
ENDTEXT
KERNEL /V10/boot/vmlinuz
INITRD /V10/boot/core.gz
APPEND loglevel=3 tce=LABEL=TC10TC15/V10/tce waitusb=5:LABEL=TC10TC15

LABEL Version15
MENU LABEL Boot TinyCore-15.0
TEXT HELP
Boot TinyCore with Embedded X/GUI extensions.
ENDTEXT
KERNEL /V15/boot/vmlinuz
INITRD /V15/boot/core.gz
APPEND loglevel=3 tce=LABEL=TC10TC15/V15/tce waitusb=5:LABEL=TC10TC15
TC10TC15.iso, MkISO, and RecordCD are available for download here:
http://tinycorelinux.net/15.x/x86/TestISO/

If you want to modify TC10TC15.iso:

Code: [Select]

mkdir Work
cd work
mkdir ISO mnt
# Copy TC10TC15.iso, MkISO, and RecordCD to the Work directory.
sudo mount TC10TC15.iso mnt/
cp -a mnt/* ISO/
sudo umount mnt
# Make your changes in the ISO/ directory.
# Then, cd back into your Work directory.
# Create the new ISO file.
MkISO
# To burn a CD
RecordCD
Some error messages when booting that xwbar.lst can't be written to the tce directory.
This is expected since tce is on a CD and read only. This message is harmless.

Hope this helps.

69

TCB Talk / Re: Chromebook Laptop booting error

« Last post by Rich on October 29, 2025, 12:32:59 PM »

Hi ctor

... Unbelievable! Your idea worked -- the keyboard now works. ...

Well, it wasn't really my idea. I just found someone elses solution.

... How did you ever find this solution? ...

A lot of times it comes down to figuring out how to phrase what you
are searching for so that the search engine returns usable results.

... Thank you for your insight and persistence.

You are welcome. Glad I could help.

70

TCB Talk / Re: Chromebook Laptop booting error

« Last post by ctor on October 29, 2025, 12:19:36 PM »

A better solution is add pinctrl-cherryview to the Linux black list command.
It reuses the released modules.gz file.