WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: How to make Leenooks great again  (Read 3238 times)

Offline neonix

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 537
How to make Leenooks great again
« on: November 23, 2024, 06:18:58 AM »
In 2008 MontaVista presented embedded Linux that boots in 1 second. In reality it was striped out version of Linux that won't work on Desktop or Server computers.

Linux can boot faster if specific configuration file (or inside core.gz) will be loaded by bootloader. Instead probing hardware everytime computer boots, configuration file will provide informations about hardware. This solutions require cooperation of Linux kernel developers.

Distros developers could also create this kind of configuration file that contains informations about hard disks, cdroms, floppies, static ip, resolution,, filesystems and services. TinyX and TinyCore is example how optimalisations improve boot time, but boot time can be even faster than is nowadys.


http://embetrix.com/2017/05/16/embedded-linux-fast-boot-techniques/

Offline core-user

  • Full Member
  • ***
  • Posts: 200
  • Linux since 1999
Re: How to make Leenooks great again
« Reply #1 on: November 23, 2024, 07:57:14 AM »
The kernel & its modules have to cover a vast array of different hardware, embedded system only need cover their specific requirements.
AMD, ARM, & Intel.

Offline yvs

  • Jr. Member
  • **
  • Posts: 74
Re: How to make Leenooks great again
« Reply #2 on: November 23, 2024, 01:57:24 PM »
the bare minimum of applications has to be taken into account too, that leads to a lot other questions like extensions and their (un)compression in case of TCL
« Last Edit: November 23, 2024, 02:03:05 PM by yvs »

Offline neonix

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 537
Re: How to make Leenooks great again
« Reply #3 on: November 30, 2024, 04:16:21 AM »
The kernel & its modules have to cover a vast array of different hardware, embedded system only need cover their specific requirements.

RPi is embedded system. Are there any picore developers reading this thread? Many boot speed improvemets can be done by bootcodes, but why not start from strip out picore to minimum and see what we get?

Offline neonix

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 537
Re: How to make Leenooks great again
« Reply #4 on: January 06, 2025, 04:02:37 AM »
tmpfs real-time compression
RAM real-time compression with low CPU priority
all RAM should be compressed

I don't use swap partition, zram compression works only whem my system is out of free RAM.
Compression should be in real-time but in background (low cpu priority.

tmpfs real-time compression
RAM real-time compression with low CPU priority


https://www.reddit.com/r/linuxquestions/comments/qxwbl7/whats_the_best_compression_algorithm_to_use_with/?rdt=55983

Offline mocore

  • Hero Member
  • *****
  • Posts: 730
  • ~.~
Re: How to make Leenooks great again
« Reply #5 on: January 06, 2025, 11:36:05 AM »
Are there any picore developers reading this thread?
you can always spot them due to the distinctive pork pie hat!

...it appears you have developed some ideas about picore/linux

Compression should be in real-time but in background (low cpu priority.

call sagan (cosmos) just informed me
"if the sun sets in the west and all ways rises again the next morning in the east
and so its possible to figure things out
*we* can do science
and with it we can improve our lives"

that sentiment (hopefully) adds encouragement to test   

picore/linux ideas


fwiw along the lines of
https://undsci.berkeley.edu/understanding-science-101/how-science-works/testing-scientific-ideas/
Quote
You can think of scientific testing as occurring in two logical steps: (1) if the idea is correct, what would we expect to see, and (2) does that expectation match what we actually observe?

 ???
nanu nanu

Offline neonix

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 537
Re: How to make Leenooks great again
« Reply #6 on: October 08, 2025, 05:02:24 PM »
New Leenooks console concept:

2025/09/27_22-22.59
[2025/09/27:22:11.01-424066] pci_bus 0000:00: on NUMA node 0
[2025/09/27:22:11.01-428414] ACPI: PCI: Interrupt link LNKA configured for IRQ 11
[2025/09/27:22:11.01-428710] ACPI: PCI: Interrupt link LNKB configured for IRQ 5
[2025/09/27:22:11.01-428996] ACPI: PCI: Interrupt link LNKC configured for IRQ 15
[2025/09/27:22:11.01-429282] ACPI: PCI: Interrupt link LNKD configured for IRQ 3
[2025/09/27:22:11.01-429571] ACPI: PCI: Interrupt link LNKE configured for IRQ 0
[2025/09/27:22:11.01-429591] ACPI: PCI: Interrupt link LNKE disabled
[2025/09/27:22:11.01-429872] ACPI: PCI: Interrupt link LNKF configured for IRQ 0
[2025/09/27:22:11.01-429892] ACPI: PCI: Interrupt link LNKF disabled
[2025/09/27:22:11.01-430197] ACPI: PCI: Interrupt link LNKG configured for IRQ 0
[2025/09/27:22:11.01-430220] ACPI: PCI: Interrupt link LNKG disabled
[2025/09/27:22:11.01-430501] ACPI: PCI: Interrupt link LNKH configured for IRQ 10

tc@box:~$ la
total 52
drwxr-s--- 7 tc   staff  420 Sep 27 16:29 ./
drwxrwxr-x 3 root staff   60 Sep 27 16:24 ../
drwxr-s--- 2 tc   staff   40 Sep 27 16:24 .X.d/
-rw------- 1 tc   staff   48 Sep 27 16:25 .Xauthority
-rwxr-xr-x 1 tc   staff  275 Sep 27 16:25 .Xdefaults
-rw-rw-r-- 1 tc   staff   22 Sep 27 19:29 .ash_history
-rw-r--r-- 1 tc   staff  424 Jun 15 09:35 .ashrc
-rw-r--r-- 1 tc   staff   29 Dec 17  2024 .bashrc
drwx--S--- 3 tc   staff   60 Sep 27 16:29 .cache/
drwx--S--- 4 tc   staff   80 Sep 27 16:29 .config/
-rw-rw-r-- 1 tc   staff 1763 Sep 27 16:25 .jwmrc
-rw-rw-r-- 1 tc   staff 1283 Sep 27 16:25 .jwmrc-keys
-rw-rw-r-- 1 tc   staff  148 Sep 27 16:25 .jwmrc-ondemand
-rw-rw-r-- 1 tc   staff 1465 Sep 27 16:25 .jwmrc-theme
-rw-rw-r-- 1 tc   staff  730 Sep 27 16:25 .jwmrc-tray
drwxr-s--- 4 tc   staff   80 Sep 27 16:29 .local/
drwx--S--- 3 tc   staff   60 Sep 27 16:29 .pki/
-rw-r--r-- 1 tc   staff  920 Jun 15 09:35 .profile
-rwxr-xr-x 1 tc   staff  103 Sep 27 16:25 .setbackground
lrwxrwxrwx 1 root staff   20 Sep 27 16:25 .wbar -> /usr/local/tce.icons
-rwx------ 1 tc   staff  550 Sep 27 16:25 .xsession