Recent Posts

1

CorePlus / Re: Absolutelly persistent TCC installation on HDD, instead load everything into RAM

« Last post by patrikg on Today at 05:32:56 PM »

There is a good wiki with a list of distros that running from RAM.

https://en.wikipedia.org/wiki/List_of_Linux_distributions_that_run_from_RAM

2

TCB Q&A Forum / Re: /var/log/wtmp rotating?

« Last post by Stefann on Today at 03:42:25 PM »

Hi rich,
Thanks!
Will do,
As said.. need to wait for weekend

3

CorePlus / Re: Absolutelly persistent TCC installation on HDD, instead load everything into RAM

« Last post by mocore on Today at 03:25:25 PM »

related topic ( wrt ram use and 'scatter mode' install )
https://forum.tinycorelinux.net/index.php/topic,27314.msg175742.html#msg175742

4

CorePlus / Absolutelly persistent TCC installation on HDD, instead load everything into RAM

« Last post by asm_tcz on Today at 02:14:26 PM »

Hi there, first post!

I know, that probably it is against of the TinyCoreLinux philosophy, but... Is there a relatively documented process of how could I persistently install TCC on HDD, without using initramfs and the unpack-into-RAM .tcz package mechanism?

Goal is to save as much RAM as possible for userspace softwares. Here's why:

I have an old Compaq evo N410c notebook (mass produced in 2003), with composite analog video output what I really need for my project. I'm searching a system only, and just only for playing 800x600 MPEG1 video files. Slow booting time and much used diskspace is not a problem. Therefore, the goal would load the kernel, kernel modules, daemons and other software stuffs that needed but everything from HDD, uncompressed form where it's possible and save the RAM for the video files.

Is it possible with TCC with "not so many" additional efforts?

I've searched and tried other distros as well, but... the recent SliTaz is buggy, was a two-day nightmare to install it persistently and unfortunatelly XOrg/MPV/mplayer cannot do the task : mpv can't see any usable output driver (despite the XOrg and the VM can run with the legacy ATI Radeon driver), and almost nor mplayer. However, mplayer can somehow find it's way to produce a video output, but has no color on X11 (it's grayscale there), and despite with a little hack it could produce output using the framebuffer on tty1, the produced color palette was a TOTAL mess/misleading. Whatever I tried, didn't help anything. =(
I've tried also PuppyLinux, but the output with the composite was even more crashy/buggy. Other distros even couldn't detect the composite output. =[

5

TCB Q&A Forum / Re: /var/log/wtmp rotating?

« Last post by Rich on Today at 01:02:29 PM »

Hi Stefann

... They claim “better to overwrite than to remove” to avoid inode number gets changed which makes me feel your

Code: [Select]

sudo mv NewWtmp /var/log/wtmpIs probably less wanted. ...

I tried that initially but it won't work. The  echo  command strips out
all the zero chars (0x00) from the stream.

Try this:

Code: [Select]

Entries=100 ; tail -c $(($Entries*384)) /var/log/wtmp > NewWtmp && sudo cp NewWtmp /var/log/wtmp; rm -rf NewWtmpThat should leave the inode number unchanged.
See here:
https://stackoverflow.com/questions/62355054/copy-and-moves-command-effect-on-inode

6

piCore Test Releases / Re: piCore15.0 Beta

« Last post by Paul_123 on Today at 12:44:49 PM »

Shrinking and expanding a fat32 partition is not possible.  From what I can see I changed the partition size before I released beta1, and the old size was only 64MB.   Did you manually create a sdcard then copy the contents?

I don't want to release an image with only a 64MB partition, but what is the right number?

7

TCB Q&A Forum / Re: /var/log/wtmp rotating?

« Last post by Stefann on Today at 11:35:16 AM »

Hi rich,
Thanks,
As said, it will need to wait until next weekend before I will try.
In the mean time I keep reading (on iPad with a whiskey on the couch ).

Based on this info: https://www.unix.com/aix/226435-wtmp-empty-everyday.html
They claim “better to overwrite than to remove” to avoid inode number gets changed which makes me feel your

Code: [Select]

sudo mv NewWtmp /var/log/wtmpIs probably less wanted.

I was actually thinking to use your earlier “normal log” solution, modified to byte count:

Code: [Select]

echo "$(tail -c  19200 /var/log/wtmp)” > /var/log/wtmp
Which should give me 50 entires as 19200=50x384

I’m not trying now though. The moment I start doing so few hours pass by very quick and that does not fit the weekdays.

8

TCB Q&A Forum / Re: /var/log/wtmp rotating?

« Last post by Rich on Today at 11:07:49 AM »

Hi Stefann

... I feel the wtmp rotation can be converted similarly in a 1 line command. I will be able to figure that out. Just following the logic of the other command. ...

Maybe something like this:

Code: [Select]

Entries=100 ; tail -c $(($Entries*384)) /var/log/wtmp > NewWtmp && sudo mv NewWtmp /var/log/wtmpJust change the value of  Entries  to how much history you wish to retain.

Just for the record, the number of entries that the  "last"  command reports
may not match  FileSize/384.  It seems when you close a terminal, that action
gets logged, but  "last"  does not report it.

Here I trim wtmp to 10 entries:

Code: [Select]

Entries=10 ; tail -c $(($Entries*384)) /var/log/wtmp > NewWtmp && sudo mv NewWtmp /var/log/wtmp
This is what  last  reports:

Code: [Select]

tc@E310:~$ last -F -f /var/log/wtmp
tc       pts/8        :0.0             Mon Oct 14 10:45:55 2024 - Mon Oct 14 10:45:57 2024  (00:00)
tc       pts/7        :0.0             Mon Oct 14 09:22:07 2024   still logged in
tc       pts/7        :0.0             Mon Oct 14 08:37:22 2024 - Mon Oct 14 09:22:07 2024  (00:44)
tc       pts/7        :0.0             Sun Oct 13 08:26:48 2024 - Sun Oct 13 12:26:17 2024  (03:59)
tc       pts/5        :0.0             Sun Oct 13 08:17:32 2024   still logged in
tc       pts/5        :0.0             Sat Oct 12 09:32:51 2024 - Sat Oct 12 09:46:46 2024  (00:13)
tc       pts/5        :0.0             Wed Oct  9 21:51:27 2024 - Sat Oct 12 09:32:51 2024 (2+11:41)

wtmp begins Wed Oct  9 21:51:27 2024
tc@E310:~$It shows 7 entries.

Using the perl script found at the link in reply #5 I get this:

Code: [Select]

tc@E310:~$ ./ReadWtmp.sh < /var/log/wtmp | sort -r -k 3
Mon Oct 14 10:45:57 2024 Term     tc                pts/8 :0.0                                         
Mon Oct 14 10:45:55 2024 Normal   tc                pts/8 :0.0                                         
Mon Oct 14 09:22:07 2024 Normal   tc                pts/7 :0.0                                         
Mon Oct 14 08:37:22 2024 Normal   tc                pts/7 :0.0                                         
Sun Oct 13 12:26:17 2024 Term     tc                pts/7 :0.0                                         
Sun Oct 13 08:26:48 2024 Normal   tc                pts/7 :0.0                                         
Sun Oct 13 08:17:32 2024 Normal   tc                pts/5 :0.0                                         
Sat Oct 12 09:46:46 2024 Term     tc                pts/5 :0.0                                         
Sat Oct 12 09:32:51 2024 Normal   tc                pts/5 :0.0                                         
Wed Oct  9 21:51:27 2024 Normal   tc                pts/5 :0.0                                         
tc@E310:~$It shows 10 entries.
Note the two pts/8 entries. That was me opening then closing a terminal.
The  last  command only reports me opening the terminal at 10:45:55.

Just wanted to point that out in case anyone else notices that discrepancy.

9

piCore Test Releases / Re: piCore15.0 Beta

« Last post by ovacikar on Today at 09:36:18 AM »

Picore 15 beta 3, the p1 partition somehow got increased to 128 MB. The content still takes 54.6 MB. How do I shrink it back and reasign to p2 with resize2fs ?

If shrinking and reallocating is not possible, can it be fixed in next release?

Code: [Select]


Linux box 6.6.47-piCore #9 Sat Aug 31 14:48:51 EDT 2024 armv6l GNU/Linux

Filesystem                Size      Used Available Use% Mounted on
/dev/mmcblk0p1          126.0M     54.6M     71.4M  43% /mnt/mmcblk0p1
Previous 15 Beta 1:

Code: [Select]

Filesystem                Size      Used Available Use% Mounted on
/dev/mmcblk0p1           78.8M     54.6M     24.1M  69% /mnt/mmcblk0p1

10

piCore Test Releases / Re: piCore15.0 Beta

« Last post by ovacikar on Today at 09:35:27 AM »

duplicate post