SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by Ilgar Pat (single-handedly) managed to keep his distro alive more than any other one. I don't think that he will kill Slack by making an obvious mistake. He's not the one that goes fastest; but clearly he knows how to drive safe .
yes and it being the oldest Distribution, Tells me it has a far stabler future, I did find out, SuSe was a throw off from Slackware too.
Originally posted by BenneJezzerette yes and it being the oldest Distribution, Tells me it has a far stabler future, I did find out, SuSe was a throw off from Slackware too.
How odd ...
They have RPM, they've use SysV inits for ages, ... :)
Originally posted by BenneJezzerette yes and it being the oldest Distribution, Tells me it has a far stabler future, I did find out, SuSe was a throw off from Slackware too.
From what i've heard about SuSe (never used it myself) that's one hell of a split. Like when South America and Africa split.
Just what happened to Solaris, started using BSD and then changed to InitV, or so I heard. Which bring me to the point.
Considering this thread about innovation and stuff, I have a question, and this is the single point that had driven me away from Slack into BSD territory, but always looking back.
If Slack is so alike to BSD, meaning it uses the same init system and users from both systems feel at home almost right away. How come there is not (that I know of, yet again I have been away from UNIX for a while) a system similar to the BSD port system? would that be difficult to accomplish? is there one already? if so, how mature it is in its development? I heard of emerde, but I am not so thrilled about it.
I do believe that a Port system a la BSD would harm no one.
Last edited by blood_omen; 05-31-2005 at 03:18 AM.
To be honest, i don't really care if Slack is the oldest or newest distro.. What i care about is that
it has an excellent community
it's frequently updated (core-wise), either officially, or unofficially
it's stable and easy to understand.
it's actually easy to maintain.
As a linux user, i don't expect everything to work 100% after installation, and i expect anyone who uses linux to learn the basics, similar to learning the basics in driving a car or using Windows (how to install a program/driver, how to change resolution, how to search for a file, etc...). Such basics as how to use the CLI, how to edit a file, how to bring up a network or load a module. And moving on to installing drivers, recompiling the kernel, etc...
As a slackware user, i'm expected to know a bit more about how linux operates, and how Slack works.. Seing as slackware isn't the easiest distro to use in terms of a GUI installer, immediate GUI inetrface and reliance on the mouse only... (eg, xandros, mandrake, etc..). It is, however, easy in terms of bringing a machine up, working, and keeping it up in a short ammount of time.
Keeping that in mind, and keeping in mind how easy it is to upgrade packages and edit config files, i don't mind downloading some from LP.net or manually compiling apps to keep my system up to date, when Pat's a bit late in providing the updates...
The unofficial updates work very well, the manual compilation has never been easier with all the vanilla work and good core. I have the latest kernel up and running, along with (more or less) everything else upgraded. It's second nature to me to manually do a few things here and there.. That's how i see myself in being a Slack user.. Otherwise, if i couldn't be bothered, i would have chosen Mandrake or any other distro that does the work for me.
Am i doing too much work in maintanance and updating when i shouldn't be in the first place? Maby.. But i'm the one who'se learning in the end.. For that i'm grateful. Back in the old days with Mandrake, if something broke, then that;s it.. I wouldnt know wtf to do, relied on others to come and fix it, and hope it doesn't muck up again...
Slack makes you work a bit, but teaches you a hell of alot.. Try not to say its out of date by looking at the fact that Slack still uses older versions of Kernel, Apache, etc... But look at the fact that upgrading to the latest bleeding edge is very easy. IMO easier than any other distro i've tried. And if you expect others (like pat) to do it for you, then maby you need another distro
Just my two cents..
Edit: heck, i've never thought i'd be able to, but i've even made the move to Solaris, and it was very easy coz of my prior knowledge of slackware =)
Slackware is maintained, to me, much better than any of the other distributions. Not tossed out and then you have to be a total programmer to make it work. Yes you do need to have a "Hands On" mindset to use it, otherwise why use it??? As for the Oldest, and slpit off to SuSe at one time, these were taken from The Linux Bible 2005", yet it has Slackware 10.0 in it, Knoppix 3.6 and some older Distributions, for a 2005 book, sometimes the writer is just days ahead of the next release. It does have Sarge in it, and FC3, but over all it's a great read and referance for learning Linux in General.
From what i've heard about SuSe (never used it myself) that's one hell of a split. Like when South America and Africa split.
SuSe was born when a few german developpers looked at RedHat, didn't like the bloat, but decided they liked RPM. Then they looked at Slackware, decided they liked the stability, but wanted a package tool that supported dependancies. So they ported RPM to Slackware, and SuSe was born.
... going back a page...
Quote:
Here is an overview of new features in apache 2.0 link. On that list is not much that will make your site all of a sudden whiz bang full of features just for having 2.0.
On that list is one very important feature for any server: POSIX threading. It won't necessarily improve speed, but it will improve stability across the board, particularly when mixed with some of the features in the 2.6 kernel. On a Pentium 4 that supports Hyperthreading, or on an Opteron or DualCore Athlon64, it will give an enormous performance boost.
That said, I still want Slackware to run on my desktop and my laptop. One has an AthlonM, the other has an AthlonXP. I have absolutely no intention of upgrading either of them, and so a Slack that's optimized for my server environment simply isn't needed. 32-bit code will run on a 64-bit processor, and there's nothing to stop me from compiling my own when installing on a 64-bit system. (indeed, that's exactly what I did when I set up my new server yesterday)
If it's any consolation...I'm using 2.6.11.11 no problem w/ Slack Current and Dropline-Gnome 2.10.1. I don't see what I'm missing (maybe I just don't do enough yet...)
Originally posted by DreameR-X
If it's any consolation...I'm using 2.6.11.11 no problem w/ Slack Current and Dropline-Gnome 2.10.1. I don't see what I'm missing (maybe I just don't do enough yet...)
That last "11" makes alot of difference - everybody else tripped over the rocks so you didn't have to.
I run various 2.6.11 kernels, from "dot six" onwards - they're all pretty stable. Wasn't always so.
Now that the bitkeeper fiasco has died down the candidate levels for 2.6.12 are rolling again - but obviously that's of no interest to the members of this forum ...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.