You know, I just figured out something. I can make a traditional version and a lighter one which I can call SliTaz lite.
Buildroot SliTaz
(20 posts) (7 voices)- Started 11 years ago by Trixar_za
- Latest reply from Trixar_za
- This topic is not a support question
-
Trixar_za
offlineKey MasterPosted 11 years ago # -
kultex
offlineKey Master@devl547
installation works fine, if you use tazinstall and choose the iso installation
and I am using rolling (frugal) on my 12" Portege R100 for dayli work and I really love it - the lxpanel settings was strange at the beginning, but in combination with wbar its really cool on the small monitor. And the kernel is not outdated - and I will give you tomorrow a testing iso with kernel 3.2.50, which came out 02.08.2013, sowhere it is outdated.....
@Trixar_za
and I think we also could start to make Razor-qt version of slitaz with current rolling......
Posted 11 years ago # -
sixofeight
offlineMemberJust a User's view..
I like the idea to keep it simple and not ignoring older Hardware.
I'm using Sz4.0 on my 12 years old box (1ghz cpu/1Gb ram) and I don't miss
anything.
Maybe we should have a Slitaz-"legacy" for older Hardware which do not
need to have all the stuff needed for new Pc's.(lastest Kernel,PAE etc.)
imho a slightly updated Sz4 would fit the needs of mostly all of the old-Hw-users
On the other Hand the "regular"-Sz-version would not have to struggle with compatibility anymore.
and oldfashioned as I am...If a (additional) program-version-xx fits my needs, then there is no need for a bloated version xxxPosted 11 years ago # -
Trixar_za
offlineKey MasterI was wrong and I'll tell you why in a minute. I've been struggling to make a 'good' Buildroot SliTaz because Buildroot gives you A LOT of options to play with, which means there is a lot of trial and error involved. But Buildroot has a single flaw: You can't generate packages from it. This means anything I include will most likely not be the same as the one in the package repository. This also means the one in the package repository will break the Buildroot system if it's ever installed. It's also an overwhelming amount of work to decide what goes into a Linux system and what will be needed and what won't be.
That is why my goal of rebuilding SliTaz in Buildroot will never work.
My original goal was to redo the kernel, udev and xorg so it was an usable base to install SliTaz packages on to fill in the other requirements. That's should work and only add a few packages to the block list of tazpkg.
So my new goal is to build the kernel, udev, xorg and busybox with Buildroot, then install the slitaz-tools and add the packages we already have in SliTaz to it. Once that's done, I'll generate the iso with our own tools with maybe a few tweaks here and there to fix compatibility. Once I'm back, I'll start updating the packages so we can have a more stable SliTaz to release. I will also match the versions we already have in the repository so we can have better compatibility.
Posted 11 years ago # -
Trixar_za
offlineKey MasterI'm reviving this with buildroot on my own system. I'll also revive my previous project to create a way to convert buildroot packages into slitaz one.
I would like to thank the group of people that have started to openly ignore me here in an effort to make me feel unwelcome. Making me angry just motivates me more - so keep it up.
Posted 9 years ago #
Reply
You must log in to post.
