Bear in mind that what you see is just a preview of raw KDE 4.7 desktop on 64bit Slax. All bundled in 180MB. There are TONS of things to be improved, though.
No doubt this is only a raw sample , but Slax 7 simply must have a new wall paper to herald a new major version of slax.
I assumed this will put an end to speculation that slax is dead. It still maybe a long time to come , but the new version had started....and it's on the way....
jcsoh wrote:
No doubt this is only a raw sample , but Slax 7 simply must have a new wall paper to herald a new major version of slax.Nooo... The wallpaper is nice and why change a perfectly good concept?
Thanks for sharing this :)
I apologize in advance for asking this question: How did you pack KDE 4.7 into 180 MB?
You are amazing! I hope you will post an (like slax-6.1.2.iso, a
$ sed -i `slax-7`'s|alpha|beta|rc|preview|g'.iso
As you can see (if you look carefully) from the video (in previous post), there are 5 modules currently packed in the pre-alpha version of Slax 7:
1) core module (kernel, drivers, and essential linux apps and binaries) ... 55MB, like in Slax 6
2) xorg module (only X with required dependencies and fluxbox) ... 30MB, almost the same like in Slax 6
3) desktop-libs (that's QT libraries and dependencies, GTK libs are missing yet) ... 25MB
4) kde module (workspace, plasma and such, konsole) ... 35 MB
5) devel module (gcc compiler and such) ... 25MB
So KDE with X with QT and libs and dependencies is about 90MB. How is that possible? I simply recompiled QT and KDE base with the less possible dependencies. For example, there is no help, thus there is no dependency on some big XML libraries. There is no python dependencies, so no python needed. And so on...
Note that there are no apps yet, no utilities, and no office. I'm still trying to get all of these under 200MB in total download, however it seems impossible, so maybe Slax 7 will be like 220MB or even bigger. I'm also considering to include Chromium browser instead of firefox, it works nicely but it's about 50MB in size, so I'm not sure yet.
If you do include Koffice /Caldera (Is this their new name ?), I hope you will keep it in a separate module as for slax 6 . This allow those of us who are using Openoffice /Libreoffice to easily exclude Koffice/Caldera.
I am now wondering if the preview is 180 MB or 170 MB?
If it is 170 MB, then where did the other 10 MB go?
[olivares@quadcore ~]$ echo 55+30+25+35+25 | bc
170
Whichever the answer is, the results are EXCELLENT!!!
Good to see you well and Slaxing again. I am still using SLAX 6.1.2 ( I like KDE 3.5) and will continue to use it for some time to come. SLAX is my favorite Linux distro. I look forward to SLAX 7 as long as it is the same masterpiece SLAX 6 is. I am sure it will be.
Basically I don't like the new oxygen decorations, however that may change with time :)
The preview is based on Slackware 13.37 64bit, however KDE is 4.7 recompiled from sources.
I would like to put the ISO somewhere, but I'm waiting for Junjiro (aufs developer) for confirmation and possible fix of some bug I reported.
Old modules will rest in piece.
There is no way for new Slax to support those, I am sorry. No backward compatibility whatsoever.
Tomas M wrote:
Old modules will rest in peace.
There is no way for new Slax to support those, I am sorry. No backward compatibility whatsoever.
Don't worry about this Tomas! People are never happy and despite many efforts, they can't be pleased :( Do what you need to do :)
The decorations are just that decorations, and people can add to it whatever they want :) Just one question, the new module extension *.xzm would be preferred or will you go with *.lzm?
Tomas M wrote:
Old modules will rest in piece.
There is no way for new Slax to support those, I am sorry. No backward compatibility whatsoever.
I had assumed as much, I was more so hinting at this provides an opportunity to make changes in the module system and how they are presented online.
In particular, scripted checks of requirements to verify basic module quality.
Just a basic check for the existence of a build script should help with submissions.
Anyhow, most of my modules have build scripts, so updating the project version and wget url should be all that is required for a rebuild (same should be true for those who conformed to module reqs).
Also with this major version change, it would be nice to see a bug tracker eventually come into existence.
We have another question:
yous said that Slax 7 is based on Slackware 13.37 64 bit
could you tell us the name of package in Slackware DVD
that you had to include in this Slax version
if you use extra package out of Slackware DVD
please name it
Regarding the module system which is here online - I think that it has to be changed again.
There are several problems with it:
- source code is missing, which violates GNU GPL
- kernel specific modules do not work on newer Slax version (where new kernel is used)
- sometimes build scripts are missing
I am thinking about following approach:
- users would just upload the build scripts, no binaries
- automatic system can get the build scripts from other sources, like slackbuilds.org, to fill up the database from the beginning
- automatic system can build the modules itself!
This is quite exciting. Very stimulating. I am sure that many are eager to get into testing phase.
Tomas are you thinking to adopt or adapt some kind of package manager like slapt-get, sbopkg or slackyd for example?
---------------------------
I am thinking about following approach:
- users would just upload the build scripts, no binaries
- automatic system can get the build scripts from other sources, like slackbuilds.org, to fill up the database from the beginning
- automatic system can build the modules itself!
Not sure if this is going to happen though :)
---------------------------
I think this is a wise move. If properly managed, this system could ensure the reliability and security of the software that is made public.
There are other distributions that use automated building for packaging the software of their repositories. Slitaz, for example, needs only to be sent a "receipt" (it is a file with build instructions) and the server will get the source and build a package with it. Better yet: only authorized personnel is allowed to submit builds.
@hoanglong1712
I have an out of date list from looking at /var/log/packages on a previous version.
I would guess the used package list should be similar +-some. http://fundamental-code.com/slax/
@Tomas M
Even if only part of that plan is implemented, it should be good. :)
Tomas M wrote:
I am thinking about following approach:
- users would just upload the build scripts, no binaries
- automatic system can get the build scripts from other sources, like slackbuilds.org, to fill up the database from the beginning
- automatic system can build the modules itself!
I've been working on doing something like this for Porteus. It's still a work-in-progress, but some pieces are already working.
Will it be possible to convert existing lzm modules to new version using some command-line utility as lzm2xzm ? That will be really good since we will not need to download all modules again. Downloading itself is not so much of a problem, but lot of time is needed for finding dependencies.
Tomas M wrote:
Basically I don't like the new oxygen decorations, however that may change with time :)
The preview is based on Slackware 13.37 64bit, however KDE is 4.7 recompiled from sources.
I would like to put the ISO somewhere, but I'm waiting for Junjiro (aufs developer) for confirmation and possible fix of some bug I reported.
Old modules will rest in piece.
There is no way for new Slax to support those, I am sorry. No backward compatibility whatsoever.
@rnslax: Sorry for you.
The father of slax said:
"... Old modules will rest in piece. There is no way for new Slax to support those... "
However, it will surely be for the better, with an efficient package management system. We have been hoping for that a long time.
What @rnslax wanted is not for Tomas to maintain the existing module repository , but a tgz2xzm (or whatever extension given to the new module) to convert his existing modules (on his own hard disk etc).
Only Tomas can answer for sure , but I believe it is a simple matter for him to provide such a script.
In the transition from slax 5 mo to slax 6 lzm , we have mo2lzm , so there is a high probability such a tool will be provided.
I agree with jcsoh. I had earlier spent a lot of time in getting many modules to work in slax because of dependency problems. I was able to convert the whole set and use them in porteus in no time using their command "lzm2xzm ." (after cd to modules folder). I hope a similar command is there in slax7 so that the migration can be quicker.
Well conversion from old format to new one is pretty simple
- get old unsquashfs from Slax 6
- get new mksquashfs from Slax 7
- make a script which unsquashfs's lzm format and repackages it using new mksquashfs to slax 7 format
However I am not sure if the converted packages can even work on newer Slax version, there are a lot of changes in all the core libraries etc, many of the packages won't be usable imho. But the format in general can be converted.
I can see you already came up with a new module extension name xzm, interesting :) It seems xzm is not used by any other software, that is good news. However I'm not sure if we shouldn't switch back to .mo extension. It seems more user friendly to me :)
Bear in mind this is the latest module format which will never ever change again (IMHO), since it is in mainline kernel and there are no reasons whatsoever for it to change.
Or perhaps slax logo could change to a cow and modules could have .moo extension.
Just a joke ;-)
Tomas M wrote:
Well conversion from old format to new one is pretty simple
- get old unsquashfs from Slax 6
- get new mksquashfs from Slax 7
- make a script which unsquashfs's lzm format and repackages it using new mksquashfs to slax 7 format
However I am not sure if the converted packages can even work on newer Slax version, there are a lot of changes in all the core libraries etc, many of the packages won't be usable imho. But the format in general can be converted.
I can see you already came up with a new module extension name xzm, interesting :) It seems xzm is not used by any other software, that is good news. However I'm not sure if we shouldn't switch back to .mo extension. It seems more user friendly to me :)
Bear in mind this is the latest module format which will never ever change again (IMHO), since it is in mainline kernel and there are no reasons whatsoever for it to change.
Or perhaps slax logo could change to a cow and modules could have .moo extension.
Just a joke ;-)
:)
How many time for wait slax 7?!
We was waiting for more times, more then one year!
hoanglong1712 wrote:
Dear Tomas M
Thanks for your quick reply
We have another question:
yous said that Slax 7 is based on Slackware 13.37 64 bit
could you tell us the name of package in Slackware DVD
that you had to include in this Slax version
if you use extra package out of Slackware DVD
please name it
I think ,you may like this scripts and packages list to automatic build system. http://ithink.8866.org/smf/index.php/topic,393.0.html
The download link at bottom of top post!
A system build list, all packages name from the list file is all from slackware-current site!
to use this list , you need "pkglistmake" scripts (make system from a list file) and "pkgmake" (make a single package)
There's tools all build in iThinkX system, did you need it ?!
:)
Tomas M, I wish the slax can like this, and we don't need download full iso , we juse need download a base and use list file to make a full system by ourself.
I was asking about the conversion of old modules on Tomas' blog as well, but I figure with Slax7 it might be time to start from scratch with a proper module system and I like the slackbuilds concept.
1 thing ... i usualy used slax on sistems witch doesnt have a internet conection :) so... will i be able to useit as before from an usb stick ? i dont mind if is 4GB of size as long as it has video drivers , works with wine and has the Mplayer with the GUI interface :)
Thanks for everithing an im waiting/hoping to see the final release
@ AppleWolf
thanks !
it is a pity that I need few month to learn chinese before i could
follow your work there
i hope that I could jion your forum in the next 4 months
Tomas M wrote:...I can see you already came up with a new module extension name xzm, interesting :) It seems xzm is not used by any other software, that is good news. However I'm not sure if we shouldn't switch back to .mo extension. It seems more user friendly to me :)
Bear in mind this is the latest module format which will never ever change again (IMHO), since it is in mainline kernel and there are no reasons whatsoever for it to change.
You certainly remember our struggle concerning mo/lzmo/lzm approx. 4 years ago?
.mo ending was taken by compiled language (po) files then and is still...
Which file manager would be there in slax7? Apparently konqueror is not available in newer kde. I think konqueror is better than newer dolphin or nautilus of gnome desktop. The search or find file layout is much better in konqueror than in others. Since file manager is a key application for any system, it would be best if many file managers are there or installable so that each person can use whichever he/she prefers. But konqueror should be one of them. I would like to know what other feel on this aspect.
@fundamental: >> Apparently konqueror is not available in newer kde.
>I am still using it to browse files KDE 4.4.3
I could not install in the new kubuntu. It was not available in synaptic package manager and I could not download it fully from its site since there were so many dependencies. My experience was limited to this only. I am glad that it is available. Which distro you are using for KDE 4.4.3? Was it available with the distro or you installed it later?
I am currently using slackware 13.1.0 (one version old).
This was available with no extra work with the base system install.
Assuming it has not magically vanished in slackware 13.37 (current release), it will appear in slax.
Odd that you had issues with kubuntu, but they [ubuntu based distros] tend to mess with the vanilla source quite a bit.
Thomas, do you make 64bit version only?
What about older PC's or Atom processors with 32bit support only? Please make a 32bit version too, because I use it to diagnose or repair older PC's. Thanks!
fundamental wrote:
> Apparently konqueror is not available in newer kde.
I am still using it to browse files KDE 4.4.3
So do I. Guess on what distribution?
Personnally, I do not like kubuntu, too much problems. Mint is quite looking good with the gnome environment, better than ubuntu.
mint is as same as ubuntu
it requires more ram and chip than slackware to do the same job
if we need to do something that is complicated while not having
much resources just use slackware
Having the gnome environment does not necessarily means that slax7 will be sluggish. If Tomas intended to use it, I imagine that he will resort to simplicity and speed. gtk packages offer interesting advantages it seems. You could get konqueror in the gnome environment if you want. I do to prefer konqueror.
I was trying live CDs of other distros and found that most mounted their disks on /media/partition-name rather than on /mnt/sda2 etc. There seem to be some advantages of mounting with partition-name since it remains the same even if a partition is deleted or added. Also since mounting in media folder is there in most distros, same script files can be used everywhere. I wonder what would be the policy in slax7. Maybe the best method would be to mount on /media/partition-name with links named sda1 etc in /mnt folder.
Mike95 wrote:
If slax is built from a slackware 64-bit system. How can we that we have a 32-bit processor boot it? Can I still use slax?
Maybe 32bit version of Slax 7 will be available, I did not decide that yet.
I dream of a 32bit version of Slax and KDE 3.5.10 + latest kernel
Slax is the best just now he needs a new kernel
KDE 4.x is a useless quack and you need new habits.
64bit not now, because it lacks 64-bit applications.
Why use a 64bit system, since most applications it will be these 32-bit?
polonus wrote:
I dream of a 32bit version of Slax and KDE 3.5.10 + latest kernel
Slax is the best just now he needs a new kernel
KDE 4.x is a useless quack and you need new habits.
64bit not now, because it lacks 64-bit applications.
Why use a 64bit system, since most applications it will be these 32-bit?
Yours and sorry for my English:)
My guess is, is because most PC's are going 64-bit. Most programs being released nowadays are 64-bit native, and 32-bit adapted. I am quite annoyed because I am running a 64-bit laptop and a 32-bit desktop; and most of my programs are 64-bit but need the power of a desktop....
I just hope an adaption is made for 32-bit for Slax 7 :)
polonus wrote:
I dream of a 32bit version of Slax and KDE 3.5.10 + latest kernel
Slax is the best just now he needs a new kernel
KDE 4.x is a useless quack and you need new habits.
64bit not now, because it lacks 64-bit applications.
Why use a 64bit system, since most applications it will be these 32-bit?
Yours and sorry for my English:)
Hope after slax 7 release, some one will build trinty desktop for it.
if the new Slax 7 detects automatically the processor type and runs, the slax modules will run in EVERY computer!, but it -the slax system- size will be larger, about 300 Mib.
I agree with the above poster: The way I understand Slax's purpose is that it's supposed to be a portable distro for use on any computer one happens to stroll by, not a replacement for a native installation. Therefore, I think 32bit support is, at least for the next few years, imperative in order for Slax to fulfill its role as a live distro. Keeping it under 200MB, on the other hand, seems unnecessary nowadays, since flash drives are constantly getting cheaper and bigger, and I've never actually seen anyone use a burned 200MB CD. Maybe set the limit at 240MB, so it'll fit old 256MB flash drives?
I also think that the devel module should be optional, and that the dev team should maintain optional alternatives for the largest & most used packages, such as KDE/Gnome/Xfce, Chromium/Firefox, and KOffice/LibreOffice/OpenOffice, instead of just sticking with one default choice for each use case, and letting the users take care of the rest. That method could potentially reduce the size of the base distro, enable Slax to cover the needs of a larger user base, minimize compatibility problems due to rogue modules, and overall emphasize the advantages of Slax's modular approach.
As for the filename extension, I'd suggest something less cryptic and more descriptive than xzm, such as s7m (Slax 7 module)
Either way, I'm excited to see that the project is still / once again alive, and can't wait to try it!
I now use USB drives for live distros too but have frequently used 210MB CDRs. I like that I can keep a distro in my shirt pocket and carry it with me. Yes, flash drives are writeable but my Slax has the optional modules I need, is customized for my network and the library WiFi, and still fits on a small CDR. I would like to see a small version we can build on if we want flash or still use CDRs.
Like many folks, I'm really looking forward to a Slax 7 (32bit, if possible).
Limiting it to 200MB is/was a good idea. Keep it slim !
However, sometimes it's nice to be able load things like Libre Office without having to go through the long list of dependencies. I've tried it a few times and didn't have much luck with the larger modules needing more dependencies. So... if that issue was resolved, that would be great.
Also, Slax is great for running on older computers. Updating the kernel can/might mean a bit more speed, breathing new life into these machines. But many of these machines still have only 512MB of RAM, and so keeping Slax slim (and 32 bit) for that reason is a very good one.
Start by posting in the proper thread . If no suitable thread exist , then create a new thread.
Posting in a non related thread especially a sticky (which Tomas used to convey inportant message /topic relects a "I can't be couldn't care less attitude".
francois.e wrote:
@ vilain and others: For 32bit computers, the older versions of slax will still be available
What is wrong with them?There's nothing wrong with Slax6 per se, but it'd kind of defeat the purpose of a supposedly highly portable, low maintenance live distro if everyone had to maintain separate module collections and keep separate boot media just to be able to use what still makes up the majority of computers (especially in settings where one is most likely to need such a distro in the first place).
xcb567 wrote: jcsoh wrote:
No doubt this is only a raw sample , but Slax 7 simply must have a new wall paper to herald a new major version of slax.Nooo... The wallpaper is nice and why change a perfectly good concept?
...just put a big "7" centered on top of the map :)
@ vilain and others: For 32bit computers, the older versions of slax will still be available
What is wrong with them?
The main problem is slax 6.1.2 is getting old and user will start running into problem of missing /incompatible dependencies with newer version of programmes.
I know it's been a while since I've posted... but this is GREAT! I have been hoping so long for the day that Slax would finally get a version 7! From the video, this looks incredibly fast and a lightyear over 6.1.2! Looking thankfully and eagerly to the day Slax 7 is released!
I think slax should stay under 210 MB and that a 32 bit version should be available for Legacy Computers.
But, if Slax is only 64 bit, it will not matter much because almost all computers now are 64 bit.
Hi Thomas, In Short PLEASE Let FREE RANGE SLAX MODULES THRIVE.
about KDE and Slax 7...
I think a good idea for Slax and KDE would be to include no apps at all. The core (as in module) system is all anyone really needs anyway. A lot of silly KDE apps are pointless in linux. Except for multimedia works.
So you could just put a script that configures the app menu with whatever modules are included by the user on the cd. That would conserve the livecd footprint and make Slax even more user friendly from a customization point of view.
about Slax Modules as linux software distro...
I like the Slax modules being publicly traded. I think they should be in order to create a health system of software development. Everyday joe user sould be able to upload modules and be downloaded by everyday bill user. I am very impressed with slax modules. A Slax Module is - The Linux programs and the library files they need, wraped in a file system so that you can just mount and run it. That style of software installer is here to stay. Its not about being the best. Its about just another way to do it. Another is put the files in an archive, or make the binary portable.
"I think a good idea for Slax and KDE would be to include no apps at all. The core (as in module) system is all anyone really needs anyway."
The type of slax users /potential users varies from the totally clueless (linux /computerwise) to very experience and a balance need to be strike to accomodate them (unless there are various version of slax).
A new user would expect to boot up slax cd/usb and be able to do thing like reading a pdf file /text file , play music /movies , so a slax without any basic apps would seem like an unusable distro to them.
@Tomas M
1st - Thanks for your work on and with SLAX
2nd - SLAX release was delayed due to bug in aufs
3rd - What if create a "repository" for alternate software ie browser,koffice
as like modules page, and use internal browser konguerer to get extras
4th - I don't know how to say this right but, when you release the next SLAX
this forum is going to go krazy with questions
anyway just my 2 cents
hope it helps
Tomas M wrote: Mike95 wrote:
If slax is built from a slackware 64-bit system. How can we that we have a 32-bit processor boot it? Can I still use slax?
Maybe 32bit version of Slax 7 will be available, I did not decide that yet.
Please provide a 32bit and 64bit version! And keep up the good work!
For a "usable" KDE4 you will need over 500 MB. Without akonadi you will not have even a usable calender nor a regular mail client. All personal information manager related items must be left out and offer them as separated modules. But KDE4 is superb!
Please add a automatic dependency handling when downloading or activating the modules.
A simple script to estimate/display the size of all the dependencies(multi-drill-level) and download them all as one zip/tar file would be an awesome addition.
Also when building customized slax on your website, you can prompt and auto add all the dependencies to the selection.
I have many times lost the interest in dowloading each of the dependency and have given up downloading large modules. This feature would be a great addition and would increase the popularity of slax...
forum wrote: theROM wrote:
I believe that there should be a larger version with all the features of KDE4.
You wanne bloat Slax?
Slax's small size is one of it's strong points..
Actually, I have slax as my main Operating system, and if there was a seperate version with KDE4, it would become a good operating system to put on your Hard Disk.
Kubuntu Demonstrated this. 700MB with MANY features.
Slax IS what I think is the Best (KDE 3, NASM, GCC C++, Koffice, 200MB,etc.), but with KDE4, it could be more downloaded that Ubuntu.
Someone could have said me to go to porteus.org and get the new/updated version of slax branched project. But looks like the users who took it over and branched it to a new project are afraid to advertise as a new version... some possible code copying?
btw, i liked porteus cause i do not have to wait for one single person to answer my question in the forum, since there is a community.
Even if porteus is advanced.. i am not happy with either of the projects, slax or porteus.
Both do not have a public CVS/SVN and i do not think it is an open source project. may be i was not looking harder. would like to see a public source hosted.
The porteus "PPM" trys to do a better job to install dependencies. I still could not find many important modules required to run a basic OS out of the box and downloading modules is still a pain.
it may be just because i was using porteus 1.1 RC, will wait for the actual release.. hopefully should solve my problems with the new package manager.
fingers crossed.
Well Wisher wrote:
Please add a automatic dependency handling when downloading or activating the modules.
A simple script to estimate/display the size of all the dependencies(multi-drill-level) and download them all as one zip/tar file would be an awesome addition.
Also when building customized slax on your website, you can prompt and auto add all the dependencies to the selection.
I have many times lost the interest in dowloading each of the dependency and have given up downloading large modules. This feature would be a great addition and would increase the popularity of slax...
Someone could have said me to go to porteus.org and get the new/updated version of slax branched project. But looks like the users who took it over and branched it to a new project are afraid to advertise as a new version... some possible code copying?
It hasn't got anything to do with code copying.
It's out of respect for Tomas M. the creator of Slax and the linux live scripts.
Porteus started of as Slax Remix and with Tomas permission they have one thread for each release on Slax's forum.
Users are repeated reminded as to post only on that thread to avoid "misusing" slax's forum , but even than some users was unhappy and marked the thread as spam (so that it becomes invisble to uses).
Tomas created magic with slax. We are sure whatever he is doing now, he must be doing a magnificent job. It will be great if we can get a glimpse of his current area of work (website etc).
Hey! Guys
Will it have support for netbooks? Also, why don't you release two versions one with KDE4 and one with LXDE/Trinity or some other lightweight desktop. So that people can use it on old laptops and netbooks.
hoanglong1712 wrote:
mint is as same as ubuntu
it requires more ram and chip than slackware to do the same job
if we need to do something that is complicated while not having
much resources just use slackware
Mint is *not* the same as ubuntu. It is ubuntu based, but uses less ram and has more features.
It also looks and works a little more like windoze.
That is like saying Ubuntu is Debian. That is what it is based on, but the differences on
a standard install are pretty significant.
Just the next week after my post with Slax 7 preview, my business broke and I am constantly working on fixing my life situation. Don't expect any new version of Slax any soon, I am sorry :(
Tomas don't be sorry, you have nothing to be sorry for, OC you MUST fix any problems that you might get in life before anything PC related, after all a happy Tomas is a happy slax community in the long term, if you need help then don't forget to ask your most trusted friends and the wider community if they are in a position to make your life easier.
In spare time I am experimenting on the zlive branch, but the original Thomas's 6.3.0 release is there too, in the master branch.
About two year ago I found Thomas's scripts as a way to build a highly secure, stable and thin mini pc router. This toy, based on Gentoo Hardened, was just for myself.
Feeling the importance of Thomas's work, I started experimenting on his scripts.
I realized then that this code was in danger of disappearing from the Net and that testers and developers were required to share experience: so I asked Thomas and put everything on Sourceforge under GPL.
This are my priorities for these scripts:
1. Keep scripts as much as possible independent from host environment (the host should give us what we need)
2. The host distribution should not be modified (transparency)
3. Should work with any distro (portability)
3. Use new Kernel features and be easily customizable (no hard coded compression schemes, initrd/initramfs at user choice)
4. Keep it simple
Because my time is short (and that because I want my time to be short for you) I will take the time I want.
In the meantime feel free to do what you want (but remember GPL license limits).
I hope that someone will try and share their experience.
And finally, I hope that Thomas will soon solve his problems.
I've been releasing KIARA, (Kiara Is A Recursive Acronym), a remixed version of Slax, for about two and a half years now. I add packages ported from Slackware 12.2, including virtually all of KDE3, emacs, sudo, some development packages, etc, and few extra modules from Slax.org. The best part is that I use packages from mozilla.org to keep Firefox, Seamonkey, and Thunderbird completely current. I usually have a new version of KIARA uploaded to the server within 48 hours of each new Firefox release.
If you know anything about Slax, you know this isn't that hard to do. KIARA is not a great feat of engineering. However, it is a great live CD. Adding the latest versions of Firefox makes KDE3 seem new all over again. The web has changed a lot in the past few years, but text editing is still text editing.
It's also the greatest hobby an aging bachelor could want. KIARA has been downloaded hundreds of times all over the world. One guy likes it so much he gave me a laptop so that I could work on getting it to support wireless better. (Verswion 2.8, released yesterday, may do the trick!)
It looks like Slax and KIARA will have to part company soon. A lot of my users are diehard KDE3 fanboys, and I don't have a single 64 bit machine. So the time has come to take it further. What I'd like is something that uses KDE3, and is based on Slackware 13.37, which stll runs KDE3 rather nicely, by the way.
I'd want it to support the latest google chrome (or maybe chromium). Chrome now syncs a user's settings and plugins automatically via a google account. This is HUGE advantage for a live CD. I also want to support the google talk-plugin, WICD. I've had no luck gettng these things running in Slax.
WICD which have not been running well in Slax, If it's possible, I'd like to have the symbolic links that I've been adding with a startup script in KDE built in, or maybe added in a bash script that doesn't require KDE. I'd also like to be able to use zsh instead of BASH. I've had problems.
I'd like it to be simple, like Slax, not convoluted like Porteus. Not that there's anything wrong with that.
I have a lot to learn before I can do this, so it's comforting to know what someone else is working on those scripts. They are hugely important. In my opinion, one of the reasons why Slackware matters is that the simple architecture seems to lend itself to some truly interesting and original second generation distros. Slax is not only among the most interesting of those distros, it's also facilitated a lot of that creativity, via the linux-live scripts. It's the basis of the Vector Linux live CDs, and heaven knows what else.
We should wait patiently for a new Slax, but if Tomas is too personally occupied to maintain those scripts, someone else should take over. Thanks again, Andrea.
Hello I apologize in advance if there are spelling mistakes because I use google translator. I am from Bulgaria and english not understand so please tell me how resources requires OS Slax (RAM, Hard, etc.) because the site is not anywhere wrote. please answer me thank you in advance emo887@abv.bg
Your question is not related to this thread. In the future please a new thread and don't abuse a sticky.
Look in your slax iso/tar. There is a text file specifying slax's requirements.
Thou are most wise.
I repent.
Truly those "unregistered" souls cannot make new thread for "salvation".
But if they seek , they can still post to existing thread, but the search can be long and hard
So repent and register.
Then the path of slax is open to thee.
I'm rather sad Slax 7 won't be released any time soon (it has been so long since the 6.1.2 release) but I understand and really hope that everything goes well for it's author, to whom we're all thankful for the diligent work up to release 6.1.2 and the technology preview.
Please start the network drive feature again.
Replace firefox with opera mini (the latest one)
Limit konqueror as file manager and webbrowser ony removing its embedded capability of opening other applications(its basically irritating)
Include wine as built in package
Hello Nickson
It was amazing solution. I was wondering that how to develop the Slax Program over the Linux so that it would be more compatible to develop amazing program in that. I mean inside the System. Is there any tool?
Thanks for Slax, your time and hard work is appreciated. I also look forward to the future release. To quote an old saying "Life is what happens when you make other plans" Best of luck to you and I hope everything comes together for you that way that you want.
I think slax should stay under 210 MB and that a 32 bit version should be available for Legacy Computers.
But, if Slax is only 64 bit, it will not matter much because almost all computers now are 64 bit. Auto MD
210MB is the magic number for those mini-cds that fit in your pocket which is why I think they decided to make it squeeze on that. Those CDs have been around a lot longer than bootable flash drives.
If KDE 4 is very large and takes up much more space, why not Trinity Desktop which emulates the old KDE 3? I think this project has a future for computers with limited resources.
"The deal has been SIGNED yesterday.
I'm officially working on Slax since today.
The plan is to update and release new Slax version in 4 months.
I will need some beta testers, I'll make a signup form for you some time soon (there's nothing to test yet, though).
