SliTaz Forum

Slitaz future?

(278 posts) (29 voices)

• Started 4 years ago by guest_account
• Latest reply from alanyih
• This topic is not resolved

Tags:

No tags yet.

1. 

   gibor
   

   offline

   Moderator

   I don't know, I don't get that error. I used polkit-0.118 in mine, but then I removed everything because I didn't want to go that route. Now only the sources are left on an external partition, and I don't really know how to help you track down the source of your problem.

   It may not mean anything but one thing that sounds bad to me is:

   Gtk-WARNING **: 14:43:49.363: Locale not supported by C library.
   Using the fallback 'C' locale.

   Non so, quell'errore non mi compare. Nel mio avevo usato polkit-0.118, ma poi ho levato tutto perché non era mia intenzione seguire quella strada. Ora rimangono solo i sorgenti su di una partizione esterna e, non saprei prorpio come aiutarti a rintracciare la fonte del tuo problema.

   Può non significare nulla ma una cosa che mi suona male è:

   Gtk-WARNING **: 14:43:49.363: Locale not supported by C library.
   Using the fallback 'C' locale.

   Posted 3 years ago #
2. 

   Filou
   

   offline

   Moderator

   ... found the error...

   since I follow SliTaz' principle of minimalism, I overlooked that polkit's receipt left out a policy file that was essential here...

   Rebuilt polkit and now udisks2 went through fine...

   I will proceed with gvfs and hopefully, we have the automount/-display features enabled in pcmanfm again...

   Posted 3 years ago #
3. 

   akm
   

   offline

   Member

   I downloaded your kernel, but startx doesn't work. I saved the log, I've supplied it with this post. I think the modules still pose a problem. How do the rootfs and the overlay play together? I'm sure there's a symbolic link or a folder somewhere in the rootfs, where all of the modules are located. As I've compiled a kernel with aufs support, and upgraded my Debian installation to it, I think I could place my 5,4 gigabytes of modules from /usr/lib/modules/5.10.47/ into it, or extract them from the rootfs automaticallly built. Is there a .so file in the rootfs?

   Attachments

   1. Xorg.0.log (5.2 KB, 277 downloads) 3 years old

   Posted 3 years ago #
4. 

   akm
   

   offline

   Member

   Here's my entry for GRUB2 in the file /etc/grub.d/40_custom
   menuentry "UnderConstruction" {
search --set=root --fs-uuid ad1b45cb-a187-464a-bc12-64ad892a0b0f
linux /bzImage root=UUID=ad1b45cb-a187-464a-bc12-64ad892a0b0f ro quiet splash
initrd /boot/myrootfs64.gz /boot/ovl_modules.gz
}
   All I have on that partition are the bzImage in the root folder the rootfs.gz and the ovl_modules.gz in the /boot folder. Nothing else, not even folders other than /boot.

   Posted 3 years ago #
5. 

   gibor
   

   offline

   Moderator

   @akm
   I'm sorry but I don't speak English, I'll try with a translator and write in Italian.

   Do not use debian or similar kernels that require initrd booting. In that case errors will occur with the init which is not the default slitaz init.
   Another thing is to unpack the whole downloaded rootfs.gz onto a partition of your choice (ext3 or ext4)
   lzma -d 210615_rootfs64.gz -c | cpio -idv
   add to that partition the /boot folder containing the kernel-64bit of your choice (bzImage).
   always of your kernel add its modules and firmware in /lib/modules and /lib/firmware
   with a grub4dos set the boot in

   title Slitaz
   root (hd0,1) <<< or your partition choice
   kernel /boot/bzImage root=/dev/sdb2 <<< or your partition of choice
   ------------------------------------------------------------------------------------------------------------------------
   scusami ma non parlo inglese, tento con un traduttore scrivendo in italiano.

   Non usare kernel debian o similari che richiedono avvi con initrd. In quel caso avvengono errori con l'init che non è quello predefinito di slitaz.
   Altra cosa scompatta per intero la rootfs.gz scaricata su di una partizione a tua scelta (ext3 o ext4)
   lzma -d 210615_rootfs64.gz -c | cpio -idv
   aggiungi su quella partizione la cartella /boot che contiene il kernel-64bit a tua scelta (bzImage)
   sempre del tuo kernel aggiungi i relativi moduli ed il firmware in /lib/modules e /lib/firmware
   con un grub4dos imposta l'avvio in

   title Slitaz
   root (hd0,1) <<< o la la tua partizione
   scelta
   kernel /boot/bzImage root=/dev/sdb2 <<< o la la tua partizione
   scelta

   Posted 3 years ago #
6. 

   akm
   

   offline

   Member

   So, I unzipped and extracted the rootfs using xarchiver, but packed it again (after putting in the drivers from ovl_modules, which I unpacked too) using find ./*| cpio > rootfs.cpio, after having changed my working directory. I gzipped it then. But now there's a kernel panic, so it's worse than before. By the way: the overlay doesn't work with grub2, I checked the modules directory after having booted using the unchanged rootfs. It was empty. So, could someone pack the modules into the rootfs, so I can try it?

   Posted 3 years ago #
7. 

   Filou
   

   offline

   Moderator

   Sorry for answering late, been busy this weekend...

   Similar to SliTaz 5.0 on the livecd I use a "stack" of images on my own hardware.
   For this, I use grub4dos, which works quite well FOR ME.

   This way, I can add or even modify any rootfs by loading additional "overlays", that complement or replace already existing files.

   On top of a clean and "kernel-less" rootfs I load the kernel-modules. If I change the kernel, all I have to do is change the modules-overlay with it and can stick to the unchanged rootfs. Like this, it's even easy to add components, like printer-drivers, browsers or office applications directly from the boot menu, which are unpacked into ram as desired.

   What I uploaded is a kernel built for my Lenove ideapad Z710 i7-4700MQ, which might (or might not) work on other hardware. What I did NOT build yet (!) is a general-use-kernel 5.x designed for the x86_64 rootfs I provided.
   I recommend to use any 64bit kernel you know that runs on your hardware.

   The kernel panic you experienced could be caused by busybox lzma, that produces a file with a buggy length (this was discussed somewhere in the forum).

   I can post two scripts later at home (I'm at the office now) that work for me to build/modify the rootfs and the ovl-files.

   Posted 3 years ago #
8. 

   akm
   

   offline

   Member

   I think I compressed the rootfs using GNU zip program from GNU, not busybox. Also GRUB 2 doesn't seem able to handle overlays. I checked the modules folder both in /lib and /usr/lib.

   Posted 3 years ago #
9. 

   Filou
   

   offline

   Moderator

   In order to have a "proof of advance" I took the latest slitaz64-rolling and extracted the kernel modules. I then added them to my rootfs in order to have a cleanly bootable image.

   I packed this into an iso that can be burnt to a CD and booted from, at least in BIOS mode. I didn't test UEFI, although I replaced rootfs.gz in the EFI folder, too (not knowing if this works this way).
   This is why the image has a size of ~150MB, because the rootfs is packed into the iso twice.

   You can find the iso under https://people.slitaz.org/~filou/rootfs/

   After booting as usual, neither my ethernet nor my WiFi were working, probably because of missing firmware. This might be different for other users...

   Posted 3 years ago #
10. 

    akm
    

    offline

    Member

    Just tried the ISO, it boots, but startx still doesn't work. I have UEFI. Still, it's really nice! It's just weird that the command line has some text "pasted" at my cursor's place every couple of minutes.

    Posted 3 years ago #
11. 

    akm
    

    offline

    Member

    So, uh, about the script for modification of the rootfs... could you post it?

    Posted 3 years ago #
12. 

    Filou
    

    offline

    Moderator

    Sorry (also for being late, been very busy these days...)

    Since the upload failed again, I put the scripts in
    https://people.slitaz.org/~filou/rootfs/Scripts/

    Sorry for them being in German, I hope it is still understandable.

    The script custom.sh unpacks the rootfs.gz to /tmp/ (or offers to proceed in an earlier version) and chroots to the system. You can then install or change everything and after exiting, the system is repacked in /
    It was derived from tazusb quite some time ago...

    For building an ovl-file I use the writeout.sh script the following way:
    1.) create a directory in which to build the overlay
    2.) in this directory, create all directories and files needed (could be only /etc/network.conf)
    3.) step back to the parent dir and call the script

    Example:
    

    # mkdir network && cd network
    # mkdir -p etc
    # cp <modified network.conf> etc/
    # cd ..
    # ./writeout.sh network

    This will result in /tmp/ovl_network.gz being created.
    If you use a stackable grub (like grub4dos) then you may use
    initrd /rootfs.gz /ovl_network.gz

    and the network.conf from rootfs.gz will be replaced by the modified network.conf during the boot process...

    Posted 3 years ago #
13. 

    devl547
    

    offline

    ~ # cook my_life

    Some more ideas possible with more recent Linux kernels: https://notes.valdikss.org.ru/linux-for-old-pc-from-2007/en/

    I have tested le9 patchset with btrfs+zstd compressed root fs by myself on an pretty weak c2d laptop with 2 gigs of ram and also on a Raspberry PI 3b system. Worked as a charm compared to the stock upstream kernel.

    If only that kind of magic was available 7-8 years earlier >_>

    Posted 3 years ago #
14. 

    jianliulin
    

    offline

    Member

    @filou

    I download your iso from https://people.slitaz.org/~filou/rootfs/Scripts/ , I can not install the package libgdiplus with tazpkg -gi libgdiplus

    Posted 3 years ago #
15. 

    Filou
    

    offline

    Moderator

    @Jianliulin

    Please be advised that the iso as well as the packages are experimental and not complete yet.

    After having built a working 64 bit SliTaz wok, I am about to compile the packages one by one.
    I made a first "sweep" a couple of months ago and built a large amount of libraries etc., some of which are linked to other - older library versions, so another sweep will be necessary for a good amount of them.

    All those packages that depend on packages that are not built yet or which show problems during version update or recipe adjustment are not available yet.
    Since ligbdiplus is not to be found in my SliTaz64 repository, I was not able to build it without errors yet.

    The whole iso is preliminary, e.g. automatic mounting of attached USB devices is not working yet, as gvfs shows problems during compilation.

    Since I am on vacation at the moment, the further cooking will be slowed down, but I will stick to this project...

    Posted 3 years ago #

RSS feed for this topic

Reply »

You must log in to post.