As you maybe noticed, the modules page is up but is rather empty yet. There are more than 300 modules waiting in the queue to be checked. It takes me so long because I'm developing a system for checking in parallel.
Every user has a link in his profile page, which will lead you to all the modules from that user. This way, you can access all your modules easily even if you can't see them in the repository. I'd like to kindly ask everybody who uploaded modules to go through them and fix all missing icons, screenshots and descriptions.
Do not upload your modules again (as a new), but rather click the 'edit module' link in the module detail page in order to update it to a newer version (or to just fix the descriptions and icons). The quality of uploaded modules is rather bad (as far as I checked), so please help me make it better.
Also, make sure to re-read the documentation page 'how to create modules the right way'.
I tried to add the icons to my modules, but after adding the first icon using "edit this module", the icon shows up ok, but when I do the same for all the rest of the modules, the icons don't show up, I still get that brown "?" icon.
Tomas M wrote:
As you maybe noticed, the modules page is up but is rather empty yet. There are more than 300 modules waiting in the queue to be checked. It takes me so long because I'm developing a system for checking in parallel.
Every user has a link in his profile page, which will lead you to all the modules from that user. This way, you can access all your modules easily even if you can't see them in the repository. I'd like to kindly ask everybody who uploaded modules to go through them and fix all missing icons, screenshots and descriptions.
Do not upload your modules again (as a new), but rather click the 'edit module' link in the module detail page in order to update it to a newer version (or to just fix the descriptions and icons). The quality of uploaded modules is rather bad (as far as I checked), so please help me make it better.
Also, make sure to re-read the documentation page 'how to create modules the right way'.
Thank you very much.
Remember to check the text on the moduledesc, before you try. I have written "to be deleted" on nearly 30-40 modules, so it can save you a great amount of time.
markds wrote:
I tried to add the icons to my modules, but after adding the first icon using "edit this module", the icon shows up ok, but when I do the same for all the rest of the modules, the icons don't show up, I still get that brown "?" icon.
F5 in your navigator.Update www browser view.Cache navigator see you previous icon.Refresh www browser.
I was been using Gimp ans .png format. The images where less than 800x600 (this is because it's the table measure!).
My problem was the browser cache!!
Bye
Pastrugno wrote:
I was been using Gimp ans .png format. The images where less than 800x600 (this is because it's the table measure!).
My problem was the browser cache!!
Bye
Lol. WMP icon on lib files. In general:
How to put icons on libmodules ?
Those should be an iconfree zone
Nevermind. I'll put my avantar on mine
(hope i do not end up in a copyright case..)
I made icons for all my modules, all same format, same resolution, colour depth, etc. Which ever one I upload 1st works. After that the rest will fail. If I try to use the on that was working again it will fail too. So the problem is not the icons or the browswer, and yes I did clear the cache and refresh and reload, still didn't work. I even tried on another computer to view and its the same.
gusterrapolis wrote: markds wrote:
I tried to add the icons to my modules, but after adding the first icon using "edit this module", the icon shows up ok, but when I do the same for all the rest of the modules, the icons don't show up, I still get that brown "?" icon.
F5 in your navigator.Update www browser view.Cache navigator see you previous icon.Refresh www browser.
Tomas I suggest you blacklist the whole geckoengine from your script. In fact everything inside the /usr/lib/$MOZILLA_TYPE_BROWSER folder. They are found in every mozilla-client anyway...And they just pops up a lot on the dep.list.
1. Check against itself (as now apparently only partly does)
2. If it contains general libs, then they could be added to the librarydatabase, given a) it is not tremendous big module (which is a typically all-in-one style) b) the libs all reside in the official slacklibfolder,"/usr/lib", or the official "MOZILLA_HOME" and c) Totally skip it if it has anything with "All" in its name..
So point 3 which is why I write this in the first place
3. It should check against itself, EVEN in the "/opt" folder. BUT those libs should Not be added to the database. Still, they should be valid for the moduleitself. In otherwords, check all binaries and see if the module itself contains the libs needed. No matter where they are placed. And if the module has them, then do Not search the database for other links. BUT, since they do not reside in the "/usr" folder (the libs of the module, that is), they should neither be added to your "official" linking database.
The clue is, I have modules that contains everything, but with libs compiled into "opt" to avoid overlinking from other modules to these, and to keep them runnable even if Slax upgrades. It is somehow funny to see that line when checking the module's dependencylist: 'libXYZ.so was not found in any modules'. And then one knows that the libs are within the module, but just not in the "/usr" folder.
Hope you understood what I meant.
I'll clarify issue 3 with an example, coz it is quite important, to me at least
Module 435 have listed all packages included in it. Among them you find "nautilus-cd-burner".
I view the details of the dep.list, and this is just one of several "not found":
"requires libnautilus-burn.so.4 not found"
And where may that libnautilus-burn.so.4 be, hmmm..Exactly, inside the module, within the package nautilus-cd-burner.
In worse occasions it links existing libraries as "not found" and link them to modules I have wished and wrote "2 b deleted" by you :)
Thor wrote:
It is somehow funny to see that line when checking the module's dependencylist: 'libXYZ.so was not found in any modules'. And then one knows that the libs are within the module, but just not in the "/usr" folder.
It seems to me you don't understand the meaning of 'library path' input field in the form (the form used to submit a module to slax.org). If your module needs libraries, which are included in the module itself (whatever subdirectory it uses), simply specify that directory in the library path field...
I'll clarify issue 3 with an example, coz it is quite important, to me at least.
Module 435 have listed all packages included in it. Among them you find "nautilus-cd-burner".
I view the details of the dep.list, and this is just one of several "not found":
"requires libnautilus-burn.so.4 not found"
That is because libnautilus-burn.so.4 is not found in /usr/lib;/lib/...
You can fix that by the library path, as mentioned above.
Slax searches for the libraries in /lib, /usr/lib, and some other trusted directories. If you know the libraries are in the module but in a non-standard directory, you have to type that directory in the library path input field. If you need to specify more than one, simply divide them by semicolon (like in PATH);
What is the exact syntax ? Just the path, and do I need to reupload it to verify it again, or is it enough to just enter the ld path into the form.
Gee, man ... Embarrasing after all these uploads that I never seen that textbox. But still a great way to solve the issue, youve come up with
For example, if your module requires libmozjs.so, which is in /usr/lib/firefox-2.0.13/, then type
/usr/lib/firefox-2.0.13/ to the input field.
If your module needs many libraries, which are all in /opt/application/lib1/ and /opt/application/lib2/ directories, then enter the library path as following: /opt/application/lib1/;/opt/application/lib2/
I have to give it to you. I just Love this solution :D
Just a little cry right now... I have a module that has same prefix as 2 other one of mine. But since the prefix is outside the normal /usr, it is (maybe just to short time since editing it) linked up to another module with a printlib inside /usr. While my main has it inside "/opt/gnome-2.21.3".
Is it possible to add some way to recognize 2 modules use the same ld_path and to bundle/connect those two, of course under the assumption that they must be a better fit since the paths are the same.
The thing right now, is that under the more elaborated dep.list, the other and mine are both listed. Still the other, with a different prefix, is listed first. Could it be reasonable inside a fair amount of effort, to add some functions into your script, that sets priority to same library-path between two modules.
Second thoughts... That could be my mistake..I think I build that module with "/usr" instead of "/opt.." as prefix. I will rebuild it and see if it changes the linkingrecommendations.
Thor wrote:
Just a little cry right now... I have a module that has same prefix as 2 other one of mine. But since the prefix is outside the normal /usr, it is (maybe just to short time since editing it) linked up to another module with a printlib inside /usr. While my main has it inside "/opt/gnome-2.21.3".
Is it possible to add some way to recognize 2 modules use the same ld_path and to bundle/connect those two, of course under the assumption that they must be a better fit since the paths are the same.
The thing right now, is that under the more elaborated dep.list, the other and mine are both listed. Still the other, with a different prefix, is listed first. Could it be reasonable inside a fair amount of effort, to add some functions into your script, that sets priority to same library-path between two modules.
Please provide examples, I don't understand you
sadrunk wrote:
ok if i post a module and i discover trought the dependencies that there is a module newer then mine to be aproved, how do i delete mine?
Currently I am the only one who can delete modules. The best is to edit description of your module - simply state there that I should delete it.
Tomas M wrote: Thor wrote:
Just a little cry right now... I have a module that has same prefix as 2 other one of mine. But since the prefix is outside the normal /usr, it is (maybe just to short time since editing it) linked up to another module with a printlib inside /usr. While my main has it inside "/opt/gnome-2.21.3".
Is it possible to add some way to recognize 2 modules use the same ld_path and to bundle/connect those two, of course under the assumption that they must be a better fit since the paths are the same.
The thing right now, is that under the more elaborated dep.list, the other and mine are both listed. Still the other, with a different prefix, is listed first. Could it be reasonable inside a fair amount of effort, to add some functions into your script, that sets priority to same library-path between two modules.
Please provide examples, I don't understand you
Yes..I know it a little better know.
LD_PATH=LD_LIB_PATH ...Just dislike to type capitalized library
What I discovered is that your script put first priority to SIZE_OF_MODULE_RELATED and secondly to LD_PATH_MODULE_RELATED.
Since LD_PATH is mostly /usr/lib I think it is the right way, in general, to order it. BUT, for those modules with a different LD_PATH, is it possible to add into your script some way to first prioritize LD_PATH_MODULE_RELATED before SIZE_OF_MODULE_RELATED
Example.
Abiword needs "libgnomecanvas"
libgnomecanvas found in 2 modules a)Abiword_All b)gnome-platform
Now:
Abiword_all is the smallest of size, so I link to Abiword_all before gnome-platform
What I wish:
libgnomecanvas found in 2 modules a)Abiword_All b)gnome-platform
"lets first check LD_PATH"
LD_PATH Abiword All = /usr/lib
LD_PATH gnome-platform =/opt/gnome-2.21.3/lib
Aha..
LD_PATH_GNOME_PLATFORM=LD_PATH_THE_MODULE_I_AM_CHECKING
ergo: They are probably related to eachother
I will link to gnome-platform first and abiword_all second, despite the fact that abiword_all is smaller
:)
I guess you see it, but Ill mention it. If both have same LD_PATH, say "/opt/gnome", then the prioritizing will just be as it is now. Size will determine which comes first in the linked-module-suggestion
Thor wrote:
What I discovered is that your script put first priority to SIZE_OF_MODULE_RELATED and secondly to LD_PATH_MODULE_RELATED.
Since LD_PATH is mostly /usr/lib I think it is the right way, in general, to order it. BUT, for those modules with a different LD_PATH, is it possible to add into your script some way to first prioritize LD_PATH_MODULE_RELATED before SIZE_OF_MODULE_RELATED
Well, it doesn't work like that.
The library path (input field in 'edit/new module') is used only FOR THE CURRENT MODULE, that means, you will force the software to search for dependencies WITHIN YOUR MODULE in a new (specified) path as well, but other modules or dependencies won't be affected in any way.
LD_PATH_GNOME_PLATFORM=LD_PATH_THE_MODULE_I_AM_CHECKING
ergo: They are probably related to eachother
I will link to gnome-platform first and abiword_all second, despite the fact that abiword_all is smaller
Now I can understand what you mean.
It is a good idea to prefer a module with the same library path, but it may be very hard to implement in my dependency-checking scripts. I will think about it, but I guess it will unlikely happen.
LD_PATH_GNOME_PLATFORM=LD_PATH_THE_MODULE_I_AM_CHECKING
ergo: They are probably related to eachother
I will link to gnome-platform first and abiword_all second, despite the fact that abiword_all is smaller
Now I can understand what you mean.
It is a good idea to prefer a module with the same library path, but it may be very hard to implement in my dependency-checking scripts. I will think about it, but I guess it will unlikely happen.
Oki. Hope you can get it incorporated.
An example of a workaround, that works but aint so pretty
The Abiword_all, contains libgnomecanvas and libgnomeprintui in /usr/lib. It got linked to each and every gnome-module I uploaded. Despite different LD_PATH
Another shot:
Could it be easier to give priority to modules from same author ?
Like:
" lgnomecanvas
Found in Abiword_All and gnome-platform. Abiword_All is the smallest. Still I'll link gnome-platform, because the latter has the same author as the module I am checking here"
Another smart guy has started splitting up the gnome-platform. Would be the same as to split up xfce into all those small lixfceXXX. No point in having just orbit installed. You need more or less everything from orbit to libgnomeui, aka gnome-platform. In contrast to xfce, elements from the Gnome platform, CAN be used by many apps, although not needed or important.
So gnome-desktop gets linked to the wrong orbit. Not the one done by me. Ergo, people download and it won't work. This is frustrating considered all the time it takes to get the gnome-desktop to work. If it goes on, I'll either just compile with prefix=/usr into small part, or I'll upload one big module with it all, down to from glib/cairo to totem mediaplayer, or just stop uploading. Just ain't working right now like it was intended. Despite being a good script, you should add some features to it.
Look at the uploaders name. The fellow seems like a copycat:D
Tomas think this one is touched before, but I'll repeat it since I like the idea.
An additional schema when a module is uploaded. Say:
Question
How did this module come alive ?
Reply
a) Downloaded from official Slackrep
b) Downloaded from unofficial Slackrep
c) Compiled myself
if c) On What Slaxversion
d) Downloaded from deb rep and converted
e) Downloaded from rpm and converted
I def avoid all from d) and e). It would be nice to know
The worst suggestion, but better than it is now, if the others are to hard to implement
What happened to that "number of hits/download" stat on the modulepage. That was a fun feature, but also useful. Modules with many hits, bothered me more to maintain, keep updated and check for errors, than those with lesser hits. Is it coming back ?
problem is, I was unable to connect to the internet using slax. In other words no slapt-get. And it isn't part of official KDE (that I know of). I don't use KDE on another other computers, so I will check on that to make sure.
BTW, I fixed the deps for it, accidentally uploaded the wrong LZM for KnetworkManager
This is my first time using Linux. I read somewhere, I could set it using "sndconfig" in /sbin. But SLAX liveCD did not have sndconfig. Any idea how to configure this soundcard into SLAX?
What I mean is I uploaded the wrong package for knetworkmanager itself. The deps weren't already uploaded. They are actually for NetworkManager, which knetworkmanager depends on. I am still working on a non-dependent package for NetworkManager. I just finished a complete package for Battle for Wesnoth (great game, btw).
iswanto wrote:
why he`s the only person to check those whole modules...??? Is there no body else to help or another reason...???? I wonder.....
I hired David few days ago, who verifies the modules. So I am not alone anymore :) The problem is with the quality of modules, only 2% of all uploads are accepted, the rest is rejected for not following the rules.
Tomas M wrote: iswanto wrote:
why he`s the only person to check those whole modules...??? Is there no body else to help or another reason...???? I wonder.....
I hired David few days ago, who verifies the modules. So I am not alone anymore :) The problem is with the quality of modules, only 2% of all uploads are accepted, the rest is rejected for not following the rules.
What are those rules ? I mean I know the official rules, but how hard are you on them
If I prefer to mtune for my k8, will it be rejected ?
If only 2% of the uploads are acceptable, then it is possible that the situation deteriorates to such an extent that users won't want to use the official modules and would opt to instead go for unofficial modules. In fact, thats exactly what is happening now, mainly because the modules page is still not 100% up.
From the looks of the success rate of submitted modules, it might be a very long while before the module's page is at the capacity of what the previous slax module's page was. While I will not dispute Tomas' rational or reasoning behind the enforcement of rules for modules, I would be inclined to voice out that the rules might need to be looked at again.
wodan wrote: Tomas M wrote:...only 2% of all uploads are accepted, the rest is rejected for not following the rules.
... maybe you should think about those rules - your users might not understand them ..."Users" might not understand them, but advanced users / developers surely do.
I would rather see a few good and reliable modules than having the caotic state in which slax5 was in (hundreds of useless / problem causing modules).
One thing that would fill up the modules page real quick is the make all official slackware packages available as modules (Tomas once said he would), so you would get hundreds of quality / reliable modules.
The rules are there for two reasons:
- to make the modules usable for everyone
- to make the repository look nice (fit webpage style)
The only problem is that people are not used to them yet. They ask questions like: why should I bother about putting an item to the menu? Why should I bother about missing dependencies, when the module works?
Users have to understand the rules. If they do not understand, they can always ask for explanation. But they should NOT build modules against the rules, else we are back in the slax5 times where the repository was full of modules (2000+) while only few percent were usable at all.
A developer should pickup his users where they actually are and not where he expects them to be
That is my point for Slax (I will pick up the users where they actually are), but it does not apply for official modules (I will publish only modules from those users who can make them, not the rest who simply download a TGZ package from web and convert it to LZM without bothering about anything.)
Thor wrote:
What are those rules ? I mean I know the official rules, but how hard are you on them
You must follow them else your modules won't be accepted to the official repository.
If I prefer to mtune for my k8, will it be rejected ?
I don't understand this question at all, I am sorry.
Tomas M wrote: Thor wrote:
What are those rules ? I mean I know the official rules, but how hard are you on them
You must follow them else your modules won't be accepted to the official repository.
If I prefer to mtune for my k8, will it be rejected ?
I don't understand this question at all, I am sorry.
1) David emailed me to say that there should be a menu item for some of my command line modules (eg wpa_supplicant). The menu item would just run the command in terminal without any arguments so as to display the help message. I understand this concept, because I use it for my bioslax distro as well, but we do it mainly for "cosmetics" and "marketability", to show people that this application is available on our distro even though its on command line. My question is, is this really necessary for SLAX? I've already repackaged the module with the K menu item, but I just wanted to ask this question first.
2) Some modules which implement new drivers are more or less meant to be included from the modules/ directory on boot up. Drivers are read when the system boots up. I was asked to put a 'depmod -a' command in a start up script for one module that implements new drivers. Again I understand the rational for it, but wouldn't it be simpler if a note was put on the module description page to tell users if they are running the module dynamically they should run 'depmod -a' before activating the driver? Even if I put 'depmod -a' into a start up script of the module, and the user activates the module on the fly, wouldn't he still have to run the startup script to do the 'depmod -a'? Does this apply to all drivers? Again I've already modified my module accordingly, but I just find it strange to need to do this.
markds wrote:
1) David emailed me to say that there should be a menu item for some of my command line modules (eg wpa_supplicant). The menu item would just run the command in terminal without any arguments so as to display the help message. [...] My question is, is this really necessary for SLAX? I've already repackaged the module with the K menu item, but I just wanted to ask this question first.
I was talking with David about this issue, and I told him to not request menu items for applications where only help would be printed. For example, menu entry is not needed for nmap, because it is useless to run it without commandline parameters. David will no more request menu items for utilities like that.
2) Some modules which implement new drivers are more or less meant to be included from the modules/ directory on boot up. Drivers are read when the system boots up. I was asked to put a 'depmod -a' command in a start up script for one module that implements new drivers. Again I understand the rational for it, but wouldn't it be simpler if a note was put on the module description page to tell users if they are running the module dynamically they should run 'depmod -a' before activating the driver? Even if I put 'depmod -a' into a start up script of the module, and the user activates the module on the fly, wouldn't he still have to run the startup script to do the 'depmod -a'?
No. User runs 'activate', and that should do EVERYTHING neede. The 'activate' also starts all scripts from /etc/rc.d/* and /etc/rc.d/init.d/* (all regular files, it ignores symlinks which are used only during Slax boot), so the startup script will be called and depmod executed.
Does this apply to all drivers?
That applies to everything. User only cares to 'activate' the module (or put it to /modules/ directory), everything else can be done automatically.
One of the requirements is to have a build script part of the .lzm module. At first glance it looks like just another pain causing extra work for the packager. Now I agree with Tomas on this. Build script is useful for SLAX team to learn how the package is created and from which source.
But what is also important, it is useful for one created the package as a documentation. After few weeks it is hard to remember all steps used to create a package and hard to reproduce the result if new source is out or something has to be modified. Having a build script no extra documentation is needed. We all hate paper work, I guess.
Just as an illustration see below my elinks.slaxbuild file used to create elinks module.
#!/bin/bash
#
################################################
# ELinks text browser lzm package for SLAX 6
#
# Packed by Bela Markus, mbl@freemail.hu
#
# Package home http://elinks.or.cz
#
# April 25, 2008
################################################
#
SRCNAM=elinks-current-stable.tar.gz
WRKDIR=elinks-0.11-20080424
MODNAM=elinks-0.11
TMPDIR=/tmp/elinks
#
##########################################
#
# Compile package on SLAX6 system
#
rm -r -f $TMPDIR
#
tar -xf $SRCNAM
cd $WRKDIR
configure-for-slax
make
make install DESTDIR=$TMPDIR
#
# Add SLAX specific files to the package
#
mkdir -p $TMPDIR/usr/src/slaxbuilds
cd ..
cp $0 $TMPDIR/usr/src/slaxbuilds
#
mkdir -p $TMPDIR/usr/share/applications
mkdir -p $TMPDIR/usr/share/pixmaps
cp *.desktop $TMPDIR/usr/share/applications
cp *.png $TMPDIR/usr/share/pixmaps
#
# Adjust directory access rigths
#
find $TMPDIR/ -type d | xargs chmod -v 755;
#
# Strip executables
#
find $TMPDIR | xargs file | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded
#
# Create lzm module
#
dir2lzm $TMPDIR $MODNAM.lzm
#
# Cleanup
#
rm -r -f $WRKDIR
rm -r -f $TMPDIR
Tomas M wrote:
I was talking with David about this issue, and I told him to not request menu items for applications where only help would be printed. For example, menu entry is not needed for nmap, because it is useless to run it without commandline parameters. David will no more request menu items for utilities like that.
Ok So I won't need to reupload the wpa_supplicant module. Thanks.
No. User runs 'activate', and that should do EVERYTHING neede. The 'activate' also starts all scripts from /etc/rc.d/* and /etc/rc.d/init.d/* (all regular files, it ignores symlinks which are used only during Slax boot), so the startup script will be called and depmod executed.
Ok, I wasn't aware activate ran the /etc/rc.d/* files as well - I don't recall it doing so for some of my previous modules. I will reupload my module with the depmod startup.
Speaking of modules, I have SLAX 6 running on a laptop (and it is AWESOME!) The only non-awesome thing is the module manager itself.. it seems to be broken. I can install things using the 'extract and manually place method' so the LZMs seems okay. The manager simply throws an error.
(Maybe this has been reported before?)
Great job on the new site and support of the distro! Very exciting stuff! I am looking forward to the growth of module availability.
dorf wrote:
Still waiting verified firewall, seems that security is not important in linux system.
if somebody know why, let me know...
I think you have misunderstood the securityconcept. Do a portscan of your default Slax, and tell me how many open ports you did find. Try the same on default Windows XP
Be as arrogant you wish to me, and I cannot throw stones while sitting in a glashouse. But please, get the basics a little first.
Security is only important, when the system you are on is insecure. With only 1 known virus todate (for BIND no less - how many of you on a personal system even use BIND?) and an almost closed off system for personal workstation installations, it is no wonder security is not deemed important in the linux system - because its a non issue.
People who claim a certain OS "is more secure" because it has 100s of virus scanners developed for it, an almost equal numer of antispyware tools and a (very basic, primitive, to somewhat non effectual) firewall, really have no clue as to what "security" is all about. If a system was really secure, would you even need any of those things?
Before applying a medicine the disase has to be identified. Against what attack the system has to be protected? On a stock SLAX 6.0.6 system only one port is open according to nmap:
- Starting Nmap 4.60 ( http://nmap.org ) at 2008-04-27 15:45 GMT
- Interesting ports on localhost (127.0.0.1):
- Not shown: 1714 closed ports
- PORT STATE SERVICE
- 631/tcp open ipp
-
- Nmap done: 1 IP address (1 host up) scanned in 0.151 seconds
BTW, in s home or SOHO environment a LINUX firewall is tipically used to share internet connection, root incoming traffic for games and P2P, etc. not only as a poor firewall.
No. User runs 'activate', and that should do EVERYTHING neede. The 'activate' also starts all scripts from /etc/rc.d/* and /etc/rc.d/init.d/* (all regular files, it ignores symlinks which are used only during Slax boot), so the startup script will be called and depmod executed.
I have two scripts dealing with winmodems, one for martian driver and the other for smartlink driver. For the smartlink driver I used to have one script to start everything, but when I used
/etc/rc.d/rc.slmodemd stop|start|restart
The script would return something like *exists **. Everytime, I tried creating another script to call on the parameters and divided the work to two rc.*** scripts one to take care of the intiation and the other to take care of restarting|starting|stopping of the driver. I would like to know if it is good practice to do that or, would it be better to fix the rc.slmodemd startup script?
If it is the case of the latter, I would put a piece of the code that should run before the module is initiated,
This part
/usr/bin/mkdir -p /dev;
/usr/bin/mknod -m 600 /dev/slamr0 c 242 0 ;
/usr/bin/mknod -m 600 /dev/slamr1 c 242 1 ;
/usr/bin/mknod -m 600 /dev/slamr2 c 242 2 ;
/usr/bin/mknod -m 600 /dev/slamr3 c 242 3 ; echo -n
/usr/bin/mknod -m 600 /dev/slusb0 c 243 0 ;
/usr/bin/mknod -m 600 /dev/slusb1 c 243 1 ;
/usr/bin/mknod -m 600 /dev/slusb2 c 243 2 ;
/usr/bin/mknod -m 600 /dev/slusb3 c 243 3 ; echo -n
/sbin/modprobe ungrab-winmodem
/sbin/modprobe slamr
needs to be executed before starting the module, for the moment I put into another script rc.slamr which executed before rc.slmodemd, but if it needs to be changed, I would like to ask help from the users that are more knowledgeable and of course Tomas.
#!/bin/sh
#
# rc.slmodemd
#
# Start slmodemd daemon for SmartLink
#
# SLMODEMD_DEVICE=/dev/slamr0 was set to /dev/slusb0
# modified by Antonio A. Olivares
# olivares14031@yahoo.com
# run depmod -a to ensure modules become available
/sbin/depmod -a
sleep 2
slmodemd_start()
{
if ! [ '/usr/bin/ls /dev/slamr0 | grep slamr0'="$C" ];
then
/usr/bin/mkdir -p /dev;
/usr/bin/mknod -m 600 /dev/slamr0 c 242 0 ;
/usr/bin/mknod -m 600 /dev/slamr1 c 242 1 ;
/usr/bin/mknod -m 600 /dev/slamr2 c 242 2 ;
/usr/bin/mknod -m 600 /dev/slamr3 c 242 3 ; echo -n
/usr/bin/mknod -m 600 /dev/slusb0 c 243 0 ;
/usr/bin/mknod -m 600 /dev/slusb1 c 243 1 ;
/usr/bin/mknod -m 600 /dev/slusb2 c 243 2 ;
/usr/bin/mknod -m 600 /dev/slusb3 c 243 3 ; echo -n
fi
if ! [ 'lsmod | grep ungrab_winmodem'="$A" ]; then
echo "\n\rRunning modprobe ungrab-winmodem ...";
/sbin/modprobe ungrab-winmodem
fi
if ! [ 'lsmod | grep slamr'="$B" ]; then
echo -e "\n\rRunning modprobe slamr ..."
/sbin/modprobe slamr
fi
if [ -x /usr/sbin/slmodemd ]; then
echo -n "Starting SmartLink modem
daemon: "
echo "/usr/sbin/slmodemd"
/usr/sbin/slmodemd
--country=$SLMODEMD_COUNTRY $SLMODEMD_DEVICE
1>/dev/null 2>/dev/null &
fi
}
*** other part of code left out for space purposes ***
however, if I leave the part as is above before the calling of the module and I type
/etc/rc.d/rc.slmodemd start|stop|restart
it will work, but will tell me that /dev/ttySL0, /dev/tty..., already exist and it proceeds, I wanted to clean that up, but was unsuccessful. Thank you for any suggestions received.
I would like to ask for some help. I try to fix the modules that need a Desktop Icon, and menu entry and I cannot fix them. If someone is willing to fix the modules, I do not mind giving the credit to another person that knows more and can fix them, I have gkrellm, gnuplot, ImageMagic, xine-lib-1.1.12, and xine-ui-0.99.5 listed here:
The xine ui module needs a Menu Entry, and a desktop icon, also it would be nice for the module to do a hdparm -d1 /dev/dvd just like Kaffeine does. I like default mplayer but I made the modules so that users that like xine would use it if it suited there needs. I used configure-for-slax, make, make install DESTDIR=/tmp/fakeroot, clean out the useless stuff using the scripts by Tomas' "how to make modules the right way", but I cannot for the life of me make the desktop entry and menu entries automatically when the module is created.
This part is the one that kills off the modules mentioned above, I copied from mbl's post.
#
# Add SLAX specific files to the package
#
mkdir -p $TMPDIR/usr/src/slaxbuilds
cd ..
cp $0 $TMPDIR/usr/src/slaxbuilds
#
mkdir -p $TMPDIR/usr/share/applications
mkdir -p $TMPDIR/usr/share/pixmaps
cp *.desktop $TMPDIR/usr/share/applications
cp *.png $TMPDIR/usr/share/pixmaps
#
Using the library-path at the modulesite, I would suggest a possibility to for instance write "/usr/lib/firefox*" or only "/usr/lib/seamonkey;/usr/lib/firefox" but that the links were read. The first suggestion is probably safer.
Why :D Uploading a package like the "pigdig_all" or "nspr", "nss" or other parts of the gecko, that still is found in each Mozilla, links first to those in "/usr/lib". In 99 percent of cases, they would be totally unneeded since most use a mozilla-based browser. The second reason, is that the browsers found on the site, keeps getting updated, such that there is not really a fix suffix for them.
Could be you already implemented a wildcard. If so, I really like to know what you have used.
I know you are not a big fan of Gnome, but I just read your SlackBuild on your firefox. You removed two "not needed" Gnome-related libs.
Well, they are needed for instance for Seahorse. I rather see you keep them so that all the mozillarelated and needed stuff can be downloaded via 1 firefox, than 1 firefox + 1 pigdin_all
I dont think there is so much to save by removing "unneeded" things that strictly. Actually I uploaded earlier another Firefox to cope with all these dependencies and suffix that varies. It was deleted when your version of ffox came out. "Exist newer version". So if it will be that strict with one-version-only, it would be great and appreciated that you are careful about removing libs. Even though they are mainly Gnome-related. Gnome has many cool apps that one do not need the whole desktop to use.
# All executables (but symlinks) in /etc/rc.d/ from this module will be started
# with two arguments: "start" "activate". Moreover, all executables in
# /etc/rc.d/rc*.d/S* will be started as well.
# This is done only by the 'activate' script, not in the case when the module is loaded
# during OS startup (in that case, your distro is responsible for execution)
/usr/bin/activate ,line 71 find $IMAGES/$MOD/etc/rc.d -type f -maxdepth 2 -mindepth 2 | egrep '/S[^/]+$' \
should be find -L $IMAGES/$MOD/etc/rc.d -type f -maxdepth 2 -mindepth 2 | egrep '/S[^/]+$' \
or else there is no activation of scripts that begin with "S-my_script" in /etc/rc.d/rc3.d
(they are sym links to ../init.d/my_script.sh )
the scripts in /etc/rc.d/ working
this is when module loads on the fly
also /usr/bin/deactivate line 46 find $IMAGES/$MODULE/etc/rc.d -type f -maxdepth 2 -mindepth 2 | egrep '/S[^/]+$' \
to find -L $IMAGES/$MODULE/etc/rc.d -type f -maxdepth 2 -mindepth 2 | egrep '/S[^/]+$' \
or else no stop in script during deactivation.
i will upload driver module that is using these symlinks.
Thor wrote:
Using the library-path at the modulesite, I would suggest a possibility to for instance write "/usr/lib/firefox*" or only "/usr/lib/seamonkey;/usr/lib/firefox" but that the links were read. The first suggestion is probably safer.
I do not like to support wildcards. On the other hand, I agree the LibraryPath should understand symlinks. I'll do the change if possible.
Thor wrote:
Uploading a package like the "pigdig_all" or "nspr", "nss" or other parts of the gecko, that still is found in each Mozilla, links first to those in "/usr/lib".
I can't find ANY modules with "pigdig_all" or "nspr", "nss" in the title.
Thor wrote:
In 99 percent of cases, they would be totally unneeded since most use a mozilla-based browser. The second reason, is that the browsers found on the site, keeps getting updated, such that there is not really a fix suffix for them.
It seems to me you're still referring to LibraryPath as if it were supporting a cross-module dependency. It doesn't work that way. If that works, it's more likely a bug :) The library path is to be used only for the current module, that means, if a different module needs the same library, it should not find it in the first module (where the library is in a nonstandard directory).
Thor wrote:
I know you are not a big fan of Gnome, but I just read your SlackBuild on your firefox. You removed two "not needed" Gnome-related libs.
Well, they are needed for instance for Seahorse.
You see, this is the perfect example why to provide build scripts, even for modules created from Slackware's TGZ packages.
The removed libraries (libgtkembedmoz.so and libnkgnomevfs.so) depend on some other gnome stuff, which is not in Slax. So the libs alone are useless, and your other software can never use them unless you install the other dependency.
I dont think there is so much to save by removing "unneeded" things that strictly.
Well, the libraries itself would be OK even if not used, but unneeded is the dependency of Mozilla Firefox to libgnome.
Tomas M wrote:
I can't find ANY modules with "pigdig_all" or "nspr", "nss" in the title.
.
Well I uploaded the nspr. I put a "delte me" on it, since I considered it more a bug because it was linked to every god d* other netrelated module as a dependency due to the Gecko engine. And gladly it has been deleted.
The pidgin is not approved yet, so it can explain why you have not seen it. If you feel to take a look how the Gecko in it, affect the depchecker, here is the link
I think I have made the slmodem module better. It should be working better now, uploaded the code to latest slmodem-2.9.11-20070417.tar.gz from LinModem Resource Page:
Thor, what is the purpose of your module 599? You want to show that all those people do not use library path correctly? That's true. But that is not my problem. Or you want to show anything else?
Tomas M wrote:
Thor, what is the purpose of your module 599? You want to show that all those people do not use library path correctly? That's true. But that is not my problem. Or you want to show anything else?
Wnat to show you that it is not working as intended and you could add some features into it.
F.ex is it a joke that the same module #600 which has libpath /opt/gnome-2.21.3/lib, which is the exactly same libpath as 3 other modules that is linked on the bad one #599, is not linked before the bad one. Same path should qualify as same "package" and therefore be prioritized.
I also wanted to illustrate how easy it is to fck up the depchecker as it is now, and as Gusterrapolis continuously do (although without purpose).
I have told you this before in here, and I KNOW you can easily fix it. But seemed to me as you did not regard it as any major problem, since it was yet to interfere with your modules.
The last purpose was to show modulemakers that they should actually use the librarypath box, even though it is not perfect.
Well maybe the very last was to try to convince you to improve it, before I just give up keeping packages clean.
I guess you saw it, so I post a delete on it, if you have not already removed it.
No offense, I knew it was a drastically mean. The intentions and the points I make though, are good.
Thor wrote:
Want to show you that it is not working as intended and you could add some features into it.
In my opinion, it IS working correctly.
Indeed I can add some more features into it, if I find it useful. But currently I do not prefer to modify depchecker to prioritize modules with the same Creator, as I believe it is NOT systematic. I am considering to prioritize modules with the same LibraryPath, as suggested by Thor long time ago, but that doesn't mean I will implement it.
The depchecker works this way:
1) first, try to find the required library in the module itself, in standard directories and then in the directories specified by LibraryPath.
2) if not found, try to find it in official Slax modules (001-006).
3) if not found, try to find it in verified modules (listed at slax.org)
4) if not found, try to find it in unverified modules, use the smallest one
F.ex is it a joke that the same module #600 which has libpath /opt/gnome-2.21.3/lib, which is the exactly same libpath as 3 other modules that is linked on the bad one #599, is not linked before the bad one. Same path should qualify as same "package" and therefore be prioritized.
You suggest to prioritize modules with the same libraryPath. I agree it's not a bad idea. But it won't help us with this particular problem. After all people understand how to use LibraryPath, all the 'bad' modules will be 'fixed' by their authors (libraryPath will be specified) and you will be at the exactly same situation like now - there will be many modules with the same libraryPath and the system will have no idea which one should it use.
In my opinion, the problem has a different solution:
- when some module is verified, all the other modules with the same files must be DELETED.
I also wanted to illustrate how easy it is to fck up the depchecker as it is now, and as Gusterrapolis continuously do (although without purpose).
I told David to yet ignore all modules from Gusterrapolis and Thor, you two are making a lot of mess.
I have told you this before in here, and I KNOW you can easily fix it. But seemed to me as you did not regard it as any major problem, since it was yet to interfere with your modules.
I still do not understand what part should _I_ fix.
In general, there is no way to correctly decide which other module should be linked as dependency. The only way to deal with this is to delete all other modules with the same libraries. For example if there is a FireFox module, there should not be any more firefox modules at all.
The last purpose was to show modulemakers that they should actually use the librarypath box, even though it is not perfect.
The LibraryPath box is there only for one purpose: if your module understands libraries in a nonstandard directory, it's not possible to detect that automatically (or at least I do not know how to detect it) and thus it must be provided by the module author.
But if your module needs some library, which is in a Mozilla package, BUT THE SOFTWARE IN YOUR MODULE CAN'T SEE THE LIBRARY THERE ANYWAY, it is not any good idea to specify LibraryPath and 'fix' the depchecker instead of fixing your module itself.
Tomas I will lay this one dead. We just keep going round in circles
First I have to say I never said it did not work. I said it did not work as you intended. Of course the latter imply "as I thought you intended". If you say it works as you intended, I will adapt to that.
But I dont really get you. I though the whole idea behind the new linksystem, was to keep it modular, to keep it small and to reuse libraries as far as could be done. To some degree I see an improvement, but on the other hand, I still see the "big bloated modules" on their way, which will include 10% of the same libraries as another big module. The way it is right now, that is just easier to make it.
Instead of using energy in trying to explain, so much that it even gets close to an argue, it is, for the very moment being, just easier to make 1 big module, f. instance Gnome, and let the user Remove the unneeded programs himself, instead of vice versa, which would be to try to keep it as small as possible and let the user add what he wants. The "big" way one can make sure to fulfill all needed dependencies without some other occasional "all_in_one" module occuring and interfering. But then again, maybe that more "traditional" module approach, in reality is prefered by a lot of Slax newbies.
Edit:
An example. Take "metacity" which is a windowmanager that dont really need Gnome, but it is used as default in Gnome. Since it can be used "stand alone", I think the best way is to separate it out from Gnome and instead have the depchecker to link it. But does a newbie really know what "metacity" is. When 10-20 other irrelevant links occur on the Gnome module's page, will the newbie really know that "metacity" is a must, but 15 of those others are just irrelevant crap, that are actually already inside one of the other linked modules (the Gnome-platform). The answer is, as we all know, a clear "no". The newbie does not know that. So to avoid people saying "it does not work, it is no good" etc...it is just easier to include metacity + 20 other major apps + 20 other libs already found in slack-current and not Slax.
Another example is Digikam. I compiled libkipi,kipiplugins, jasper. Well I compiled all, but those 3 + sqllite are the ones used by many other applications. The others can be justified to include into the mainpackage. due to less used by other applications. But the quiz became like Should I just put them all into Digikam, or should I allow other to reuse them without downloading the whole Digikam. Well, the result of the latter is, that the module will look "messy" as you say it. But is not the philosophy of Slax to keep it small. Then why download the whole Digikam, when all that one need for another module, is that tiny "libkipi".
In this way, I just dont understand where you are coming from. But wherever that is, it is ok for me, just prefer to know it. I see the problem with millions of small libs around all over the section, but once again, there is also an advantage one looses when those small are packed into a larger one. The last was quite off-topic, just that sometimes it feels as your guideline states "a little bit of this, a little bit of that". Most times it works best I suppose, other times, not so easy.
Conclusion must be that there is no real conclusion. I'll stick to your rules, it is just that even your rules, are not that clear that there are no situations where it becomes Tomeito, Tomato what is chosen. This was mainly why I wished you could improve the depchecker a little bit more (not saying it does not do a good job, just that it could do even better).
I think it would be an improvement to give higher value to same librarypath on 2 different modules. What I really think you should, and still can do, is to convert the slackware-current tree, such that one do not need to upload packages like FLAC et more. The slack-current tree would also make a soundable base for the dependency checking and many of those libraries found there, are recircled by a lot of apps.
F.ex. should I know include a needed library "libcdio" in a module... If so, should I use the slack-current or recompile with different path. The slack-current is fine for now, but will be outdated plus it may also happen that Tomas include it as default in Slax. If the latter happens, then by definition I am not allowed to let "libcdio" stay within my module. Maybe I should just upload it separately, but then again, there are so many of these small 300 kb libraries that could be uploaded or they could be taken into the module from the beginning.
Also, libcdio gets updated, so boring to reupload 70mb module because a 500kb lib is updated.
Those problems could easily been avoided, or better maybe is better to say, with a slack-current lzm-version.
The whole thing is very easy when one makes these silly small modules like aircrack-ng, like htop etc. But when one do bigger projects/modules , it is just a lot of problems one runs into, and that is when one also gets to check your depchecker more broadly. Slax itself is one of those bigger projects, and it constantly changes despite it rather mature age.
Interesting exchange of view I suppose. I am a newbee , I like Slax since a long time, it is light and modular. But the module section is growing so slowly that I fear I will have to wait so long to have my favorites apps included ... I am sorry, I am not clever enough and have no time to invest in developing my own modules. So I can say, Slax, as it is now, is not anymore modular as there are quite no modules .
I read in this forum that module repository for Slax 5 was bad and you want to do something much better. Ok but even if all modules .mo were not working for me at the first time, (but apparently where OK on some other machines) i could find what I needed with the help of authors in this forum.
I had so many things: Slax working in arabic,in chinese, with Lyx, and Kile and Digikam etc.
In a few words, best in a long time is not better than not very good now.
I agree completely with the people that suggest an official repository and an other one where everybody can upload and try and comment modules; some users are clever I think, and that is the strongest point of linux distros: use the skills of the community; even if it looks a bit like a mess.
Every user can have a different way of using Slax. For exemple, sometimes I want to look at my photographs, so I load Slax with Digikam and run. If one hour later I decide to write a paper with Lyx, no problem, I shut down and start again with Lyx this time ...etc I am not doing two so different things at the same time. So I need the Digikam module include all dependencies, same as Lyx, etc never mind if Gimp brings the same library, I dont load Gimp everytime I load Digikam
Hope it helps
Couscous wrote:
Interesting exchange of view I suppose. I am a newbee , I like Slax since a long time, it is light and modular. But the module section is growing so slowly that I fear I will have to wait so long to have my favorites apps included ... I am sorry, I am not clever enough and have no time to invest in developing my own modules. So I can say, Slax, as it is now, is not anymore modular as there are quite no modules
Lol. Good point :)
Interesting point of view Couscous.
Personally I have gone from being very content with the sort of "all_in_one" or "Synaptic" (which is more or less the same), when I first started to walk in linux with no Windows. Now I prefer the total opposite, the split-up of everything. The latter is not always practical, but one asks oneself "hm wonder what that missing lib actually does. Gotta go to Wikipedia and have a look", so it becomes a bit fun due to the learning.
Despite that, I have a feeling that most Slax-users are a little extreme. From people who prefer or at least can fix it themself no matter how Slax and modulesection is organized, to those testing their first distro. In that matter, I'd guess that the modulesection will do most good to the last mentioned group. But how ?? :)
I cant really answer that one. But I can add I too believe that many people like to get the "unverified" modules that are out there now, then to not be able to test anything at all.
Thor, I sent you another email with zero response from your side. So I guess you do not like email; so I'll continue in this thread. But I won't reply to all your comments, because it's hard for me to follow up. For now, I'll just focus on your first paragraph:
I though the whole idea behind the new linksystem, was to keep it modular, to keep it small and to reuse libraries as far as could be done.
Yes, that is very correct. That is the idea. And I believe this idea is successfully implemented. Why do you think opposite? Please explain on examples.
To some degree I see an improvement, but on the other hand, I still see the "big bloated modules" on their way
On their way? What does that mean? There are some UNVERIFIED and UNCONFIRMED 'big bloated modules' from several people in the repository, but those modules will hardly become verified. Why do you care so much about them? Why they bother you so much? Whats wrong with them? Leave them where they are, simply ignore them. Is it OK now?
I should be staying out of this, but I'll say my peace.
This is Tomas' project, his creation, his rules. We can make suggestions, but if he doesn't want to implement them, there is no changing that. Accept it and let it be.
As previously discussed, we have the official and verified modules on slax.org and we have numerous (at last count at least 10) user repositories with unofficial and unverified modules. If you don't mind unverified modules, and you have space to run bloated modules, then use the unofficial ones. If you're a stickler for "official" stuff, then download only what Tomas verifies in the modules page.
Does it matter if one leaves it empty ?
The startup command is for modules where it has some sense (eg. applications).
You can leave it empty if there is no command to be started :)
Just a quick question with 6.0.6 I could not start wpa_supplicant and wpa_gui. Was this removed. And will it be added as a module later. Any answer is appreciated.
I don't think wpa_supplicant (which includes wpa_gui) was ever a part of slax, hence a discussion in one of the other threads. There are modules for it.
Guest wrote:
Just a quick question with 6.0.6 I could not start wpa_supplicant and wpa_gui. Was this removed. And will it be added as a module later. Any answer is appreciated.
Markds. Thanks for the quick reply. I saw on your other threads you included wpa_supplicant 5.1. I will grab that. But with slax 6.0.3. Tom included that in the build. I remember because when slax 6 initially was released I had to compile it myself and copy it over from my slackware box. I had reference to libraries that weren't available. With 6.0.3 he included it and cleared all that up. But hey no worries. As long as I can get it no big deal. Thanks for your help. I appreciate it. Are your modules still in the pending approval state. P.S. Tom if your reading this terrific work on a light weight linux live edition.
I have not read all the posts in this thread, so I hope this was not answered already somewhere above... Please forgive me if it was answered already.
My question: How can I search for a module which has the "This module is not verified yet and thus it is not listed in the official repository" status?
E.g. I am looking for a OpenOffice.org module. (Should that be in "editors" when it is verified?)
Or maybe others are looking for my "Nvidia Driver V169.12 for Kernel 2.6.24.4" module.
Thanks to Tomas, and David I am getting better at fixing the modules that I have created although most of them are not perfect and are a work in progress. I have a very big question regarding a module or group of modules
When I try to make the buildscript for module in the link above, I combined the first module with the second using
root@slax:/tmp/fakeroot# lzm2dir wvstreams-4.4.1.lzm temp/
root@slax:/tmp/fakeroot# lzm2dir wvdial-1.60.lzm temp/
root@slax:/tmp/fakeroot/temp# cd ..
root@slax:/tmp/fakeroot# dir2lzm temp/ wvdial160.lzm
[================================================================]
268/268 100%root@slax:/tmp/fakeroot#
root@slax:/tmp/fakeroot# ls -l
-r-------- 1 root root 188416 May 3 01:24 wvdial-1.60.lzm
-r-------- 1 root root 1687552 May 3 01:30 wvdial160.lzm
-r-------- 1 root root 1499136 May 3 01:13 wvstreams-4.4.1.lzm
I have tried repeatedly without success to make the module all in one script. Is it okay to put two separate modules or leave the wvdial-1.60.lzm on the modules page. I am having a difficult time putting the pieces together. Can someone suggest a better fix?
Which is the best way to do this?
Leave wvstreams-4.4.1.lzm and add the small wvdial-1.60.lzm(the standalone one that depends on wvstreams-4.4.1.lzm), or still combine them into one and have three different packages.slaxbuild's.
I also at one time saw that the module wvdial supposedly depended on other modules. Several dependencies were removed and now only tk--8.4.18-i486-1
I beg to differ. The wvstreams module is stand alone, it includes the libraries that wvdial needs to dialout. They only share one part in common
/usr/bin/wvtestmeter
requires wish found in: tk-8.4.18-i486-1, gparted_0_3_6_all_s6_03, gparted 0.3.7 all
If you compile wvstreams-4.4.1 in slax, you will see that you did not have to download the source for tk-8.4.18-i486. There has to be a better way to clean this up. The modules are being checked and I know it is very hard for Tomas and the other power Slax users which help out.
I believe that I have fixed some of the other modules slmdodem and martian with a buildscript that is working. I have also fixed them so that wvdial is not required, but only create it for those users that use slax without KDE and need something to connect to the internet. We cannot leave them out :)
Thank you all for reading. Any suggestions/comments are greatly appreciated.
Been checking my script's logs to mirror the modules and apparently 653 modules have been uploaded (including the core modules) but 135 of them have been deleted. Includes verified and unverified modules.
If you mean downloading all the modules, yes it was - but only once a week at midnight Singapore time and sometimes in the middle of the week if I update manually.
OK, no problem at all, I was just wondering if you are personally testing many uncofirmed modules - in that case I would ask you to send me IDs (by email) of modules which are completely OK and should be in your opinion verified and published :)
Rava Wrote:
I have not read all the posts in this thread, so I hope this was not answered already somewhere above... Please forgive me if it was answered already.
My question: How can I search for a module which has the "This module is not verified yet and thus it is not listed in the official repository" status?
E.g. I am looking for a OpenOffice.org module. (Should that be in "editors" when it is verified?)
Or maybe others are looking for my "Nvidia Driver V169.12 for Kernel 2.6.24.4" module.
Does anyone have an answer for this question? It would allow people to easily find a module. (better unverified than nothing)
fundamental wrote: Rava Wrote:
I have not read all the posts in this thread, so I hope this was not answered already somewhere above... Please forgive me if it was answered already.
My question: How can I search for a module which has the "This module is not verified yet and thus it is not listed in the official repository" status?
E.g. I am looking for a OpenOffice.org module. (Should that be in "editors" when it is verified?)
Or maybe others are looking for my "Nvidia Driver V169.12 for Kernel 2.6.24.4" module.
Does anyone have an answer for this question? It would allow people to easily find a module. (better unverified than nothing)
The question was: is there a simple way to search all of the modules, including the unverified modules?
The nvidia driver was used as an example.
It would be useful to have a list of all uploaded modules, irregardless of their verification, to see what modules have been started or are somewhat working.
i think there are no reservations for uploading modules, so if someone uploads a modules it's unverified not only for correct building but also for functioning.
btw, in the link markds gave you above, you can find lotta more modules, just leave out the nvidia module filename ;)
There are a lot more modules, official and unofficial, verified and otherwise and even the old slax 5 modules there. I would suppose its easier to search for what you want there, but that by no means should indicate you shouldn't check the slax.org modules page first.
Modules are updated every Sunday.
I would dare say its not easy to search for unverified modules on slax.org and that is because I'm pretty sure Tomas doesn't want users downloading unverified modules that might mess up their system. Thats the reason behind the "official" site - to ensure you get quality, approved modules. If you download from elsewhere, you do so at your own risk.
fundamental wrote:
The question was: is there a simple way to search all of the modules, including the unverified modules?
The nvidia driver was used as an example.
It would be useful to have a list of all uploaded modules, irregardless of their verification, to see what modules have been started or are somewhat working.
Hi All,Just a note of thanks to Tomas and all included for the Slax 6.0.7. Live CD and to the man who posted Audacity V 1.3.5 beta (unicode) I 486.LZM .I apologize for not remembering and now I can't find it :o( While I have managed to add this file it is definitely there ,although not operational(presumably because I haven't met some dependency requirement) or anyway from a newbies idea,I suppose this is the case.I will say Slax has certainly peaked my interest in Slax/Linux and hope to learn enough to get by.Thanks again.Cheers
I am find that most modules from old version of Slax (*.mo) works in Slax 6 if rename it from *.mo to *.lzm, So Why we need wait for new versions of modules if old one working good? And why you not place a working modules from old version Slax?
There are no plans to add non-english forums Tomas M:
Well that has been discussed many times, and I still feel unhappy making international forums. From my point of view, it's better if everybody can understand each other. So we use english, as most of the computer community will speak (or at least will understand) english.
If there are international forums, I would never visit them (as I won't understand them) ... Those people who can't speak english can freely make own forums for Slax in their language at their webpages.
Tomas has a child (if you couldn't tell by the sticky thread) and only one other person is reviewing modules. It takes time to look at all of the modules and there are a lot of modules.
This forum was an attempt for the community to perfect everyone's modules and let the reviewers have to only look at a few modules that are ready to be checked.
hootch wrote:
Wow this is a great way of sharing modules. If I become slax-productive enough I'll try and create a module for Teeworlds! Summer project ftw :)
Through the magic of regular expressions I present the list of ALL (I think) modules hosted at www.slax.org in a sortable wiki table (may have slight format errors (ie repeated entries, approval and working columns may be inaccurate, and misplaced columns) ) http://slax.scribblewiki.com/Module_List
As long as that page does not crash there should be no trouble finding modules stored in the official repository any more.
To see the spaghetti logic code that generated the list with obfuscated regular expressions see the bottom of the discussion page.
@Vbotond,
Like any other Linux software can be installed via multiple methods, but Slax specializes in modules. I recomend using modules or installing the software with another method and converting that to a module.
I submitted some modules. As far as I know they are correctly compiled:
* Revise - a command line tool I made for quick file revisions.
* p7zip - port of command line 7-zip for Windows to Unix-like systems
* UPX - command line tool for compressing executables
* Lua - programming language interpreter, compiler and development library.
I noticed in the making modules documentation, that *.slaxbuild files were mentioned for programs built from source code. Is this a script to build the module itself or to compile the program from source? Or indeed, both?
If improvements are made to the module pages a nice feature to add would be a list of possibly conflicting modules for each module. Possibly conflicting modules would be modules that contain files with the same names and directories with different content. It should not be too dificult to implment either. This feature could show authors that there might be a problem with how they created their module and warn downloaders about which combinations of modules might cause problems. If this feature is implemented it would also be nice to have a page like the detailed dependencies page to show which files conflict on the modules that do have conflicting files contained.
Rava wrote:
Is there any font viewer module available, with the ability to show the system font as well as not installed fonts like fonts in a certain directory?
I searched the web and found some like gfontview or wxfontview, but was not able to get them to run (one wanted python 2.4 instead of 2.5)
Only gucharmap (which is more of a charviewer) runs without problem, but this program only shows the installed fonts.
I hope some of you have already a working font viewer lzm (and are willing to share).
I have gfontview, but there are too many missing dependencies. I've gotten one, but maybe you can help find the others.
I have gfontview, but there are too many missing dependencies. I've gotten one, but maybe you can help find the others.
Which one do you have and which one do still miss.
And which version of gfontview you try to make into a lzm (e.g. could be I tried it with a newer one and so it would be advised I try finding all missing dependencies for my own version)
I just got slax and I am very happy with it. Now I want to customize it and... well... I don't know what to do. I tried reading the "manuals", but they confused me even more. The manuals keep on referring to a "/slax" location. That location doesn't exist! When I created it, and put some modules into a /slax/modules folder, and rebooted, only the firefox module activated on boot. GNOME didn't work, since I still have KDE, and neither did the "human" look.
Can anyone help me? My hope is to make Slax look like Ubuntu, and have all the Ubuntu apps.
Any modules for clamva being worked on? I was thinking about creating one if there was not one already getting cleaned up and going to be put back in the modules page.
i am trying to install a few things on my slax, but every time i click on the modules, they all say an error, and everything i am trying to use, come from this site, so i know they work, but just not working with my slax. I am running my slax off my usb, and i have a folder on my drive for linux downloads, and thats were i go to get to my modules, Do i have to put them in a module folder or something?
i already activate wine-0.9.60-i486-3tb.lzm and so with wine-1.0-rc3-i486-1tb.lzm
so, how can i use that things? so what the different between it? thx 4 the light
I tried to update a module I uploaded last week and it said I couldn't update it during the "revalidation process." I don't think Tomas should be the only one validating them as that would take way too long; he should assign other people to help.
fundamental done a good job!
i think a lot of module from his unofficial wiki is eligible for slax. check them all...
i use a lot of module from there. they r all working nice.
everybody need that.
I am new to Slax. In an attempt to get my wireless usb adapter to work I have tried to activate multiple modules including NDISWrapper, (multiple) WPA Supplicants, and madwifi. The modules will either not activate due to an "Unknown Error" or will activate but then be unable to load. How can I get the modules that will activate to run?
Thanks
Thanks I wil refer to that later, but my current issue is getting Slax Modules to work properly. I'll download an lzm file from the module list, move it to the Module directory in my Slax USB folder and it still won't load (sometimes it will activate but it still won't load or create an icon in the KDE menu). In the Module Manager the data location of the modules I am attempting to load is "Unknown", maybe this has something do with the issue.
Hello... I'am ioetre and I have a problem. In short... Slax is a verssion of linux almost perfect... is bery bery good. And my problem is a new laptop "ASPIRE one" whit processor "intel Atom" of Acer company; I wantto initiate whit the lastest version of Slax instaled in my pen drive USB of 4G. My laptop says "not modules finded for kernel"... I understend a few from this but I would want to know a solution. I don't want a ubuntu or linpus or other in my laptop... I want Slax... What can I do? Slax in my pen drive starts good in each machine tha I have proove...
ioetre wrote:
Hello... I'am ioetre and I have a problem. In short... Slax is a verssion of linux almost perfect... is bery bery good. And my problem is a new laptop "ASPIRE one" whit processor "intel Atom" of Acer company; I wantto initiate whit the lastest version of Slax instaled in my pen drive USB of 4G. My laptop says "not modules finded for kernel"... I understend a few from this but I would want to know a solution. I don't want a ubuntu or linpus or other in my laptop... I want Slax... What can I do? Slax in my pen drive starts good in each machine tha I have proove...
Just reformat your pen drive and put slax on it again.
Respnse to Slaxrocks....
Nooo no no no... that's not the solution... I understand that Slax have not modules from the procesor intel Atom... I need to know if I can modify Slax whith another kernel. But I'm a beginner programaer, I don't know if I can to do that....
Other data is that Slax is functional in my laptop if es running like a virtual machin whit VMware workstation but just like image ISO.
So, then who is that is functional if do not have kernel... It is confused....
My slax is cool i like it. My only problem is that it needs too much time on my big machine finding the livecd.sgn which is rubbish cuz its on the usb drive but it seems to look there through my harddrives too. How can i modify that so the boot mechanism works faster?
But i also want to participate in designin and creatin slax.
I also got some interest in deeper sphere stuff that might could improve workin of Slax...
I've done a module that adds 11 templates for new files by right-clicking or in Konqueror>Edit>Create new. Templates are 3 images (BMP, PNG, JPG), 3 sounds (High and low quality WAV, high quality OGG), 4 compressed files (TAR.GZ, ZIP, 7Z and RAR) and 1 empty bash script. Those happened to be the ones that I always miss, but please send your suggestions/templates/translations/bugs. I'm aware that it will never be an official one since it doesn't follow Thomas rules but please test it (it's my very first module for Slax 6) and report your feedback.
I've made also a generic autoinstallable script (extratemplates-1.0.sh) , in theory suitable for any distro. I'd like to know how it goes under KDE 4 and Gnome. Anyone willing to do some testing? Download it from http://in.solit.us/archives/show/154219 or galinux.myftp.org. Thank you in advance.
UPDATE: It doesn't work with gnome (thanks Mario and Andres)
@Товарищи плиз помогите! It is impolite to write in a language that most of the users here don't understand. Please read the forum rules. Any way it was stupid for me to even bother writing this post...
The referencing of "official" modules is taking aaaaaaaages... This is probably for good reasons, however it would be nice then if an "unofficial" modules listing existed. Is it the case somewhere?
maybe we should start a new thread where people can vote on a priority list for to be approved modules
that way we can all get the modules that are most important
I have just started exploring slax 6.07. I have compiled some personal Qt4.3 programs on suse and I'm trying to move them to slax. My version of Qt is newer than the version on slax so when I run ldd it states that 3 libraries cannot be found libQtGUI.so.4 and its network & core counterparts. I tried copying the 3 libraries to a variety of places with no success, in the end in /usr/lib I renamed Qt to something else and copied my suse library to slax/usr/lib but still ldd fails to find them. In suse (and windows etc) I can set path, include and lib to pick these up, I cannot find .profile in slax so I'm stuck. I followed the rational behind modules but until I can find libraries cannot make a functioning one.
Following on from the above note, ldd in slax now recognises the later versions of libQtGUI.so.4 + network + core. However I then get the following
root@slax:/tmp/POS/sales_client# ./sales_client
./sales_client: /usr/lib/libpng12.so.0: no version information available (required by /usr/lib/libQtGui.so.4)
Segmentation fault
This is the first time I've tried to move Qt programs from suse - any guidance would be welcome. It was working well in suse.
Thank you, I'll investigate them. I think the problem was probably that I had not defined directory paths well enough within my Qt code for deployment. I re-read the Qt deployment howto and it became clearer. If I can code on suse and run binaries on slax I'll be very impressed. Just need to get slackware up and running, my impression is that a slax/slackware combo would suite me very well for client/server use.
PAN and klibido modules would be very much appreciated.
PAN breaks for me :
root@slax:/mnt/hda1/downloads/Linux# pan
pan: error while loading shared libraries: libgnet-2.0.so.0: cannot open shared object file: No such file or directory
Charles-ML wrote:
Can I do something to add more modules at slax modules page ?
I want more programs here, can I do it somehow ?
see fundamentals post a few messages prior for now ... http://66.246.76.162/slax/wiki/Module_List
My question is this now ...
If Tomas has a Approver of Modules, then why doesn't the Module Approver provide appropriate correspondence to assist with a module developers approval process?
Is it just the slackbuild requirement?
If so, then I challenge the Module Approver to "teach us the way"
After been tired for waiting for other people to continue Slax6 development, I finally did it myself.
I compiled four very useful networking programs into one Slax6-LZM file :
1.) pan 0.132 ("pan2"), WITH NZB support
2.) bftpd 2.2.1
3.) tlswrap 1.04
4.) fakeident
The file is less than 900 kb, you can find it at :
Notes:
1.) Pan 2 : I was tired about old Slax5 PAN newsreader versions, I badly needed NZB support. So I grabbed the compiled PAN from Opensuse 11.0. "ldd pan" revealed that three more libraries were required on Slax6, namely libgtkspell.so.0, libenchant.so.0, and libgmime-2.0.so.3. I took these out of Opensuse11, copied them into my lzm-workdir, made a lzm with dir2lzm and it worked!
2.) BFTPD is the only decent FTPD working fine with slax. Contrary to what you have heard or seen as other FTPD-lzm-modules, proftpd did not work fine for me no matter what I tried. So I compiled BFTPD on another machine, took the executable file to Slax, and it works fine.
The manual page is included, but you can just start it with "bftpd -d".
I disabled a lot of security checks, i.e. /etc/ftpusers is ignored, root can login, etc.
You may want to change this - just feel free to edit /etc/bftpd.conf .
3.) tlswrap is sometimes useful to make a secure ftp connection. thus, it is included (without manual). Just start "tlswrap" and the wrapper listens on port 7000.
4.) fakeident is a fake ident daemon. This is required by some ftp servers that check not only your password, but also your IP adress and even your ident information on port 113. It is also useful for chatting on IRC.
Start it with "fakeident your_fake_login_name".
I'd like to see klibido compiled and included into Slax6. Anyone with me?
Note: Go to /usr/local/BNR2/bin dir and start "bnr2starter". The original filename was "bnr2" (all lowercase) but I could not use it because the main program "BNR2" (all uppercase) is in the same directory, and it seems the lower/uppercase same name was messing up something in the directory structure.
I think it would be a good idea to split the Modules section into "Approved"/"Pending Approval"... at the moment it is really hard to find a pending approval module, because we have to click on the author name of an approved module and then search for other stuff that person has uploaded. If we try to search in the search box, it only searches the "approved" modules.
It would be nice if we have a choice to attempt pending modules rather than having to wait for you to get around to testing them. If you're concerned about ppl breaking their computer, you could have a "I agree" button before you allow access to that part.
I hope you don't mind me sticking my big fat nose in about this issue. It's only a minor thing and I'm sure most people won't even care, but I'm also sure we're missing out on a lot of goodies, and dammit... I like my goodies!
Nevart,
You might want to check out this listing: http://66.246.76.162/slax/modsearch/list.jsp
It lists all of the modules in Slax with links to their pages and direct download links.
Once I have some more time I will add a searching feature so that the descriptions can be searched through, but for now one can use the ^F search built into most browsers.
no responsibility is taken by whatever you choose to do with these unofficial modules, so have fun :)
OK. Thank you. My only grumble (not really!) would be that for new users they will not know that there are more modules available. It took me a long time to find out that I could get the extra modules, and even longer to make it into the forum and etc (which only happened because I did a google search for some module that I wanted). I just think it would make everything easier if it was obvious that there are many places to get modules.
I have to say I am super-impressed with Slax so far, there are only a few small things I have had trouble with so far, and I don't mind too much!
I used Slax when it was just a small largely unknown thing, now that my hard drive died and I happen to have a USB stick, I am back for Slax, and I love it! The module system is vastly improved, and the ease at converting/making modules is a +, and the change saving is really good and efficient. I will defiantly contribute to the modules page and these forums as much as possible. Keep up the good work.
I have made a start on this. Started at 10am and it is now 7pm, 50% done! Hopefully if I can keep up the same work rate, it will all be done in 24 hours. I tried automating this task, but it is impossible (for me at least) because of the weird format of Wiki files.
So I am cutting and pasting by hand. To help the process along, please do not make any edits to the page until the current task is complete, and this way we will avoid a situation where one or other of us cancels out the work that has been done so far.
The aim of the project is, of course, to make it easier to find modules and perhaps to help along the process of getting the modules approved (I am guessing Tomas will find it easier if the files are in alphabetical order).
I have attempted to always list the most recent version first, however because nobody has stuck to naming conventions (for example, many ppl used "mozilla firefox" instead of just "firefox", some ppl put the version number ahead of the filename and so on)... it makes a lot of extra work and I may stuff a few up. If after all is done (which I will post here to say!) you notice a problem please either fix it or bring to my attention so I can fix it.
Thanks guys. I am sure all this work will be worth it in the end! Also if there are any objections to my doing this, please voice them ASAP so that I can roll it back to the original state before undertaking too much more work on it.
Nevart,
There was javascript code to automatically sort the entries alphabetically...
They were the arrows next to the text on the first line...
I apologize for not checking the forum earlier to let you know that.
see also: Fundamental: can someone sort the list at http://66.246.76.162/slax/wiki/Module_List alphabetically ?
It has buttons in the heading that will sort the list with javascript.(it is a few posts above.)
No matter. If it was that simple, I am astounded that nobody tried it before. Oh well... I only lost a day!
What I did was I tried to write a script to do it using |- as a record delimiter, but it didn't work, so I gave up and did everything manually. I did not see anything on the page, but then again, I have JS disabled anyway so maybe the button for sorting is only visible if JS is turned on.
Anyway... what's done is done. If it's not good, then just roll it back to how it looked before I did my thing (in the edit history before my "stage 1" edit).
**** Update ***
I went back and tried the page with JS enabled, and sure enough... the buttons for sorting appeared. I'd be embarrassed except that I think it is a bad design for the interface (buttons should be visible even if they do not work). I actually looked for a "sort" feature before starting, did not see any way to sort the columns, so assumed that there was no feature available.
If I had the magical ability I would probably call down a curse on the interface designer for their bad design idea, but in lieu of that awesome power, I guess I will have to settle for just sticking my tongue out at him/her/it.
:P
At least the problem is now solved for anyone who goes to the page and does not have JS enabled. The columns are now in alphabetical order regardless of your JS status.
Just made a few quick edits to http://66.246.76.162/slax/modsearch/list.jsp
It now supports server side sorting (it is much easier to sort stuff when you let your database software do it for you :P ), so no javascript is required. (I am trying to create an improved module list with a improved back end)
Good stuff. There seem to be a lot of lists. Now the only thing I think needs to be done is some SEO, because finding these lists is just marginally more difficult than I guess it would be to maintain them. :)
The forum is a good place for us to find what we need, but I would guess a lot of people never find their way in here.
I had converted a slackware kdevelop pakage to lzm by using tgz2lzm
now when i want to run kdevelop i must type kdevelop in my console and the console windows stays there until i turn off the kdevelop
i want to have an icon of kdevelop and when i click it i can run kdeveop without using console windows
what should i do
I had converted a slackware kdevelop pakage to lzm by using tgz2lzm
now when i want to run kdevelop i must type kdevelop in my console and the console windows stays there until i turn off the kdevelop
i want to have an icon of kdevelop and when i click it i can run kdeveop without using console windows
what should i do
Copyrighted firmware prevents free distribution, but are needed for many devices to work -- mainly wireless devices. I am experimenting a by-pass. I have made a module which does not contain anything but a .slaxbuild. Running this .slaxbuild gives you the firmware.lzm you are desesperatedly missing.
I felt the need to quickly build modules following official guidelines. So I wrote a .slaxbuild as generic as possible, and all my .slaxbuild are easily derived from the generic one with only minor or trivial variations.
prvDir=$(pwd)
[ -f $modSrcNameTgz ] || modGetSrc
modWorkDir=/tmp/${module}.workDir
if [ -d $modWorkDir ] ; then
rm -rf $modWorkDir/*
else
mkdir $modWorkDir
mount -t tmpfs tmpfs $modWorkDir
fi
cd $modWorkDir
modUntar $prvDir/$modSrcNameTgz
cd $modBuildDir
modPatch
modConfigure
modMake
modDestDir=$modWorkDir/$module.dir
modInstall $modDestDir
cd $modDestDir
modStrip
mkdir -p usr/src/slaxbuilds/
cp -p $prvDir/$0 usr/src/slaxbuilds/${module}.slaxbuild
cd $prvDir
dir2lzm $modDestDir ${module}.lzm
#umount $modDestDir
#rmdir $modDestDir
#rm -rf $modSrcName $modSrcNameTgz
-------
I would like suggestions to improve it.
I've improved my gparted module. now it has screenshot :)
I'm not sure about deps of this module, someone tell me pls wether i should make a separate module for gtkmm or not.
@PhilippeL
I would replace: modUntar() {
tar zxf $1
}
with the more generic (tar should be able to detect if the package is .tar.gz , .tar.bz2 , or .tar with this command) modUntar() {
tar xf $1
}
If you want to refine that script further, you might want to look at other users build scripts and perhaps start its own thread (currently it does take up a fair bit of vertical space in this thread).
Some good examples:
mbl's build scripts (inside the modules): http://www.slax.org/modules.php?author=412
my build scripts: http://66.246.76.162/slax/build/
@Slackware_user
I would just remove the unessecery packages, as I do beleive that they exist elsewhere in the module repository.
fundamental,
As far as i can see now there are 2 slax modules with gparted-0.4.1, one is mine(runs out-of-box) and one is simply a conversion of slackware package without deps (i.e you should download 4 other modules to use it).
Which module is closer to slax philosophy?
I think that the gparted without dependencies is more in the spirit of Slax.
The dependencies of that module however might not be in the spirit of Slax.
As far as I know there are few programs that require only one of the CairoMM 1.4.8, libgtkmm-2.4, libsigc++-2.0, or glibmm 1.14.2 modules.
They almost allways require all four. Perhaps it would be best if they were repackaged into one module (most likely under the GTKmm name as it does require the other three.)
This would leave the gparted module with only one needed dependency.
If you think that I am not being accurate to the base of Slax, here is the source:Tomas M at http://www.slax.org/documentation_create_modules_rules.php:
9) Dependencies of your module must be as sparse as possible. That means, the less other modules are required by your module, the better, but also remember to keep the size of your module as small as possible. For example, If your module can run safely without python, then make sure to delete all python scripts from your module, instead of includin python in it.
If your module requires some libraries, which are practically useful only for your module, then include the libraries directly in your module and do not upload them separately. As an example, XFCE requires a lot of xfcelib* libraries, while those are practically unneeded by anything else. So, include them in XFCE module.
On the other hand, if your module needs some libraries or programs, which can be useful for other modules as well, never include it in your module, but upload it separately. For example, python binaries should be always uploaded separately and never included in any module.
fundamental, modules are ready.
i've found some bug in a dependency-tracking system: it prints as dependency the oldest of available modules (i think should be the newest).
This are my first steps in slax-6.0.9 and I need "partimage" to rescue my system, but I can't find the module "partimage" :-(
Has anyone create this module for slax-6.0.9 ?
@fundamental,
thanks for your fast answer, but I think it is at the moment to complicated for me to build my own modul.
I will try it if I have more time.
@fundamental,
I've try it yesterday with the slackware packet and it works fine. I can use partimage with my Slax and I must say "Slax is a very good Linux distribution".
Thank you for your help and thanks to the developer of Slax.
Paust
Tomas M wrote: Thor wrote:
I know you are not a big fan of Gnome, but I just read your SlackBuild on your firefox. You removed two "not needed" Gnome-related libs.
Well, they are needed for instance for Seahorse.
You see, this is the perfect example why to provide build scripts, even for modules created from Slackware's TGZ packages.
The removed libraries (libgtkembedmoz.so and libnkgnomevfs.so) depend on some other gnome stuff, which is not in Slax. So the libs alone are useless, and your other software can never use them unless you install the other dependency.
I dont think there is so much to save by removing "unneeded" things that strictly.
Well, the libraries itself would be OK even if not used, but unneeded is the dependency of Mozilla Firefox to libgnome.
Actually, those libs are in XULRUNNER-1.0.8.? from the Mozilla Foundation. Although this is an older version of the xulrunner libraries its size is negligable compared to downloading the entire Mozilla packages. (The question mark is simply because I forgot the exact version number but I can get it if needed.)
The Mozilla Foundation has since moved on to primarily developing their Gecko Engine, which is really quite impressive and just goes to show what the FSF i.e. community can do!
BTW Thomas, this is a very impressive project. I've been using SuSE for years while occasionally dabbling in other distros' (i.e., Red Hat, Debian, FreeBSD, and many others) and I have to commend you for the SLAX distro, it is simple and yet efficient, a very rare thing to accomplish!
I'm an Architect by trade but also an artist. If you or any of your module builders need artwork for Icons or Splash screen or whatever just drop me an e-mail obrigman@nc.rr.com
I have heard of SLAX before but I have never tried for my self. I'm going to download it tonight I try it. I know I will like it. I have always been a Windows user but one of my old computers have no operating system right now, so why don't I put SLAX Linux on it? Hope I like it.
i'd spent quite some time selecting the modules i wanted. built it up to about 800 MB. today, it takes me back to not having any of the added modules and it looks like i've to start from scratch. (i hadn't tried to download the image).
SAD LOSS!
I build three machines this week for new users I want them all SLAX but I do not dare because of modules. DUMB! Most new users just want media web and office things. Easier. Make them the target group and follow the module rules.
Devs hackers modders slackers will keep right on doing what they want anyway. They do not need good clean proper built modules and good looking page. They don't want Wild West they go play eleswhere anyway.
Almost a year and the module situation is terrible still. Of 15 chosen this past few days only 4 worked. One we fiddled up to work. DONT DARE ASK MODULE OPINION!
New SLAX users screwed each way.
Read these module threads going round round round no where.
The solution is very simple but unpleasant for multiple interests. Many people want their own way and others do not follow rules and make SLAX look BAD! blah blah blah. No change is no change from 2 months, 12 months, SLAX5.
I say dump all unverified modules from SLAX pages now.
There be tonnes of unverified modules on many servers without SLAX name on. VERY easy to find with many people offering their own pages HERE every day full contact sports.
People want Wild West let them.
People want working for sure let them have less choice and SLAX look good AND just work.
@mamaslax
it is written with warning letters ,on unaproved modules
"Warning: This module is not verified yet and thus it is not recommended to use it. Do not trust it until it is reviewed." . so whats the problem ?
"I say dump all unverified modules from SLAX pages now."
Tomas actually resist making the unverified modules visible for a very long time , and as a lastv resort you only allow it to be visible and therefore downloadable to the users , when it become clear the checking of all modules is no longer a viable options .
So rather than dumping (immediately) all the modules , he make it available but users are caution that they are not verified.
So it's really up to the users to decide to used it or otherwise.
When slax 6.10 comes out ,Tomas mentioned random checking and potential mass deletion of unverified modules.
Contrary to mamaslax 's experience , most of the module work for me , but then again I am mostly using modules made by known Users (whose modules I had successfully used in the past
Let me put it this way , if users can risk down downloading an entire iso of an operating system , what's harm can a single module do ? . The risk cannot be more than trying a new iso or even a new version of slax.
You just need to keep your back up in place and up to date.
No risk No Gain.
%the_greek
If you actually want an answer I will make you the list.
%jcsoh
I regard the ideas pretty much the same on my own. My time is well paid for.
I suspect the question is the value of others and their time.
Perhaps a value system issue.
Turn the coin over.
Think of new users.
The front page says it is modern well organized outstanding design easy - and the middle bit:
"If you're missing your favourite text editor, networking tool or game, simply download a module with the software and copy it to Slax, no need to install, no need to configure."
When a new user comes here and downloads the ISO after reading that they get screwed.
The modules are not only disorganized they say "DONT USE THIS!!!" on them AND
When they don't work the only option is to endure the full contact forum to get directions MAYBE on how to "configure" something that might work for those who can wade the ancient lingo and values.
This makes SLAX look very bad. False advertisement. No regard for others.
The pages look great but in short time it is clear it is disorganized - but not clear why.
This makes the same bad experience.
"Easy" only for a very small group of privileged people who share a narrow value system but everyone else go suffer.
Very bad for SLAX. Very bad for Linux.
End result predictable and unrequired. Bad for SLAX Bad for Linux Bad for everyone except itty bitty group who gain from suffering.
This is no problem if the new user never needs a module.
This is very much smaller problem if only proper working modules are on SLAX site for download.
There is almost zero harm in only offering verified modules.
There is clearly harm in the opposite.
Currently Tomas M is the only individual who can approve modules.
I will guess that this will change after the module cleanout, which he has plans to do.
(for more information you may wish to see the blog)
Also, it appears that some of your modules do not follow rule number three. If you compiled the module from source codes, provide the build script, which is used to create the module.
If you are going to have modules, it is best if they have a slaxbuild or leave the traces that package conversion leaves behind.
MamaSlax wrote:
The modules are not only disorganized they say "DONT USE THIS!!!" MamaSlax, stop the whining and trolling. What it says in the modules page is: Warning: This module is not verified yet and thus it is not recommended to use it. Do not trust it until it is reviewed. That can take several days or even months, so please be patient. I "translate" this as "Use at your own risk" and not "Don't use" as you say.
MamaSlax wrote:
When they don't work the only option is to endure the full contact forum to get directions MAYBE on how to "configure" something that might work for those who can wade the ancient lingo and values.
The forum is there to help people and many who were a bit patient to put down some work have solved their problems. As markds had said in another thread, the people who actually post on the forum and have some problem are the minority and usually are new users who now start to learn. Reading a few threads you will see that the answers they get are not "directions MAYBE on how to "configure" something that might work" as you say, but are specific instructions (go to this link, download this file, edit the other one etc).
What you say "might work for those who can wade the ancient lingo and values" makes no sense to me.
captain_picard
The point was that a module can do a great deal of harm if it is a new user who gets screwed.
It has nothing to do with you.
The "translations" of experienced users are not relevant to either the argument or the point of the argument.
New users, and in particular those coming off a Windows habit, "translate" that big triangle warning sign with a big red exclamation point in and those very scary words based on THEIR experience and exposure not yours.
The SLAX front page says "no need to install, no need to configure."
I would wager large sums safely that "specific instructions (go this link, download this file, edit the other one etc)"
"translates" very neatly to "install and configure" for most English speakers.
The other points you reference.
I argue that there is NO persistent [Stickies] clear instruction on the forum.
Each new user question is subject to the whims of the personalities on forum.
This is not likely to change.
I submit that these personalities are less than consistent in almost every way.
Add to that the fact that a substantial number of the "answers" new users get are directions to peoples personal web spaces instead of the SLAX manuals and Wikis.
In my experience, constantly "inconsistent" and "dependent on personalities", "translates" to "maybe" in almost every human endevour.
Too many of the answers I read over the past year here are unbelievably and unnecessarily uncivil.
Ask yourself this simple question please:
Would you suggest your elders and children read these posts?
Even if they could work out what all the jargon means it is unreasonable to expect them to share or even grasp the values of the forum regulars and be subject to the abusive language.
This is a full contact forum by choice of the regulars not the new users. That makes SLAX look bad.
This other thing.
EDIT:
This bit was really just the pot calling the kettle a spoon.
I apologize to captain_picard and the forum. I have removed it.
"Too many of the answers I read over the past year here are unbelievably and unnecessarily uncivil."
Any change must start with oneself.
Instead of complaining about a lack of proper answer to new users , how about getting the ball rolling to make the necessary change , by answering "properly " and "civily".
I didn't really see any useful answer from you to any posting yet . Perhaps , if you start answer post based on "the high standard you defined" , others may follow.
I for one are impressed on Markds patient and proffesional annswer mainly on wifi / wireless and network , although I do not join such thread as the issues are alien to me.
However , I would agree there are unnecessay uncivil response like the one about "if you wash you stinky armpit.....", but I hope you will understand Tomas has in principle maintained that he will not locked / censored any posting even if he disagreed with any users point of view. He used to assigned some moderator but there are none at the moment, so slax is pretty much an open public forum.
On the other hand Mamaslax , I hope you will understand , the long time users (of this forum) tends to view you as a "whiner" because they have yet to see you as a useful contributor (module contribution wise ,forum posting and answering wise , general wise....), but rather you been posting bone complain after another.
Point taken. Agreed.
I have been a bit to loud for the crowd. Comes from my sterling social skills module.
I was a little shocked by myself. I did/do apologize and time shall tell.
Hi ppl. I don't know where else to post this, so don't get angry:) Aria2c module (http://www.slax.org/modules.php?action=detail&id=1008 ) gives segmentation fault after ~10 minutes of work. Conditions: eee pc 901, pppoe connection over Ethernet, run on SD card. Thanks for a wonderful release.
TOO MANY OF THE ANSWERS I READ OVER THE PAST YEAR HERE ARE UNBELIEVABLY AND UNNECESSARILY UNCIVIL.
THIS MAKES SLAX LOOK VERY BAD. FALSE ADVERTISEMENT. NO REGARD FOR OTHERS.
BAD FOR SLAX. BAD FOR LINUX.
END RESULT PREDICTABLE AND UNREQUIRED.
BAD FOR EVERYONE EXCEPT ITTY BITTY GROUP WHO GAIN FROM SUFFERING.
VERY BAD FOR SLAX. VERY BAD FOR LINUX.
I fully agree with Mamaslax.
...and you can turn it around
To many questions in here are useless for the Slax community and has both been responeded numerous times before, as well can easily be found/solved by a simple search. These questions makes Slax look bad, because they annoy "elder" linux guys away from the forum and Slax appears as a playground for kids. These guys prompting those type of questions scare(bore..) away people and if figuring out how to search is to much trouble for a guy, he/she will hardly ever be able to contribute later. That is because to learn linux, you have to a) learn how to search and b) stop being lazy or afraid of running into some small issue. In other words, take some pride in solving issues for oneself and see it as the best way to learn. That is, if one is interested in learning at all.
Just a thought... And yes its whining, but so is the post about uncivilized replies.
karlo53,
This is not the correct thread for this issue.
Once you figure out what your specific problem is, then post it in a relevant thread or create a new one.
"I have leptop hp mini.I did not know to doo slax for this model help mee.pleas"
I assumed you have one of those hp netbook with no cd/dvd drive ??. In which case you should start off with standard slax booting from the usb . After that post a separate thread in the forum on whatever problems you face .Don't use this thread as you question will not be obvious.
Please post you netbook (??) model number as well , as there maybe other users who are already running slax sucessfully on the particular model. They may be able to help you.
