[Current version dev thread] - Usage of SliTaz 4.0 / rolling

SliTaz Forum » English Support » Live and installation

[Current version dev thread] - Usage of SliTaz 4.0 / rolling

(506 posts) (13 voices)

Started 1 year ago by shann
Latest reply from shann
This topic is not a support question

Tags:

No tags yet.

« Previous 1…262728…34 Next »

shann

offline
Administrator

Je vois, sympa :).

Xlunch, je ne connaissais pas, ça fait penser au launcher sur Slax, (en regardant c'est lui qui l'a développé ^^).

j'ai dû renoncer au son après l'upgrade de openssl/libssl/libcrypto (1.1.1 vers 3.0.13), c'est là que le rootfs a dépassé 33.1MB.

:(, je vois qu'on a 3.3Mo pour openssl 1.1 et 4.7Mo pour openssl 3.0, au moins pour libssl.so et libcrypto.so

Pour Tazweb, oui il dépend de webkitgtk 2.4.11 et en // on a "tazweb-legacy" linké à libwebkit 1.8.3.
libwebkit 1.8.3 => libwebkitgtk-1.0w.so.0.13.4 (29.9M)
webkitgtk 2.4.11 => libwebkitgtk-1.0.so.0.22.17 (40.6M)

Pour webkitgtk, il est compilé avec --enable-video, donc inclus gstreamer-1.0 / gst-plugins-base-1.0 en dependances.

Posted 8 months ago #
sheela1

offline
Member

Salut a tous si vous avez besoin d'un coup de main pour le projet n'hésiter pas a m'écrire ;)

Posted 8 months ago #
Rantanplan

offline
Member

Bonjour @Ceel,

Je me fais le porte-paroles de MarceloCripe membre de ce forum et qui souhaite contribuer à ta demande ci-dessous :

[blockquote]Je cherche un gestionnaire de fenêtres plus léger qu'OpenBox...[/blockquote]

Contribution de MarceloCripe :
[blockquote]TinyCore a FLWM comme gestionnaire de fenêtres et est plus léger et consomme encore moins de RAM que Fluxbox, JWM et Openbox. Si le Slitaz commence à utiliser le FLWM, il sera certainement encore plus léger.[/blockquote]

Bon dimanche.
Amitiés.

Posted 8 months ago #
Ceel

offline
Administrator

Bonjour Rantanplan,

C'est exact, FLWM est très léger. Je n'y avais pas pensé (bien qu'utilisateur occasionnel de TinyCore). Je l'ai ajouté à ma liste de WM à évaluer.
Je n'ai pas retrouvé trace de cette demande de MarceloCripte. Eventuellement, je peux tenter de l'empaqueter s'il veut le tester, car de mon côté je ne l'ai pas mis dans mes WM prioritaires.
Je cherche un WM léger mais pas forcément le plus léger ; plutôt un compromis entre légèreté et possibilités offertes.

Bonjour shann,

C'est bien le launcher de Slax. Ca faisait un moment que j'avais envie de le tester sur SliTaz.

Bon weekend à tous les deux.

Posted 7 months ago #
Ged

offline
Member
Hello all,

My first post here.

Until the day before yesterday I'd never heard of SliTaz. :/

Thank you all for all your work on it. It looks great for my purposes.

Briefly I'm looking for a minimal 32-bit operating system which I can:

1. keep up to date - the kernel in particular, even if I have to build it myself - and
2. use to build and run DNS (bind), HTTP (apache2) and SMTP (sendmail) servers which do nothing else.

I am not interested in X, GUIs, and the frills, bells and whistles which go with them.

I am interested in security - this means that

3. logging is very important (I use syslog-ng),
4. the box must always know the correct time to within a few milliseconds (I use Chrony), and
5. I need to be able to manage iptables/ipsets rules in bulk (mostly Bash scripts).

None of that should present issues to the Linux kernel, but recently, here, it has done.

The servers run on headless VirtualBox 32-bit VMs with very little memory (the DNS servers run with 128M RAM). They are managed remotely using ssh. At the moment they run a more or less stock Debian Bullseye, but with Bullseye the most recent kernel that I have been able to boot on these VMs is 4.19.0. Before Bullseye the systems were fine, but now, after apt-get upgrade, the systems will not boot until I replace the kernel with something older. In addition, since security updates of about a year ago, the real-time clocks on some of the VMs have become unstable to the point of being useless.

Although the host system is 64-bit, the VMs are limited to 32-bit because of restrictions imposed by the hardware (host CPUs) and VirtualBox itself. I have been running this setup for many years, and I do not feel comfortable switching to a different virtualization system (of any description, including things like Docker).

What I would like to do is start more or less from scratch with a minimal system instead of one of the more well-known and increasingly bloated distributions. I've used Debian because of the simplicity of security updates, but an alternative seems necessary since more often than not the security upgrades now break the operating system.

I've followed this thread and it looks very promising. Obviously a lot of work has been done to get SliTaz where it is now. Maybe I can make a small contribution by building kernels.

Here is what I have done so far.

Using some of the .ISO files for example in ~shann/slitaz-current-stuff/2023xxxx/
I have attempted to start the systems on a spare VM. Using VirtualBox it's very quick and easy to do this for any .ISO file. If I just drop he ISO in the appropriate directory and point the VM's virtual DVD drive to it, the VM will attempt to boot from that ISO and I can tail the kernel log.

The results so far are below.
```
slitaz-current-base-hybrid-20230911.iso 512M    OK
slitaz-current-base_2023.10.29.iso      512M    OK
slitaz-current-base_2023.11.07.iso      512M    OK
slitaz-current-core-pae_2023.12.02.iso  512M    Kernel panic - system is deadlocked on memory
slitaz-current-core-pae_2023.12.02.iso  768M    OK
slitaz-current-core_2023.12.02.iso      512M    OK
slitaz-current-core_2023.12.17.iso      512M    Kernel panic - system is deadlocked on memory
slitaz-current-core_2023.12.17.iso      768M    OK
slitaz-current-core-pae_2023.12.17.iso  512M    Kernel panic - system is deadlocked on memory
slitaz-current-core-pae_2023.12.17.iso  768M    OK
slitaz-current-core_2023.12.23.iso      768M    OK
slitaz-current-core-pae_2023.12.23.iso  768M    OK
slitaz-current-base_2024.05.27.iso      512M    Kernel panic - Attempted to kill idle task!
slitaz-rolling.iso                      512M    Kernel panic - Attempted to kill idle task!
```
The "attempted to kill idle task" kernel panic seems to be the same problem I see in recent Debian kernels which I have tried (5.x, 6.x) and other recent "minimal" systems too (Tinycore, Antix, ...). The most recent Tinycore system I could boot for example was Tinycore 10.1 from February 2020.

It would be great if I could use a script (or maybe several scripts) to create SliTaz "base" .ISOs with custom kernels. I have seen references to "woks" and "cooking" but I don't seem to be able to find what I need to build the .ISOs - maybe I'm looking in the wrong places. Ideally to begin with I'd like to be able to build one or more of the .ISOs in my list above as an exercise, so that I can tell that I'm doing it more or less right. As well as "base" .ISOs I'd be happy to build "core" and other .ISOs if they might be useful to anyone.

If there are build systems which I could use for this, where should I be looking for them?
Posted 7 months ago #
shann

offline
Administrator

Hi Ged,

Infact slitaz could be a good choice for your usage.

For me it's strange that you have issue on virtualbox but i found this
https://forums.virtualbox.org/viewtopic.php?t=107195

Said with 1 CPU assigned issue, not with 2 CPUs assigned.

Which is version of Virtualbox do you have, for 32bits limitation it's due of CPU svm/vmx miss options i think ?
In this topic https://forums.virtualbox.org/viewtopic.php?f=1&t=62339, talk about limitation for CPU don't have this options.
no x64 guests, and one vCPU only.

For current until February iso use 4.19.307 kernel, and since February switched to 5.10 kernel branch (could be explain error you see).
But for rolling, kernel is 3.16.55, in case should work.

Also for Kernel panic - system is deadlocked on memory, infact due of rootfs size of Core (full desktop) that required more of 512M.
=> concerning this point, i need to work on it to optimize it.

you can read and follow this as begin for understood how create custom livecd
https://doc.slitaz.org/en:handbook:genlivecd

wok is our source repository for all packages.
cooking do reference of development version.

Posted 7 months ago #
Ged

offline
Member

Hi Shann,

Thank you for your very useful reply.

Yes, I have seen the VirtualBox threads which you pointed out for me. :(

Unfortunately because of the hardware limitations which I mentioned I cannot use 2 CPUs, and I cannot upgrade VirtualBox from version 6 which I am currently using. The 32 bit limitation is caused by the lack of hardware virtualization support in the host (actually in the host BIOS). I could replace the host (and probably at some point in the distant future I will), but it has been very reliable for many years and I do not want to change to an unknown quantity for all my virtual servers. Even with a known quantity, it's quite enough work to keep them happy.

It might well be that if I could select a second CPU things would work, but, even though I do not have that option, I am not sure that I actually want it! These servers have all run just fine for many years using a single CPU for each server.

I am hoping that I will be able to build more recent kernels without some feature which is causing my problems so that I will be able boot a recent kernel with 1 CPU on VirtualBox 6.x - but I must admit it is just a hope, and of course if there is such a feature I first have to find it. This is why I expect to be building a lot of kernels. :(

Agreed you need to work on reducing the memory usage if SliTaz won't boot in 512M. :) :) :)

Thank you for the link to handbook:genlivecd. That will be my light reading for this weekend...

Have a good one, and thanks again. :)

Ged.

Posted 7 months ago #
Ceel

offline
Administrator
Bonsoir shann,

Petit souci avec mtpaint aujourd'hui ; ça faisait quelques semaines que je ne l'avais pas utilisé.
Voici les messages lorsque je le lance depuis un terminal :
(mtpaint:6056): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (mtpaint:6056): GLib-GObject-CRITICAL **: g_object_unref: assertion 'val !=NULL' failed Segmentation fault

J'en profite pour te signaler un autre dysfonctionnement, mais pas bloquant, à chaque fois que je lance Gparted. Lors du scan du disque dur :
```
        Libparted Error
Error informing the kernel about modifications to partition
/dev/sda4 -- Invalid argument.  This means Linux won't know
about any changes you made to /dev/sda4 until you reboot
-- so you shouldn't mount it or use it in any way before
rebooting.
        [ Cancel ]        [ Ignore ]
```
Après avoir cliqué (2 fois) sur [Cancel] ou (1 fois) sur [Ignore], les partitons s'affichent :
```
Partition	File System
/dev/sda1	linux-swap
/dev/sda2	ext3
/dev/sda3	ext2
/dev/sda4	extended
  /dev/sda5	ext3
  /dev/sda6	ext3
```
Posted 7 months ago #
Ceel

offline
Administrator

Trouvé pour mtpaint. C'est la mise à jour de gdk-pixbuf 2.42.6 vers 2.42.12 qui crée le problème.

Posted 7 months ago #
Ged

offline
Member
Hi Shann,

Well, it took rather less than the whole weekend. :(

I don't know if this should stay in this thread or if I should start another one.

The latest base won't boot, so I'm using base from 7 November 2023.

I started a VM with 768M RAM from the LiveCD, selected UK keyboard at the first screen and just hit return at the next two. SliTaz picked up a local IP from my DHCP server and put the local search path in resolv.conf. It didn't pick up my nameservers (I haven't yet looked into why) so I edited resolv.conf to add two (my local primary and a remote secondary). Network access and name resolution seem to work fine.

Looking at handbook:genlivecd I tried to generate a custom LiveCD according to the instructions but I failed at the first step:
```
root@slitaz:~# tazlito list-flavors
Connecting to people.slitaz.org (141.94.188.35:80)
Connecting to people.slitaz.org (141.94.188.35:443)
wget: server returned error: HTTP/1.1 404 Not Found

List of flavors
================================================================================
================================================================================

root@slitaz:~#
```
So I tried to look at the tazlito 'man' page using 'man tazlito' (as root or tux, no difference) and the displayed text looks like this:
```
8<----------------------------------------------------------------------
                     Tazlito Manual

</div>
             Copyright C <span class="year"></span> SliTaz GNU/Linux

standard input lines 1-4/4 (END)
8<----------------------------------------------------------------------
```
None of this looks like problems with the VM, have I missed something?

No rush. At the moment my primary NS is resetting its clock every minute, good enough for MIT. :)
Posted 7 months ago #
shann

offline
Administrator

Bonjour Ceel,

En effet il s'avère que la version gdk-pixbuf 2.42.12 créer un segfault mtpaint.
Après debug avec gdb, je vois que ce serait en lien avec g_type_check_instance_is_fundamentally_a() from /usr/lib/libgobject-.20.so.0

Ce qui est étrange c'est que des infos que j'ai trouvé, ce serait déjà fixé depuis un moment :/.

Si je construit mtpaint avec gtk3, pas de soucis avec la 2.42.12, mais gtk2 segfault.

J'ai downgrade gdk-pixbuf en 2.42.6 et appliquer le patch pour la CVE-2022-48622.
gdk-pixbuf et gtk+ ont été reconstruit ainsi que mtpaint

Hi Ged,

Infact for current version no flavors available that could be explain 404 Not Found :/

For man page, infact seem try to display manual html page :(
You can see it on "Applications > Documentation > Tazlito manual"

Posted 7 months ago #
Ged

offline
Member

Hi Shann,

Will 'Applications->Documentation->Manual' work with the base install, without X, and with no GUI...?

(I'm sure I'll read the manual somehow - the point was that 'man' seems to be broken in base.:)

Don't worry, I'll look into it when I have time. Are we OK using this thread?

Ged.

Posted 7 months ago #
shann

offline
Administrator

Hi Ged,

Sorry infact confusing that you have base iso, in same time i fix issue on mtpaint and forget this.

For thread, think good idea that you create one.

Posted 7 months ago #
alanyih

offline
Administrator
mesa-dri - hardlink

hrwxr-xr-x root/root 0 2022-01-28 20:52 usr/lib/dri/i915_dri.so link to usr/lib/dri/i830_dri.so
hrwxr-xr-x root/root 0 2022-01-28 20:52 usr/lib/dri/i965_dri.so link to usr/lib/dri/i830_dri.so
hrwxr-xr-x root/root 0 2022-01-28 20:52 usr/lib/dri/iris_dri.so link to usr/lib/dri/crocus_dri.so

slitaz-current

tux@slitaz:~$ tazpkg -s mesa-dri

Search result for "mesa-dri"
=====================================================================
Installed packages
--------------------------------------------------------------------------------
mesa-dri 21.3.5 x-window
mesa-dri-ati 21.3.5 x-window
mesa-dri-crocus 21.3.5 x-window
mesa-dri-intel 21.3.5 x-window
mesa-dri-iris 21.3.5 x-window
mesa-dri-nouveau 21.3.5 x-window
mesa-dri-virtio 21.3.5 x-window
=====================================================================
7 installed packages found for "mesa-dri"
[..]

tux@slitaz:~$ ls -l /usr/lib/dri
total 225488
-rwxr-xr-x 1 root root 21190112 Mar 4 17:04 crocus_dri.so
-rwxr-xr-x 1 root root 13581848 Jan 14 21:02 i830_dri.so
-rwxr-xr-x 1 root root 13581848 Jan 14 21:02 i915_dri.so
-rwxr-xr-x 1 root root 13581848 Jan 14 21:02 i965_dri.so
-rwxr-xr-x 1 root root 21190112 Mar 4 17:04 iris_dri.so
-rwxr-xr-x 1 root root 21190112 Mar 4 17:04 nouveau_dri.so
-rwxr-xr-x 1 root root 13581848 Mar 4 17:04 nouveau_vieux_dri.so
-rwxr-xr-x 1 root root 13581848 Jan 14 21:01 r200_dri.so
-rwxr-xr-x 1 root root 16157480 Jan 14 21:01 r300_dri.so
-rwxr-xr-x 1 root root 16157480 Jan 14 21:01 r600_dri.so
-rwxr-xr-x 1 root root 13581848 Jan 14 21:01 radeon_dri.so
-rwxr-xr-x 1 root root 16157480 Jan 14 21:01 radeonsi_dri.so
-rwxr-xr-x 1 root root 16157480 Jan 14 21:01 swrast_dri.so
-rwxr-xr-x 1 root root 21190112 Mar 4 17:04 virtio_gpu_dri.so

tux@slitaz:~$ du -sh /usr/lib/dri
220.2M /usr/lib/dri

VS.

slackware-15

live@darkstar:~$ ls -l /usr/lib/dri
total 424744
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 crocus_dri.so*
-rwxr-xr-x 6 root root 16067956 Jan 28 2022 i830_dri.so*
-rwxr-xr-x 6 root root 16067956 Jan 28 2022 i915_dri.so*
-rwxr-xr-x 6 root root 16067956 Jan 28 2022 i965_dri.so*
-rwxr-xr-x 1 root root 975 Feb 14 2021 i965_drv_video.la*
-rwxr-xr-x 1 root root 8251412 Feb 14 2021 i965_drv_video.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 iris_dri.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 kms_swrast_dri.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 nouveau_dri.so*
-rwxr-xr-x 3 root root 12301628 Jan 28 2022 nouveau_drv_video.so*
-rwxr-xr-x 6 root root 16067956 Jan 28 2022 nouveau_vieux_dri.so*
-rwxr-xr-x 6 root root 16067956 Jan 28 2022 r200_dri.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 r300_dri.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 r600_dri.so*
-rwxr-xr-x 3 root root 12301628 Jan 28 2022 r600_drv_video.so*
-rwxr-xr-x 6 root root 16067956 Jan 28 2022 radeon_dri.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 radeonsi_dri.so*
-rwxr-xr-x 3 root root 12301628 Jan 28 2022 radeonsi_drv_video.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 swrast_dri.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 virtio_gpu_dri.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 vmwgfx_dri.so*
-rwxr-xr-x 11 root root 26667324 Jan 28 2022 zink_dri.so*

live@darkstar:~$ tar tvf mesa-21.3.5-i586-2.txz | grep usr/lib/dri
```
drwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/
-rwxr-xr-x root/root  26667324 2022-01-28 20:52 usr/lib/dri/crocus_dri.so
-rwxr-xr-x root/root  16067956 2022-01-28 20:52 usr/lib/dri/i830_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/i915_dri.so link to usr/lib/dri/i830_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/i965_dri.so link to usr/lib/dri/i830_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/iris_dri.so link to usr/lib/dri/crocus_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/kms_swrast_dri.so link to usr/lib/dri/crocus_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/nouveau_dri.so link to usr/lib/dri/crocus_dri.so
-rwxr-xr-x root/root  12301628 2022-01-28 20:52 usr/lib/dri/nouveau_drv_video.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/nouveau_vieux_dri.so link to usr/lib/dri/i830_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/r200_dri.so link to usr/lib/dri/i830_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/r300_dri.so link to usr/lib/dri/crocus_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/r600_dri.so link to usr/lib/dri/crocus_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/r600_drv_video.so link to usr/lib/dri/nouveau_drv_video.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/radeon_dri.so link to usr/lib/dri/i830_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/radeonsi_dri.so link to usr/lib/dri/crocus_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/radeonsi_drv_video.so link to usr/lib/dri/nouveau_drv_video.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/swrast_dri.so link to usr/lib/dri/crocus_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/virtio_gpu_dri.so link to usr/lib/dri/crocus_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/vmwgfx_dri.so link to usr/lib/dri/crocus_dri.so
hrwxr-xr-x root/root     	0 2022-01-28 20:52 usr/lib/dri/zink_dri.so link to usr/lib/dri/crocus_dri.so
```
live@darkstar:~$ du -sh /usr/lib/dri
61M /usr/lib/dri

mesa-21.3.5-i586-2.txz 2022-01-28 21:53 20M
http://slackware.nl/slackware/slackware-15.0/slackware/x/mesa-21.3.5-i586-2.txz
Attachments
mesa-hardlink.png (23.3 KB, 110 downloads) 7 months old
Posted 7 months ago #
shann

offline
Administrator

Hi alanyih,

Oh nice catch thanks :).

I adjust receipt of mesa-dri-* packages to use symlink.
Reduce space used by 85% (220Mo vs 33Mo)

Posted 7 months ago #

RSS feed for this topic

« Previous 1…262728…34 Next »

Reply »

You must log in to post.

[Current version dev thread] - Usage of SliTaz 4.0 / rolling

Attachments

Reply »