no scripts - its just the different kernel config

SliTaz 5 (?)
(35 posts) (10 voices)-
Posted 11 years ago #
-
Oh right, I'm thinking mdev configuration. Since we don't use it, we don't really need to write in support. I'm pretty sure udevil does a better job at managing this.
Posted 11 years ago # -
@ erjo: I think we should go with tom's (kultex) ideas, I had to add sleep 1 to system.h to get rolling to boot (although it looks like the soundcard stuff has been commented out now). I can mount all my drives (inc. usb) no problem with the new kernel config, and sound and video (nouveau) drivers working fine also. I don't have wifi unfortunately.
If we could use an updated kernel and packages that would be great also.
Having a spacefm-root desktop file and wbar is a nice touch.
Posted 11 years ago # -
== Google Tranlate ===
I have nothing against having kernel and package updated. On the contrary!
Each new version of SliTaz, I spend my time compiling everything to have the latest version of my favorite applications.This is also why I support the idea of backports (http://forum.slitaz.org/topic/survey-for-create-backport-repository-for-stable-release). The most part of utiilisateurs, myself, do not even know what version of glibc they use. They just want to have the latest version of claws-mail, Firefox, Apache or other packages.
What I want to avoid is to destroy everything and start with 1 or 2 years of debugging.
I do not doubt the work Kultex and Tom made. But our buildhost is sometimes capricious with some change== French ==
Je n'ai rien contre le fait d'avoir des paquets et un noyau à jour. Au contraire!
A chaque nouvelle version de SliTaz, je passe mon temps à tout recompiler pour avoir des version plus récentes de mes applications préférées.C'est aussi pour ça que je soutiens l'idée du backports (http://forum.slitaz.org/topic/survey-for-create-backport-repository-for-stable-release).
La pluspart des utiilisateurs, moi le premier, ne savent même pas quelle version de glibc ou de toolchain ils utilisent. Ils veulent avoir la dernière version de claws-mail, Firefox, Apache ou autre packages.Ce que je veux éviter, c'est de tout casser et repartir avec 1 ou 2 ans de deboggage.
Je ne mets pas en doute le travail que Kultex et Tom ont réalisés. Mais notre buildhost est parfois capricieux avec certains changement...Posted 11 years ago # -
tout à fait, et ce que je vois c'est que présentement avec la rolling, mon écran externe
est bloqué à la même résolution que l'écran de mon laptop... donc c'est super d'être toujours
à la pointe, mais le résultat est que je connais maintenant une flopée de gens qui sont passé
à côté de Slitaz parce qu'ils ont du faire face à 2,3 écrans noirs et cette idiotie d'avoir à get-installer
le module ethernet ou wifiFranchement, vous avez le mérite d'avoir construit un des meilleurs linux par la pureté de son code, mais
est ce que c'est bien nécessaire d'avoir des milliers de paquets qui sont utilisés par 10% des gens alors
que ça vous prend peut-être 90% de votre temps pour les compiler ou je ne sais pas trop quoi ?Posted 11 years ago # -
@Paul - you had to add sleep=1 in my testing iso? - in my iso you will find the soundcard stuff and all my other changes in local.sh
@erjo - I underline your statment, that we have to avoid to destroy everything and start with 1 or 2 years of debugging. Thats the reason, why I want to stay on kernel 3.2.xx and never would touch glibc....
Posted 11 years ago # -
Well, we'll stay with 3.2.x for now and once a full release happens, we can backport newer packages while updating the cooking repository. This seems like the simplest way.
@erjo - Can you make a backports repository on hg.slitaz.org ?
Posted 11 years ago # -
@ kultex: I only added sleep 1 to the 'official' rolling (I hacked a LiveCD). Your iso boots fine for me.
Posted 11 years ago # -
ok, it seems now, that we are going for 5.0
before we start to do this, somebody has to take care of cookutils - also Kapil describes here http://forum.slitaz.org/topic/chroot/page/3, that something does not work
I tried to configure evrything new today, but I could not cook, because of missing depency busybox-boot 1.21.1 - I see on http://pkgs.slitaz.org/search.sh?receipt=busybox&version=cooking, that busybox is 1.21.1, in wok its 1.18, but I dont know how to update wok.
I really think the same as Kapil, that it would be good, if somebody makes a working cookutils iso, where it is easy for beginners to learn and help and not to struggle around setting it up - its such a loss of energy and I think also a loss of people
Posted 11 years ago # -
update wok ?
Clone a repo, example for wok
$ hg clone http://repos.slitaz.org/wokTo update your wok with the local server
$ hg pull -uPosted 11 years ago # -
It's been at busybox 1.21.1 for about 5 months. Maybe you altered yours, which means mercurial expects a merge rather than an update.
Posted 11 years ago # -
Hi,
thanks ergo for create wok-backports repository,
I start with firefox last versionFirefox 26.0 (Binary version from mozilla website), work out of box.
NB: Firefox need that plugins should be installed in "/usr/lib/mozilla/plugins"
I would inspirate by receipt include in wok for build this release.
I don't have access on wok-backports.
Ergo, can you give me grant permission ? thanksPosted 11 years ago # -
but it is still necessary to set up cooker and wok on 4.0 and not on rolling?
Posted 11 years ago # -
@Trizar_za: slitaz-backports is created.
@shann: I created a new tread ;for backports: http://forum.slitaz.org/topic/about-slitaz-backports
For grant access contact me on mail.@kultex: Yes cooker and wok are for cooking release.
I try you iso. I would like to build your kernel on wok-undigest before updating the wok.Posted 11 years ago # -
but please wait with the kernel - I want to update to 3.2.53
you help me, when you update those in wok-undigest claws-mail to 3.9.2 - spacefm to 0.9.2 - udevil to 0.4.3 - wbar to 2.3.4 - midori to 0.5.6-1
Posted 11 years ago #
Reply »
You must log in to post.