Recent Posts

21

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by gadget42 on March 02, 2026, 09:49:47 AM »

as i am always trying to learn more about topics as they come along casually...i used duckduckgo-lite to search:

https://start.duckduckgo.com/lite/?q=pkill+udhcpc

and at least right now(post date/time) a tcl forum post is the first result listed:

https://forum.tinycorelinux.net/index.php/topic,20223.0.html

great that the forum continues to be present in search results!

22

TCB Talk / Re: Installing on a Tatung TWN-5213 CU

« Last post by gadget42 on March 02, 2026, 09:19:18 AM »

this might help others to follow along in the journey:

https://www.manualshelf.com/manual/tatung/twn5213/user-manual-english.html

23

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by Rich on March 02, 2026, 08:45:02 AM »

Hi patrikg
I know. I do tend to include the nodhcp boot code.
I leave the pkill in there for a couple of reasons:

1. I copy this script anytime I set up a new machine or TC version.
   The pkill protects me if I forget the nodhcp boot code.

2. I sometimes post this for new users wanting a static IP. The pkill
   ensures it will work regardless of the new users skill level, knowledge
   of boot loaders, and knowledge of boot codes. And, this way I don't
   have to try to walk them through boot loader and boot code changes.

24

TCB Bugs / Re: Module.symvers and System.map Missing for TC 17.x

« Last post by Juanito on March 02, 2026, 04:42:41 AM »

The Module.symvers file used to be useful to compile kernel modules quickly, but it seems this was dropped after linux-5.x.y.

It sounds like you didn't copy config-6.18.2-tinycore64 to .config and "make oldconfig" before you started?

25

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by patrikg on March 02, 2026, 02:18:43 AM »

You can remove the line:

Code: [Select]

pkill udhcpc
And add the kernel commmand line argument:

Code: [Select]

nodhcp
See:
https://distro.ibiblio.org/tinycorelinux/faq.html#bootcodes

To gain a little boot time.

26

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by Rich on March 02, 2026, 12:23:45 AM »

Hi _matthew_

... the bootsync file that is called before the bootlocal file, ...

Near the end of  /etc/init.d/tc-config , the system restores the files you
backed up. Shortly after that, bootsync is called and clobbers your hosts
file. Take a look at  /usr/bin/sethostname  and you'll see it too.

I haven't found what what alters resolv.conf yet.
On my systems, it's a script I use to set a static IP:

Code: [Select]

tc@E310:~$ cat /opt/eth0.sh
#!/bin/sh
pkill udhcpc
ifconfig eth0 192.168.1.35 netmask 255.255.255.0 broadcast 192.168.1.255 up
route add default gw 192.168.1.1
echo nameserver 192.168.1.1 > /etc/resolv.conf
echo nameserver 68.237.161.12 >> /etc/resolv.conf
tc@E310:~$

... So the first echo nameserver 192.168.1.151 >  /etc/resolv.conf sets it up
long enough for ntp to resolve the hosts it needs to start.  Sometime beteween
the first one and the second one, it gets plowed. ...

These 3 commands are the only thing run between the echo commands:

Code: [Select]

/usr/sbin/ntpd -p pool.ntp.org
/usr/sbin/crond -b
/usr/local/etc/init.d/openssh startRestart each one manually to figure out who the troublemaker is.

27

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by Rich on March 02, 2026, 12:23:28 AM »

Hi _matthew_

Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:

[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]

It will appear like this in your post:

Code: [Select]

[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.

28

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by _matthew_ on March 01, 2026, 10:10:08 PM »

Hello guys, and thank you for responding!

I need to define a bunch of static IP's that are out of the dhcp servers range in /etc/hosts.  Dnamasq reads this by default.  If I put /etc/hosts in the /opt/.filetool.lst file and run filetool I can see that it grabs my /etc/hosts.  I can also go into the tar file filetool creates and verifies that the contents are correct.  So I do a reboot, and when I go back and look at /etc/hosts, my version is gone and the stock version is back.  I have similar issues with /etc/resolve.conf.  I have got past them with band aid fixes:

This is ugly but it is the winning combo:

Code: [Select]

#!/bin/sh
# put other system startup commands here
/bin/date >> /mnt/sda1/reoot.log
/sbin/syslogd -b 3
/sbin/ifconfig eth0 192.168.1.145 netmask 255.255.255.0 up
/sbin/route add default gw 192.168.1.1
echo nameserver 192.168.1.151 >  /etc/resolv.conf
/usr/sbin/ntpd -p pool.ntp.org
/usr/sbin/crond -b
/usr/local/etc/init.d/openssh start
echo nameserver 192.168.1.151 >  /etc/resolv.conf
cat /etc/dnsmasq.anames > /etc/hosts
/usr/local/sbin/dnsmasq

So the first echo nameserver 192.168.1.151 >  /etc/resolv.conf sets it up long enough for ntp to resolve the hosts it needs to start.  Sometime beteween the first one and the second one, it gets plowed.  Without the second echo nameserver 192.168.1.151 >  /etc/resolv.conf the system has no name resolution until it is set again.

And to the person who sugguested the bootsync file that is called before the bootlocal file, in fact that calls the bootlocal file so without question that would get plowed under.

/usr/bin/sethostname dns
/opt/bootlocal.sh &

    [Edit]: Added code tags.  Rich

29

TCB Talk / Re: Installing on a Tatung TWN-5213 CU

« Last post by Rich on March 01, 2026, 08:32:59 PM »

Hi peasthope
If your device has a wired network connection available, then Tiny Core is sufficient.

If your device only has wifi, try Core Plus. It includes wifi drivers and firmware. If you
are lucky, yours will be included.
If drivers and firmware are not included, we can explore other options.

Hardware specifications appear to be virtually nonexistent for your device.

I recommend plugging in a USB keyboard. I don't expect the touch screen to be recognized.
Have a USB mouse handy for the GUI.

... Display resolution 1014 x 768 15 bit 65536 colorXDA ...

Actually, that's  1024 x 768 , that specification was available on the Internet.

30

TCB Talk / Re: Installing on a Tatung TWN-5213 CU

« Last post by peasthope on March 01, 2026, 05:29:15 PM »

What's the problem?

Specs for the target computer

Tatung TWN-5213 CU CPU Transmeta TM5800 733MHz
CPU Transmeta TM5800 733MHz
https://en.wikipedia.org/wiki/Transmeta_Crusoe#Software_limitations
states "The Crusoe processor supports MMX but not SSE."

Memory 256MB DDR-SODIMM
Storage 512 MB Compact Flash, upgraded to  4 GB
Display resolution 1014 x 768 15 bit 65536 colorXDA
USB 2

Appears I have three possibilities: Micro Core, Tiny Core and Core Plus.
Of the three, which is the most capable likely to work on the hardware?
Is X feasible?

Thanks,                     ... P.