5 Linux Distros You Should Watch Out For in 2013
|
|
|
Comments (42)
22 earlier comments in the full thread.
Compiling everything on the local machine sounds good in theory, but I can't stand it.
You should avoid distros that compile on the local machine then. Stay away from the likes of Gentoo, for instance. ;-)
Oh don't be so hard on the old gal...
Caitlyn's just got her knickers all bunched up in a knot over Slackware because of the egg left on her face when an old decrepit webserver went offline, she had a panic attack, and reaped the flaming wrath of hundreds of users across the Internet for being so naive about it.
Don't pay her any mind, she's learned her lesson and will either calm down eventually, or succumb to hypertension.
She's really a good egg otherwise, even though she drank the ewboontew kool-aid.
I hope that helps :)
Caitlyn's just got her knickers all bunched up in a knot over Slackware because of the egg left on her face when an old decrepit webserver went offline, she had a panic attack, and reaped the flaming wrath of hundreds of users across the Internet for being so naive about it.
Don't pay her any mind, she's learned her lesson and will either calm down eventually, or succumb to hypertension.
She's really a good egg otherwise, even though she drank the ewboontew kool-aid.
I hope that helps :)
> ...even though she drank the ewboontew kool-aid.
Caitlyn is a consultant who supports Linux (and whatever else the job requires) for a living. Slackware out of the box doesn't meet her clients' needs, and she can't make it do so with what she considers a reasonable amount of effort. I agree with her that there are other distros that do a better job of meeting her needs in that regard.
Her only mistake (if you want to call it that) is in generalizing that to saying it is therefore unsuitable for most people. That's a step that involves several unproven assumptions (which doesn't mean she isn't correct, merely that it's unproven). Slackware does meet the needs of a (in modern Linux terms) a relatively small number of people (of which I'm one), and she admits that.
She is not, and never particularly has been an Ubuntu devotee.
Caitlyn is a consultant who supports Linux (and whatever else the job requires) for a living. Slackware out of the box doesn't meet her clients' needs, and she can't make it do so with what she considers a reasonable amount of effort. I agree with her that there are other distros that do a better job of meeting her needs in that regard.
Her only mistake (if you want to call it that) is in generalizing that to saying it is therefore unsuitable for most people. That's a step that involves several unproven assumptions (which doesn't mean she isn't correct, merely that it's unproven). Slackware does meet the needs of a (in modern Linux terms) a relatively small number of people (of which I'm one), and she admits that.
She is not, and never particularly has been an Ubuntu devotee.
Wasn't caitlyn once a slackware fan? Wasn't she going to create a distro based on slackware, but changed her mind? When was that?
I didn't get the entire story, jes the part about her now being heavily involved in some linux distro that seems to exist nowhere except in her resume. ;)
I didn't get the entire story, jes the part about her now being heavily involved in some linux distro that seems to exist nowhere except in her resume. ;)
what. this thread needs is more gasoline. The flames don't burn hot enough.
In my everyday work, I have to handle the "usual suspects" of distributions: I did some training on Oracle Linux for the company that builds the motorways in South France, I've used a fair share of RHEL and CentOS for clients, I care of a handful of public servers running Debian. Like my latin teacher once pointed out: there's no "best" latin grammar. The "best" latin grammar is the one you're most comfortable with. It just so happens that I'm most comfortable with Slackware, because it was my first distribution back in 2001. Now I may not be as proficient as some others who have used Slackware since 1789, but so far, I've setup middle-sized networks for 50 to 100 users around, 100% Slackware on both servers and desktops, and, well, no complaints so far. Just works(tm). And since this is the base of my company's products, I went so far as to voice my opinion (watch out for Slackware) since it's one of the rare distros which focuses on values like perennity and stability while keeping a human size. I also value it for its flexibility, since unlike many other distributions: 1) the installer never chokes on anything 2) it installs on any kind of low-spec hardware 3) it doesn't make me jump through burning loops whenever I need a particular kind of software in some particular version. So many reasons to say "it's great, watch out for it". But posting it here makes me feel a bit like walking into the "Café de l'Olympique de Marseille" (headquarters of the eponymous football team here) and suggesting that the PSG (Paris Saint-Germain) is a gifted team. Wrong place, wrong time. My bad.
Oooh looky, personal attacks. If you can't attack the message the go after the messenger.
Yes, I used to be a Slackware fan, or more precisely, a fan of Slackware derivatives which added the missing pieces. I always considered Slackware to be a good basis on which to build a distro. @tallship is referring to the fact that Slackware's website went offine for a couple of weeks. It was reported in the Linux press, including LXer.com, with suggestions that the distro was in financial trouble. I wasn't the one who started that story or wrote the original article. I did comment on DistroWatch that the little private distro I was part of (used in small businesses by several consultants but NOT released to the general public) was going to rebase off of Slackware. The Slackware community, including Mr. Tallship, or so it seems, went absolutely nuts about my comments.
Sorry, tallship, there is no egg on my face. My comments were aprospos to the situation at the time. It's insane to base anything used in business on a small distro with a small development team and absolutely no transparency. That incident was instructive. Up until that point I thought that, aside from a few loudmouths the Slackware community was mostly helpful and friendly. That indicdent taught me that the Slackware community is almost as toxic as the Puppy Linux community. True, I didn't receive any death threats, but the abuse and the fact that you are continuing it all this time later proves that I should warn people away from Slackware for just that reason: the community is absolutely intolerant of criticism. Let me add an old Yiddish saying:" A fish rots from the head." In this case I learned the intoerance comes from the developer community on down.
You know why we kept Yarok private? We just don't want to deal with the community that would likely develop. I doubt now it will ever be released to the public.
My main objection to Slackware in business remains 1) lack of commercial support and 2) lack of modern security tools. Nothing more, nothing less.
My objection to kikinovak's original post wasn't a critique of Slackware per se, but rather that it really does not belong in a list of up and coming distros. Red Hat doesn't belong in such a list either. Neither does SUSE. They aren't new and don't need to be watched for something revolutionary. They will continue to advance and progress, but in an evolutionary way.
Yes, I used to be a Slackware fan, or more precisely, a fan of Slackware derivatives which added the missing pieces. I always considered Slackware to be a good basis on which to build a distro. @tallship is referring to the fact that Slackware's website went offine for a couple of weeks. It was reported in the Linux press, including LXer.com, with suggestions that the distro was in financial trouble. I wasn't the one who started that story or wrote the original article. I did comment on DistroWatch that the little private distro I was part of (used in small businesses by several consultants but NOT released to the general public) was going to rebase off of Slackware. The Slackware community, including Mr. Tallship, or so it seems, went absolutely nuts about my comments.
Sorry, tallship, there is no egg on my face. My comments were aprospos to the situation at the time. It's insane to base anything used in business on a small distro with a small development team and absolutely no transparency. That incident was instructive. Up until that point I thought that, aside from a few loudmouths the Slackware community was mostly helpful and friendly. That indicdent taught me that the Slackware community is almost as toxic as the Puppy Linux community. True, I didn't receive any death threats, but the abuse and the fact that you are continuing it all this time later proves that I should warn people away from Slackware for just that reason: the community is absolutely intolerant of criticism. Let me add an old Yiddish saying:" A fish rots from the head." In this case I learned the intoerance comes from the developer community on down.
You know why we kept Yarok private? We just don't want to deal with the community that would likely develop. I doubt now it will ever be released to the public.
My main objection to Slackware in business remains 1) lack of commercial support and 2) lack of modern security tools. Nothing more, nothing less.
My objection to kikinovak's original post wasn't a critique of Slackware per se, but rather that it really does not belong in a list of up and coming distros. Red Hat doesn't belong in such a list either. Neither does SUSE. They aren't new and don't need to be watched for something revolutionary. They will continue to advance and progress, but in an evolutionary way.
> That indicdent taught me that the Slackware community is almost as toxic as the Puppy Linux community. True, I didn't receive any death threats,
Then it can hardly be consider almost as toxic, now can it? There's a lot of room between even personal attacks and death threats. I think you owe the Slackware community an apology for that comparison, Caitlyn.
Then it can hardly be consider almost as toxic, now can it? There's a lot of room between even personal attacks and death threats. I think you owe the Slackware community an apology for that comparison, Caitlyn.
[quote="cailyn"]Oooh looky, personal attacks[/quotes]
Ooooh looky, self flattery.
Ooooh looky, self flattery.
@jdixon: No, I don't owe the Slackware community anything. The e-mail and web based attacks I've had for months now do rival the Puppy Linux community for venom with the exception of that one death threat on DistroWatch. They far exceed the Puppy Linux community in sheer volume. If anything, I'm being restrained in my criticism. You'd really not like it if I said what I really think.
> They far exceed the Puppy Linux community in sheer volume.
That's undoubtedly a factor of the size of the respective communities. While small my Red Hat standards, Slackware still has a reasonable following. They're also loyal to a fault.
> If anything, I'm being restrained in my criticism. You'd really not like it if I said what I really think.
Probably not. But then I'm not the one comparing email flames to a death threat, so what do I know?
That's undoubtedly a factor of the size of the respective communities. While small my Red Hat standards, Slackware still has a reasonable following. They're also loyal to a fault.
> If anything, I'm being restrained in my criticism. You'd really not like it if I said what I really think.
Probably not. But then I'm not the one comparing email flames to a death threat, so what do I know?
E-mail flames or public posts questioning my qualifications, my intelligence, my sanity, and several other things? Yeah... it's not worth mentioning, is it. Your "to a fault" bit is spot on. Religious zealotry over a piece of software I don't need.... ever.
> Your "to a fault" bit is spot on.
Of course. That's why I said it. Everyone and every group has faults.
Except for Dino, of course. :) But he's the exception which proves the rule.
Of course. That's why I said it. Everyone and every group has faults.
Except for Dino, of course. :) But he's the exception which proves the rule.
I think it is abundantly clear that Caitlyn will always actively discourage people from using Slackware based on her own opinions of it. While I do not agree with her attitude (she seems to think her opinions are somehow more worthy than others' opinions, though the same can definitely be said of many in and out of the Slackware community as well), she does have a right to dislike Slackware. Aside from her crude hyperbole that Slackware is stuck in the 90's, she hasn't said anything that isn't true here and does not merit some of the responses she has received. I think many of the arguments in the past were rooted in factual inaccuracies or half-truths, which evoked anger from those that were concerned that Slackware was being wrongly portrayed to those that may not know it intimately. Slackware does not have a huge market and in order for it to continue to exist, people need to keep using it -- I think this is the primary source of (frustration? fear?) from current Slackers that fear that not just the negative press, but the negative spin put on that press may threaten its existence. I think Caitlyn fails to understand the root of the problem and I think the community is not particularly good at addressing it.
While Caitlyn clearly wishes to denounce the Slackware community as being wholly abusive, unhelpful, and overzealous, I think it is unscrupulous to let personal tiffs get in the way of truths. I think you'll find that the Slackware community -- or at least LQ -- embraces newcomers that seek help or advice rather than starting off by insulting or making arbitrary distro comparisons. I can think of a lot of other communities that are actively hostile towards newbies, even if those newbies are not hostile themselves. I've seen many newcomers come to LQ that seem to be actively hostile (and I wonder why they come there in the first place) -- they maintain their own opinions of what a Linux distro should be, which does not align with what Slackware is, and then criticize Slackware or advise ways of making Slackware fit their needs rather than the needs of people who are already using it (and liking it). Obviously, these devolve quickly into flamewars. However, when a newbie requests help getting started with Slackware, wants to know what Slackware is about, or is looking to solve a problem with their Slackware installation, while maintaining a respectful attitude, they will almost certainly be welcomed kindly and given plenty of help. If you put respect in, your get respect out. If you throw hostility out, you're going to get it back.
While Caitlyn clearly wishes to denounce the Slackware community as being wholly abusive, unhelpful, and overzealous, I think it is unscrupulous to let personal tiffs get in the way of truths. I think you'll find that the Slackware community -- or at least LQ -- embraces newcomers that seek help or advice rather than starting off by insulting or making arbitrary distro comparisons. I can think of a lot of other communities that are actively hostile towards newbies, even if those newbies are not hostile themselves. I've seen many newcomers come to LQ that seem to be actively hostile (and I wonder why they come there in the first place) -- they maintain their own opinions of what a Linux distro should be, which does not align with what Slackware is, and then criticize Slackware or advise ways of making Slackware fit their needs rather than the needs of people who are already using it (and liking it). Obviously, these devolve quickly into flamewars. However, when a newbie requests help getting started with Slackware, wants to know what Slackware is about, or is looking to solve a problem with their Slackware installation, while maintaining a respectful attitude, they will almost certainly be welcomed kindly and given plenty of help. If you put respect in, your get respect out. If you throw hostility out, you're going to get it back.
@T3slider: More mud slinging. Are you trying to prove my point? The reviews that irked the Slackware community were written for O'Reilly and DistroWatch respectively where most of my audience would never have tried Slackware before. The purpose of the reviews wasn't to discourage anyone. The purpose was to let people know both the pros and cons and that included the ways in which Slackware 1) isn't like more popular distros and 2) requires a steeper learning curve for newcomers. That means I have to compare it to other distros. The purpose was never to discourage anyone or anything... until today. Today was they day I became totally fed up with the obnoxiousness of the Slackware community.
I think Slackers shouldn't let their blind fanboy biases decide that I am off on some sort of tiff. I also don't think the Slackware community is wholly abusive, unhelpful or overzealous to everyone, just to anyone who dares criticize their holy writ, which says their distro is unquestionably perfect and any criticism is unjustified and clearly due to a failure of the critic. Oh, and yeah, I don't think anyone should ever be subject to that sort of abuse.
I think Slackers shouldn't let their blind fanboy biases decide that I am off on some sort of tiff. I also don't think the Slackware community is wholly abusive, unhelpful or overzealous to everyone, just to anyone who dares criticize their holy writ, which says their distro is unquestionably perfect and any criticism is unjustified and clearly due to a failure of the critic. Oh, and yeah, I don't think anyone should ever be subject to that sort of abuse.
Woah...I don't know if you read what I wrote or what you wanted me to write but I certainly meant no disrespect. I was riding the middle on this one, defending you and the Slackware community in one breath while pointing out problems with both...I don't know how that can be considered mud slinging. I was trying to intentionally be mild...I agree with most of what you said in this thread and said as much. If you still saw what you did in that post then I don't know what to say except to apologize.
>The purpose was never to discourage anyone or anything
>It's not a distribution I can recommend to most Linux users and it is one that I would actively discourage newcomers to Linux from trying unless they really and truly know what they are getting into.
>I also don't think the Slackware community is wholly abusive, unhelpful or overzealous to everyone, just to anyone who dares criticize their holy writ, which says their distro is unquestionably perfect and any criticism is unjustified and clearly due to a failure of the critic.
I have to assume I'm included in that description, but I think your automatic jump to zealotry (which seems to happen every time) is unfounded. I don't think Slackware is perfect and I have said this before. If you point out legitimate problems with Slackware, I will agree with them. Your point about SELinux/AppArmor was fair. I mentioned grsecurity as a potential replacement but acknowledged that it isn't a perfect replacement. Slackware's lack of PAM, while keeping things simple, also makes LDAP setups prohibitively difficult. These are legitimate, rational points against Slackware which, if important to a potential user, could make Slackware a less-than-ideal distro. Neither I nor any other rational person could suggest otherwise. Thus, I have just admitted that Slackware has serious flaws. I could similarly name flaws in every other distro, and choosing one requires a balancing of pros and cons. My *opinion* is that Slackware fulfills my needs adequately, while acknowledging that it may not fulfill others' needs. Nowhere have I said that Slackware is the 'best' distro or that it is beyond critique.
What I thought was a fairly middling post apparently evoked a very negative and unexpected reaction so I suppose I must stop talking. You definitely read much more of a negative tone to my post than was written or intended. For the record there is absolutely no ill will in this post either so if you manage to read any...then either your reading comprehension or my writing skills are in need of improvement.
(Note: the use of the word 'tiff' in the previous post was meant to imply personal altercations, ie. rare personalized experiences/events that may not reflect the whole of the Slackware community or you in general; I did not mean to imply a 'fit of anger', a personal vendetta, or some other similar definition that would imply you were 'out to get' the community. Perhaps another word would have been more appropriate.)
>The purpose was never to discourage anyone or anything
>It's not a distribution I can recommend to most Linux users and it is one that I would actively discourage newcomers to Linux from trying unless they really and truly know what they are getting into.
>I also don't think the Slackware community is wholly abusive, unhelpful or overzealous to everyone, just to anyone who dares criticize their holy writ, which says their distro is unquestionably perfect and any criticism is unjustified and clearly due to a failure of the critic.
I have to assume I'm included in that description, but I think your automatic jump to zealotry (which seems to happen every time) is unfounded. I don't think Slackware is perfect and I have said this before. If you point out legitimate problems with Slackware, I will agree with them. Your point about SELinux/AppArmor was fair. I mentioned grsecurity as a potential replacement but acknowledged that it isn't a perfect replacement. Slackware's lack of PAM, while keeping things simple, also makes LDAP setups prohibitively difficult. These are legitimate, rational points against Slackware which, if important to a potential user, could make Slackware a less-than-ideal distro. Neither I nor any other rational person could suggest otherwise. Thus, I have just admitted that Slackware has serious flaws. I could similarly name flaws in every other distro, and choosing one requires a balancing of pros and cons. My *opinion* is that Slackware fulfills my needs adequately, while acknowledging that it may not fulfill others' needs. Nowhere have I said that Slackware is the 'best' distro or that it is beyond critique.
What I thought was a fairly middling post apparently evoked a very negative and unexpected reaction so I suppose I must stop talking. You definitely read much more of a negative tone to my post than was written or intended. For the record there is absolutely no ill will in this post either so if you manage to read any...then either your reading comprehension or my writing skills are in need of improvement.
(Note: the use of the word 'tiff' in the previous post was meant to imply personal altercations, ie. rare personalized experiences/events that may not reflect the whole of the Slackware community or you in general; I did not mean to imply a 'fit of anger', a personal vendetta, or some other similar definition that would imply you were 'out to get' the community. Perhaps another word would have been more appropriate.)
The point is often made that Slackware is an "amateur" distro (project website hosted on smartphone perpetually low on battery, sole distribution maintainer regularly crossing highways in front of buses for relaxing, community members eating little kids for breakfast) in opposition to "professional" distributions (RHEL, Oracle, SLES and similar distributions driving airports, moon missions and nuclear plants).
Let's not forget that Noah's Ark was built by amateurs, while the Titanic was a professional project.
Let's not forget that Noah's Ark was built by amateurs, while the Titanic was a professional project.
None of Microsoft's vapour ware ever failed either.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

As for security, grsecurity isn't too difficult to get up and running on Slackware, though its goals are somewhat different than SELinux's.