Recent Posts

71

Corepure64 / Re: What is corepure for

« Last post by neonix on September 07, 2025, 06:57:59 AM »

It's for all people who wants to use advantage that 64 bits processor gives. Tiny Core Linux was designed to support  as much as possible, all desktop hardware.

72

Off-Topic - Tiny Core Lounge / Cessing my activity on the forum

« Last post by Vaguiner on September 07, 2025, 04:48:20 AM »

Hello, TinyCore community.

I've been using computers for almost 20 years. I tried Linux several times and never quite got the hang of it. It was thanks to TinyCore that I was able to realize this dream about three years ago. TinyCore is an excellent system, and I hope it lasts a long time.

As for me, for personal reasons, I'll have to take a permanent leave of absence.

Thank you all for your support!

73

TCE Tips & Tricks / Re: firefox 144 as last version for x86 (32 bits)?

« Last post by nick65go on September 06, 2025, 01:32:03 PM »

haven't tried/used seamonkey for a few years but it looks like they still do 32bit:

I own a Dell INSPIRON mini 10, CPU is Intel Atom A270 at 1.6GHz with 1GB RAM and 16GB SSD, display 10 inch, from stone age (year 2006-2009 maybe). It doesn't have a scratch, perfect functional (if you forget the dead battery). So it has no x86-64 instructions.

Except this laptop, I can bet that (almost) never in my life I will BUY a device with CPU on 32 bits + BIOS. First of all that all NEW laptops are UEFI + 64 bits CPU (in the countries where I travel /stay), and I do not intent to buy old devices (they can be near their end of life because wearing parts, excessive usage etc.).

Therefore 32 bits will be useful in containers, isolated / virtual machines , in our days of concern about security and privacy (for people who care). At least is a step in the right direction for protection, and speed.


FYI: Ideal software for me is code written in ASM (machine code) as Kolibri OS, or maybe x32 (small pointers 32 bits + large CPU registries 64 bits), but not much software as this in Linux distros. https://wiki.debian.org/X32Port

74

Corepure64 / Re: What is corepure for

« Last post by gadget42 on September 06, 2025, 07:01:06 AM »

@Rich, are we going to have a 20th anniversary celebration in honor of your dell? woohoo!

75

TCE Tips & Tricks / Re: firefox 144 as last version for x86 (32 bits)?

« Last post by gadget42 on September 06, 2025, 06:57:56 AM »

haven't tried/used seamonkey for a few years but it looks like they still do 32bit:

https://www.seamonkey-project.org/releases/#official

76

Corepure64 / Re: What is corepure for

« Last post by Rich on September 05, 2025, 09:05:25 PM »

Hi LubielTheStoopid
That depends on your definition of "more modern".

According to the BIOS, the machine I'm writing this on is from 04/04/2006, and
it has a 64 bit processor.

77

Corepure64 / Re: What is corepure for

« Last post by LubielTheStoopid on September 05, 2025, 08:23:27 PM »

that means corepure is for more modern machines?

78

TCE Tips & Tricks / Re: firefox 144 as last version for x86 (32 bits)?

« Last post by Juanito on September 05, 2025, 04:18:25 PM »

I’ve compiled Firefox for tinycore/piCore a number of times, it’s been difficult to do so for x86 for some time now.

79

TCE Tips & Tricks / firefox 144 as last version for x86 (32 bits)?

« Last post by nick65go on September 05, 2025, 03:39:06 PM »

https://www.phoronix.com/news/Firefox-Ending-32-bit-Linux
My understanding is that no many (if any) TC developers compile Firefox from sources. So most TC users grab a Firefox using a smart script (get-firefox-latest.sh) to grab already compiled Firefox from horse mouth. From year 2026 this will not be possible, and no Firefox securities / updates will be available easy to download for 32 bits.

This is an important / unfair kick in the back for understaffed /hobby Linux distros . At least for me, without Firefox browser I will not touch a distro for production or important LIVE things.

80

TCB Bugs / Re: PS1 bug in TC16

« Last post by nick65go on September 05, 2025, 02:53:13 PM »

Here a demo. with two fictive users (John and Smith), each with different shell prompter

Code: [Select]

❯ ls -l home/
drwxr-xr-x - abc  5 Sep 19:52  John
drwxr-xr-x - abc  5 Sep 19:53  Smith

❯ cat home/John/.profile
PS1='\u@GREEN:\w\$ '
export PS1

❯ cat home/Smith/.profile
PS1='\u@RED:\w\$ '
export PS1If you use a LOGIN SHELL, sh -l, or login, you get the user specific prompter.
But if you just SU/SUDO (switch user) , the shell prompter stays as former user:

Code: [Select]

~/Desktop/TinyCore/demo
❯ sudo chroot . /bin/login -f John
John@GREEN:~$ cd /
John@GREEN:/$ su Smith
Smith@GREEN:/$                        <==same GREEN prompter as for John, former user

Smith@GREEN:/$ sudo login -f Smith
Smith@RED:~$ exit                      <==now the new user prompter RED
Smith@GREEN:/$ ^CThe way to change the shell prompter even for a non-login shell is to have, BEFORE summon the su or sudo, the ENV (environment variable) set to a personal script somewhere, as ENV=full-path-to-that-executable-script-to-change-PS1. So every time you change user, the new sh shell will SOURCE that script.