SliTaz Forum
You are not logged in.
Pages: 1
What do you think about having Slitaz 5RC3 ?
It could be a nice idea, no ?
Offline
Hi erjo,
I agree!
Offline
Update toolchain! xD
Man, our gcc and glibc versions are from paleozoic era.
Offline
@erjo - it is really necessary to make quick a RC3, to get rid of RC2
@devl547 - its true that gcc and glibc are quite old, but I think, it would be no good idea to update them or to another kernel - 3.2.x is supported until 2017-04-26
https://www.kernel.org/
https://lkml.org/lkml/2015/1/1/50
@all - whats necessary to finish 5.0 ???
maybe we can collect the ideas here - just my thoughts:
1) Update kernel to 3.2.66
2) work on "tazhw setup printer" - thats totally out of order
3) Aleksej worked on tazx, so that tazx detects automatic the grafic chip - my question is I think for Pascal - is it possible to get a bootline, that automatic boots to tazx and installs the correct grafic drivers - of course, if there is internet....
maybe we can collect the issues here and finish 5.0 within a month?
Offline
I think it's a really good idea to make a RC3, because RC2 is too old and there are some people that still using it. Also, RC3 could increase visits to Slitaz at DistroWatch.
I don't know how Slitaz team develops it, but I suggest to use the Debian style of: unstable (rolling) -> frozen (tests phase) -> stable (RC3 or 5.0).
This can minimize the occurrence of bugs and errors. But, of course, it's just an idea. 
What's necessary to finish 5.0? To me, the system is very good. Just make a stable version (without bugs) and I'll be happy.
Offline
>3.2.x is supported until 2017-04-26
Sure, but IMHO new desktop features and bugfixes are more crucial than LTS support for servers.
And also on kernel.org:
mainline: 3.19 2015-02-09
stable: 3.18.7 2015-02-11
All other are LTS.
Offline
I also agree with a RC3 version, some bugs was fixed after the RC2 release, so it would be nice to everyone.
Offline
... pls, no "automatic" network connections to repositories or anywhere... every network connection should be explicitly requested by the user... thats critical for who does forensics 
(... personally, at live boot, I would even remove that dhcp request on LAN... its also useless for who doesnt use wired net, and slows down boot time 4+ secs...)
[... personally, at live boot, also wrong is the automatic wireless modules probe, because sometimes the loaded module is wrong... blacklisting on live is inappropriate and further unloading the module often crashes all... ]
{... FYI, at live boot, the kernel messages get scattered all over the screen, on smaller monitors, e.g. on a netbook pc... }
SliTaz is a very good distro. My thank goes to all the developers.
I would appreciate a SliTaz 5.0 RC3 version in March 2015.
Today I have testet the weekly from the 15th. of Febuary. Unfortunately there are still some disappearing mouse pointers in this version. These bugs should be fixed before releasing RC3. For instance the mouse pointer is disappearing when I move the mouse pointer over the close button in alsaplayer and it is disappearing when I move it over the close button in xine-ui. There it shows the help "Hide Gui", but before that the mouse pointer has disappeared.
The isomaster should be updated and I would wish, that it would be integrated in RC3. At least it should not be forgotten in the locale-xx-extra packages.
Offline
... agree, mouse pointer which disappears is very annoying also for me... v4 doesn't have this issue, don't see a reason why we should suffer that torture in v5
Yes please. RC3
Offline
It's a common issue with LXDE based Linuxes. I had a similiar disappearing mouse issue with Ubuntu and Debian. Using a different windows manager apparently fixes the issue because Peppermint didn't have the issue (it uses xfce's windows manager instead of Openbox). Updating the packages to latest versions will probably fix the bug though - so freezing the repository would be a BAD idea right now.
Offline
... so v5r3 will be fully LXDE?
afaiu, v4 is a mix of openbox + xfce... not bad I would say...
so why now shift to fully LXDE? isn't full LXDE more battery consuming on old laptops? fancy to describe the reasons for that change?
I'm saying it's either Openbox or it's interaction with the LXDE components that's causing the issue. It has been fixed in current versions of Lubuntu and LXDE Debian though - it seems like it's an issue from 2013 to mid 2014 and got fixed at some point. So clearly we just need to update the LXDE components (and Openbox) to fix it.
SliTaz 4 uses LXDE's pcmanfm, panel, display and theme manager and choice of windows manager.
Personally, I feel we should be going with a full Qt based version since LXDE and RazorQt merged to form LXQt. It's much lighter on system resources, dependencies and iso size space required than what current LXDE needs. We could then just have the user install GTK with packages that need it (or include it since we'll be saving space from not having to meet pcmanfm's heavy requirements).
Offline
... oh, LXQt, never heard of it! 
thanks, I went to distrowatch and tried one of the only 2 distro with it... well, boot normal speed, desktop in idle 1% cpu, shutdown 2 seconds (!)... played with openbox and lxqt settings, didnt see much difference, fast as our v4 env, no disappearing mouse indeed, but again pcmanfm errors, couldnt mount my hd partitions...
anyway, looks promising... so agree, just drop out a r3 in lxde+openbox as planned to close that neverending loop... and after we could give a shot to LXQt ...
... coming back to our bugs, my summary:
> wrong wireless modules are modprobe at live boot (eg. brcmsmac, that module needs firmware files which are not shipped with the distro,a better module would be wl, but unfortunately once brcmsmac is loaded, can't be unloaded, making the wifi card unusable in live mode.. all firmware based modules are affected, and not only)
>> solution: no automatic modprobe at live, only by user request (eg. by wifi-configuration)
>>> severity: critical+blocking
> cursor disappears *every* time the right-mouse button is pressed, or click on not-grouped not-iconed apps in task manager, and stays hidden till out of menu or other major action.
>> solution: update to latest lxde+openbox (?)
>>> severity: critical
> all tools run from menu, and opening in terminal (eg. alsamixer, nanoeditor, vieditor,..) they open in blank window - they get visible only if press keys inside or maximize.
>> solution: unknown.
>>> severity: major
> the dhcp request on LAN at live boot is useless for users without LAN and slows down boot time 4+ secs
>> solution: remove dhcp request on live boot, only by user request (eg. by Network manager)
>>> severity: trivial
> at live boot, the kernel messages get scattered all over the screen, on smaller monitors, e.g. on a netbook pc.
>> solution: unknown
>>> severity: trivial
SliTaz now just has 42 MB and does not claim, that evrything is working out of the box - I would say, its just the lowest common denominator to get the iso working on most hardware. If I am aware of my linux hardware, evrything works out of the box - if I am not aware, you have to tweak.
Main tweek of the live CD are the bootoptions - http://doc.slitaz.org/en:handbook:livecd
> wrong wireless modules - try to load wl with bootoptions or remove brcmsmac from the modules, add wl to LOAD_MODULES in /etc/rcS.conf or add the brcmsmac firmware to /lib/firmware and make a new iso.
> all tools run from menu - for me eg. "sakura -e alsamixer" works without any problem
> the dhcp request on LAN at live boot - remove network.sh from run scripts in /etc/rcS.conf
> at live boot, the kernel messages get scattered - bootoption: vga=XXX
Offline
... I agree on what you say @kultex, but that
> wrong wireless modules - try to load wl with bootoptions or remove brcmsmac from the modules, add wl to LOAD_MODULES in /etc/rcS.conf or add the brcmsmac firmware to /lib/firmware and make a new iso.
>> sure, lets put it that way, I have a problem, I am enough skilled, I solve it myself, no prob with that, already did that in v4... but its not only *my* problem, here the issue is slightly different, in v4 I just *added* a matrioska with brcmsmac+firmware files, because at the time of v4 it did not exist brcmsmac, so it was not loaded, was easy, no need to mess up the main matrioskas... I just added, was lucky now in v5, you say, you have a brcmsmac (or any other problematic wifi driver) issue, you solve it yourself, no matter if it is a common problem, *objective*, not subjective... and no matter if you know it already but still put me in charge to fix it that is the slight line which keeps users like me on slitaz, instead of core: because if I need to fix something, I just *add* a matrioska with what I need, the rest is already taken care by you Devs... thats it- easy life, thanks!
In any case, you understand yourself, I'm probably just the first who reported this issue, but be sure, others will come back to you telling they can *not* use the wifi because the driver (not talking about firmware) is wrong, and they dont want it to be set auto at live boot... that is also a bad reclame, users will say slitaz has a wrong wireless support... we are already almost out top-100 list in distrowatch... instead, what about fix that now, so you will have 1 problem less?
Now, I'm not suggesting to remove the wifi support, or add firmware files, not at all !! because for example, you can go lucky and have only a rtl or ath or any other wifi which doesn't need firmware+plus driver is unique=smile... but, for others, what's the point to load a driver which, first of all doesn't work without firmware, second is not unique and some others could prefer (for many reasons) b43 instead of wl, third you can't unload it ... just making an example
> all tools run from menu - for me eg. "sakura -e alsamixer" works without any problem
>> yes, they work ok, I just said, when you open them, they are somehow "invisible", not rendered, the window content is blank... press a key inside or maximize the terminal solves the issue.
> the dhcp request on LAN at live boot - remove network.sh from run scripts in /etc/rcS.conf
>> same as before, also here I can't *add* nothing, need remove+repack... before I do that, personally, I would rather not touch it, and stay with v4
> at live boot, the kernel messages get scattered - bootoption: vga=XXX
>> tried already all vga options available, the letters get smaller, shrink, and so on, but the scatter effect remains. Its visible mostly after the [OK], next line just goes <lf> under without <cr>
> the dhcp request on LAN at live boot - remove network.sh from run scripts in /etc/rcS.conf
Dhcp client can be daemonized, so no wait is needed.
Also, we can do wired and wireless init in parallel.
Offline
How can I help test specific fixes?
And test in general to help with RC3 ?
Offline
@nikitan -
first what is main difference between *add* and remove bevor you repack - in both ways you have to do something - and if you do not like the slitaz way of networking, you have to choose another - if you want to use wicd instead of SliTaz networking you replace network.sh with wicd in RUN_DAEMONS and thats it.
and "before I do that, personally, I would rather not touch it, and stay with v4" - thats only a question of your specivic hardware... - like my Portege R100 works out of the box first time with 5.0 - before I had all the time a black screen booting the live CD - and my AMD-Geode LX 800 audioservers worked with 3.0, crashed with 4.0 (no chance to get them working) and working now with 5.0 perfect again.
So - if you want a distro, that runs on 90% of the hardware you need at least 200 MB and thats not the aim of SliTaz - there are enough distros on the market
Offline
I agree with Kultex and I believe he was the first person to say that SliTaz isn't easy.
There's a reason for that: SliTaz tries very hard to be simple, generic and small. It does all of that very well, but comes at the cost that you sometimes need to hand configure things or fix issues related your system. I personally think this is a small price to pay and teaches you how to solve the problem - a skill you can use with other distros when a similiar problem crops up.
Now if you want a version of SliTaz that meets your needs and systems, then feel free to make one with the tools provided by SliTaz. Just don't be surprised if it's a memory gobbling monster 
Offline
no-no-no @Kultex dont try to picture me as the usual "monster" which asks a slitaz with only what I need for free, no-no-no
I suggested only 1 solution: remove the auto probe for wifi modules at boot time in the live version.
A solution for the not *subjective* issues you have read, and totally in line with what @trixar said: "simple, generic and small".
End.
As for the other rendering issues, I hope they will be solved upgrading lxde+openbox.
If not, I like that LXQt ...
For the rest, sure nopr, there is always time for a little matrioska.
I would like to say thanks for updating isomaster and the locale-xy-extra files. SliTaz is something I don't want to miss. I am wishing the project to attain a great success.
Offline
Pages: 1
[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]