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.
Everything is proved as working on the hardware available to us before it hits the current branch. From there we rely on reports from users that often use current on a daily basis. Current really is the testing phase for any release.
I personally find that the people putting things together are probably the worst test case for any product especially something as complex as a Linux distribution.
While we do check everything thoroughly there is bound to be some corner case or someone using something in an unexpected fashion that will cause a degree of breakage.
The hardware we have at our disposal is also limited so putting it "out there" is the best test it can have.
Hard to say it any better than Goblin here, so there's no much need for any of the rest of us to comment ;-)
However, I do want to reiterate the idea that the -current tree *needs* testing and feedback in order to ensure that the stable release derived from it is as reliable as what we've come to expect from Slackware. As I said before, nobody's perfect, and no, we don't expect everyone to dedicate a separate box to running the -current tree, but it's quite aggravating to have a barrage of minor bugs reported right around the time a release candidate is announced (or even worse, after it goes out as a -stable release).
then if we have An old P2 500mhz, 256mb RAM and 1Mhz internet speed
how many user can connect to this server ???
and what will happen if we used Debian or FreeBsd
then if we have An old P2 500mhz, 256mb RAM and 1Mhz internet speed
how many user can connect to this server ???
and what will happen if we used Debian or FreeBsd
Can you tell me how long it will take me to drive from here to the town hall if I tell you what sort of car I have?
Don't mean to be sarcastic here but it is an example of a question that has so many varibles it has no real answer.
then if we have An old P2 500mhz, 256mb RAM and 1Mhz internet speed
how many user can connect to this server ???
and what will happen if we used Debian or FreeBsd
-1. Because interenet connection speed isn't measured in Mhz, and you didn't say which server (http/mail/ftp?).
Seriously, it is impossible to tell. You easily can have content which will eat ALL your bandwidth even with one user. It depends on content, server software, type of server, etc. Launch server and see yourself.
ahmed gamal's question has no relation to this topic so please do not follow up on it here. Ahmed if you want to discuss the use of Slackware as a server please open your own thread.
ahmed gamal's question has no relation to this topic so please do not follow up on it here. Ahmed if you want to discuss the use of Slackware as a server please open your own thread.
No need to be sorry - your question is good, but it does not belong in this thread. If you want to ask random questions, perhaps you should visit the Slackware IRC channels and have a chat there.
And now, back to the original topic, already in progess...
Quote:
Originally Posted by rworkman
Theoretically, everything in our repository is tested for proper function by the submitter, and proper packaging by the approver (the SBo admin), and we (speaking for SlackBuilds.org) often test for proper function too if it's within our expertise to do so (but lots of things simply aren't
In that case, I will thoroughly test the few packages I plan to build scripts for, BEFORE submitting them, since they will be my first. Shorewall will be the first. I might PM you on that one when it's ready, to make sure I got everything right.
Quote:
Originally Posted by rworkman
However, I do want to reiterate the idea that the -current tree *needs* testing and feedback in order to ensure that the stable release derived from it is as reliable as what we've come to expect from Slackware.
I have an extra box or two in the lab I can use to play with -current. I'll put it on one of my laptops too (this one in front of the tv for news and such).
Quote:
Originally Posted by yasker
Wich version of slackware would you recommend for producition use?
A perfectly valid question for this thread, I'm curious to see the recommendation too. As an adventurer in heart, I'll start with 12.2. If anything proves to be a major problem, then I'll reconsider an older version, if recommended.
A perfectly valid question for this thread, I'm curious to see the recommendation too. As an adventurer in heart, I'll start with 12.2. If anything proves to be a major problem, then I'll reconsider an older version, if recommended.
I've found Slackware 12.2 to be very stable and it runs very well on my Plll 667 MHz, my Celeron 850 MHz, and my Pentium D 2.8 GHz. Interestingly, the newer kernel plays better with my oldest Slackware box. I'm certain you will like 12.2.
In that case, I will thoroughly test the few packages I plan to build scripts for, BEFORE submitting them, since they will be my first. Shorewall will be the first. I might PM you on that one when it's ready, to make sure I got everything right.
Sure; you can email me directly if you'd like: rworkman at slackware.com
Quote:
I have an extra box or two in the lab I can use to play with -current. I'll put it on one of my laptops too (this one in front of the tv for news and such).
Good to hear. Another tester with experience and expertise is always good. :-)
Quote:
As an adventurer in heart, I'll start with 12.2. If anything proves to be a major problem, then I'll reconsider an older version, if recommended.
Unless you're trying to run on *really* old hardware, there's almost never a good reason to stay with an older version unless it's already installed, in which case, there just might not be a good reason to upgrade :-)
Personally, I have found Slackware to be /the/ most stable Linux distribution out there, period. And I have tried quite a few over the years. Slackware's stability is enhanced, IMHO, by the tendency to stick with vanilla sources and the desire to keep things simple -- and by simple, I mean simple in a 'traditional-unixy-command-line-all-config-files-no-guis' kind of way. IMHO, the number of patches applied to the kernel and other upstream projects by other distributions only introduces more variables and more chances for bugs.
Thanks, will do. btw I like your politics page I agree. They ain't getting my sig sauer's
Quote:
Originally Posted by chess
-- and by simple, I mean simple in a 'traditional-unixy-command-line-all-config-files-no-guis' kind of way.
So, are you saying that people who use gui's to administer a server are fricking lame dorky ig'nant LOSERS who suck like nobody has sucked before? I agree. All my servers are headless, no gui's ever. ssh into it to makes changes and check things out. Don't need no stinkin VNC. Webmin is okay, it has some uses (I won't give managers a shell account, but will give them limited webmin access).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.