Recent Posts

81

TCE Bugs / Re: Bash extension

« Last post by CentralWare on June 27, 2026, 01:40:48 PM »

I have to wipe the machine in question and start over from scratch once I have ollama set up as an extension -- if it repeats I'll deliver a complete step-by-step.
Thanks!

82

TCE Talk / Re: Firefox latest

« Last post by Rantanplan on June 27, 2026, 10:17:02 AM »

Hello @Rich,

TH

Hi Rantanplan
... you need to reboot in order for updates to take effect.

I did it, but...

Now, TCL runs very good and Firefox too, that's the most important thing. :-)

Friendly.

83

Programming & Scripting - Unofficial / busybox fork, micro self-extracting payload, micro qemu

« Last post by Roberto A. Foglietta on June 27, 2026, 09:18:31 AM »

Hi all,

I have used TinyCore in the past also in company/consultant works (for USB bootable) like these project:

- https://github.com/robang74/tinycore-editor/tree/main/busybox/patches

These patches applied to the 1.34 allows to do complex scripting advanced debug because I coded bash like trap and signal handling.

About busybox itself, I created a fork which is 135+ commits haed and the branch presented is my cherrypicking integration:

- https://github.com/robang74/busybox (branch uchaosys)

Which I use in this 2MB linux kernel + rootfs tiny system (boots in 0.1s with 32MB of RAM and with 64MB does qemu-in-qemu) with a reduced footprint 3MB (roms included) qemu q35, kvm-accel, tce but only virtio-hw compiled in:

- https://github.com/robang74/uchaosys

So, how did I managed to shrink a 33MB dynamic linked binary into a 3MB static linked portable app? Cutting everything is obsolete, out of scope and not useful in the most general case (e.g. we love virtio HW emulation because tends to be passtrough as much as possible and do not bother us with insane proprietary bloatware drivers/firmwares because we already have on the bare-metal installation).

- https://github.com/robang74/uchaosys/tree/v074/qemu

However, cutting stuff brought to 7.5MB the next step as been accomplished creating a 512-byes (a single `dd` block) payload in Assembler which is able to read after itself take the gzip attached, send to zcat (or equivalent) and run the extracted ELF (or script) on the fly in RAM only

- https://github.com/robang74/uzpexec

This tool is also very powerful / useful when it comes to run stuff from wget which arrived gzipped (or any other supported compression format that can be decompressed on STDOUT, like xzcat).

I am aware that TinyCore package system (like every distro) relies on compressed packages and smart compression tools skips to compress files that already has been compressed. Therefore there is no an immediate advantage using uzpack (conversion to compressed executable) in general.

Instead, when it comes to use single file binary like qemu or PractRand RNG_test, it becomes quite interesting because break down the barrier/separation between installation & run, and allows the idea that everything that can access by wget, can be put in run on the fly and only RAM (scary but also dawn useful).

I hope this helps, R-

84

TCE Bugs / Re: Bash extension

« Last post by Juanito on June 27, 2026, 08:33:49 AM »

I don’t see that - I see bash working as expected..

85

TCE Bugs / Bash extension

« Last post by CentralWare on June 27, 2026, 07:24:10 AM »

Good morning everyone!

@juanito:

I'm about to turn TinyCore into an LLM/AI foundation and while preparing to build Nvidia data-center drivers, I hit a brick wall right off the bat...  bash has an oops with library locations.

Code: [Select]

tc@5610C:/$ ldd /usr/local/bin/bash
        linux-vdso.so.1 (0x00007f3590edc000)
        libreadline.so.8 => not found
        libhistory.so.8 => not found
        libncursesw.so.6 => /usr/local/lib/libncursesw.so.6 (0x00007f3590d99000)
        libc.so.6 => /lib/libc.so.6 (0x00007f3590c0d000)
        /lib/ld-linux-x86-64.so.2 (0x00007f3590ede000)

Readline, etc. are all installed due to the bash.dep - bash just expects to find the missing libraries in /usr/lib instead of /usr/local/lib and doesn't look elsewhere.
This is a raw install of TCL17x64 where I removed all extensions and persistence before posting "just to make sure."

86

Release Candidate Testing / Re: Core v17.1beta1

« Last post by Stefann on June 27, 2026, 03:33:44 AM »

@GNU, @Rich,
Thanks, separating initrd files with a ',' (and no spaces) worked!
I had googled for using multiple initrd on extlinux but missed the ',' in the explanation.
As my 'k' key was not working and my normal working directory is called "work" (with a k) it became very difficult to continue

Anyway, modified extlinux.conf and rebooted. Now it works.
I have only 1 kernel extension: usb-serial-x.y.z-tinycore.tcz which is not needed for booting so I could download that after boot.

During the troubleshooting of my usb-serial issue I invested in "fixed installing a service monitor and keyboard in the cupboard where my system is located". That now gives a real good advantage in testing this. I can just do the beta as an extra boot option and "if it does not work" I'm no longer stuck on a non-functional remote connection.

Results so far on TC17.1 beta running on VIA EDEN 32bit 1core 500MHz cpu
tc@huis:~$ uname -a
Linux huis 6.18.35-tinycore #1 SMP Fri Jun 19 00:05:19 UTC 2026 i686 GNU/Linux

- Boot OK
- 'k' key working again (was a weird issue anyway)
- ssh OK
- VNC OK
- samba OK
- flwm OK
- X0VNCserver OK
- usb-serial-6.18.35-tinycore.tcz works but..... will have to see whether it crashes after duration test. Now testing

87

TCB Talk / Re: copy and pasting files with emelfm

« Last post by Rich on June 26, 2026, 04:39:33 PM »

Hi JunkYard
Ctrl-C  Copies what is highlighted.
Ctrl-V  Pastes what you copied.

These control codes have existed as long as I can remember.
I even used them back when I used to use Windows.

88

TCB Talk / Re: copy and pasting files with emelfm

« Last post by Juanito on June 26, 2026, 04:31:59 PM »

I noticed it had 2 search term windows. one on the left and one on the right? so you are saying set the left as drive to copy from and right to to paste to

Affirmative

Vice versa will also work

89

TCB Talk / Re: copy and pasting files with emelfm

« Last post by JunkYard on June 26, 2026, 04:07:59 PM »

Greetings!

So I load emelfm up. then load my drive up I want. find the file I want. right click and can not see a copy option. then press ctrl+c. Then I go to the other drive that I want to paste and press ctrl+paste and nothing happens!

Any help please?
Thanks

Sorry it was a typo
i ment ctrl+p. did not seam to work

90

TCB Talk / Re: copy and pasting files with emelfm

« Last post by JunkYard on June 26, 2026, 04:04:54 PM »

..but emelfm is a two pane file manager - if you have one pane set to the source directory and the other pane set to the destination directory, you can highlight the file and click on the copy button.

I noticed it had 2 search term windows. one on the left and one on the right? so you are saying set the left as drive to copy from and right to to paste to