It's not a question of not buying CD's, it's a question of not buying CD's that are on RIAA labels. Speaking as someone who is a memeber of the independant music community, I can say that bands like ours could use all the support we could get, in order to try and find a place for ourselves and avoid what boils down to a Management Union. The more independant music you buy, the less power the RIAA has, whereas if you don't buy -any- music, then the balance of power stays the same, and believe it or not, you actually help fund their statistics of people not buying music due to piracy. And for the recrod, there are plenty of music labels that aren't members of the RIAA. For example, If you're into Punk, (My area of expertise) there is Street Anthem Records and Fat Wreck Records. Both are known for treating their bands with the level of dignity and respect (and revenue ) that performers aught to be due. What I'm saying is that it's necessary to go a step further than not supporting the RIAA. You have to support their enemy, which would be free and independant music organizations.
And now its time for my shameless self plug, since we don't have the billions of the RIAA backing us for their own exploitive purposes, and probably never will:
The Pubcrawlers http://the-pubcrawlers.com New England Celtic Punk
Get a BS in Business Admin. Being in my senior year of my undergraduate degree, I will go so far as to say it was worthless. Especially if you alerady have job experience. With the Business degree, you will learn how to navigate the buisness world. You can always pick up technical skills on your own.
I really have to ask a question. When is the last time the moderators of this site actually posted anything remotely positive about Slackware? I have used Slackware for something around 7 years now. I have tried Redhat, Suse, and Stormix. Nothing against any of them, but they are not for me. I was taught BSD style UNIX, and I find Slackware fills the functionality I need. Yet it constantly gets negative press from this news site. I haven't even HEARD of the tool that was mentioned in the headline. Alot of Slackware users haven't either. It just simply amazes me, that, because a developer of a tool that isn't even very known amongst the users of a distrobution is some how the equivilant to the distrobution dying, or fading away.
This shows a severe lack of responsibility on the part of the person who posted this story, not to mention, it's extremly insulting to the thousands of people who use slackware. I honestly think that there should be a public apology posted. This is utterly rediculous, and I am getting sick and tired of having to read about how Slackware is old, dying, useless, or whatever. It is still one of the largest used Linux distrobutuins in existance, especially in an enterprise/server market.
This is specifically the sort of infighting that is causing problems with any sort of possible true unification of the GNU movement. If people could at least pay a little respect to other peoples methods and thinking, than I think that Free Software as a whole would go considerably further. Who cares whether or not a certain distro does something the way you want it to? It's more important that the code is free. And since Slackware, like a considerable amount of other distrobutions is GNU, through and though, it should be celebrated. So for the love of god, Download Slackware, Red Hat, or whatever, play with it to your hearts content. Crack open a beer. Smile. That's what it's all about, isn't it? You have the Freedom to do so.
Okay, I see absolutely nothing useful here. It is a fat, disturbingly bloated high level language, with no perticular improvment in theory or concept over something such as java, but with even -more- built in functions. Is there anyone else here who would rather see something more interesting than a CEO trying to get his name out?
Re:The Neverending wave of criticism of slackware.
on
Slackware 8.0 Released
·
· Score: 2
Excuse me, I should re-iterate, a more potent graphical package tool is in development. There is a package tool out there, and it is incredibly easy to use, and efficient. Its 10:30 after a very very late coding run.
these mistakes can happen:-p
Long Live Slackware!
The Neverending wave of criticism of slackware....
on
Slackware 8.0 Released
·
· Score: 5
If there is one thing I do not understand, is the neverending wave of criticism often dealt out to slackware linux. Either it is attacked for its lack of a package management system, or it is attacked for not being a modern OS, or whathave you.
First and foremost, Slackware linux was never intended to be a 'modern' operating system. It was not intended to follow the broken precident that Microsoft established for operating systems, which is that of bleeding edge dysfunctionality due to attempts at convenience. It was intended to follow the UNIX model of an operating system, more specifically the BSD model. Slackware was originally created because Patrick Volkerding couldn't get 386BSD working on his computer. So he took the time and created the basis of a truely UNIX based linux distrobution. It's a damn shame no one else seems to have followed his lead.
Also, another point: does anyone remember the early glibc nightmares, when redhat would break half the time? I never had that problem on my personal box, because the people at slackware waited until a more stable release came out. I have yet to use a more stable release of linux, having used a good 5 different distros since I have started my linux career back in 94. I never, and repeat -never- have had to deal with any eath shattering flaw out of a stable release of slackware. And it is considerably more secure out of the box than most other distrobutions I have useds.
To address the issue of packages; there is a package tool in development. And development is taking its time, to make sure a stable product is publicly released to the masses. And when it comes down to it, there is still no easier way to deal with source code than the tarbal. It is the one step short of having a CVS tree. Since source is the fundamental element of the GNU revolution,
it must be payed attention to, and Slackware certainly does. Sources are apart of every distrobution. And do you know something? Slackware tarballs are still cross platform compatable to other unixes, or windows. Or at least far more than RPMs or DEBs.
Slackware is a sourcefriendly distrobution that is rock solid from the bottom up. It is not a wonder that it doesn't die, It is only a wonder that people don't take the time to think about seriously using it.
I hate to disagree, however, I have had no library issues with Slackware whatsoever. Esound is happy, Enlightenment, Gtk, and anything else you care to throw at it. I am familiar with both RH and Slackware, and would have to say that I enjoy Slackwares lean, cognisant functionality over RH's, but when it comes down to it, they are both Linux, and they both function rather well.
I honestly believe this is one of the most ill-thought out pieces I have read in a long time. I think if anything, our blind acceptance of technology is at the very crux of the flaws of the twentieth century.I am hardly a Luddite, however, the human impact is often uncalculated. It is the letting go of those precious '-isms' as they were so referred to that have caused us to be in the trap that we are in now. As much as technology has the potential to benifit us as a whole, it is only a tool; and it takes an idealology to weild that tool. To worship the tool itself is just fool hearty.
I'll agree, but neither are viable lifestyle options. Everything in moderation. I've met both too many drunks, and too many burnouts to really embrace either as anything more than an occasional activity, preferably social at that. And of course, this is providing that the pot is pure, and not mixed/laced. I have to admit, though, from what I've heard, it does make for much easier coding, at least when you have to deal with C++ OO hierarchy. Either way, I find that geeks who've had a few to drink make much better company then geeks who've taken a few hits, for as you said, it makes for a better escape.
Slashdot Mirror
It's not a question of not buying CD's, it's a question of not buying CD's that are on RIAA labels. Speaking as someone who is a memeber of the independant music community, I can say that bands like ours could use all the support we could get, in order to try and find a place for ourselves and avoid what boils down to a Management Union. The more independant music you buy, the less power the RIAA has, whereas if you don't buy -any- music, then the balance of power stays the same, and believe it or not, you actually help fund their statistics of people not buying music due to piracy. And for the recrod, there are plenty of music labels that aren't members of the RIAA. For example, If you're into Punk, (My area of expertise) there is Street Anthem Records and Fat Wreck Records. Both are known for treating their bands with the level of dignity and respect (and revenue ) that performers aught to be due. What I'm saying is that it's necessary to go a step further than not supporting the RIAA. You have to support their enemy, which would be free and independant music organizations.
And now its time for my shameless self plug, since we don't have the billions of the RIAA backing us for their own exploitive purposes, and probably never will:
The Pubcrawlers
http://the-pubcrawlers.com
New England Celtic Punk
Get a BS in Business Admin. Being in my senior year of my undergraduate degree, I will go so far as to say it was worthless. Especially if you alerady have job experience. With the Business degree, you will learn how to navigate the buisness world. You can always pick up technical skills on your own.
Wait, hold up. Stop everything here.
I really have to ask a question. When is the last time the moderators of this site actually posted anything remotely positive about Slackware? I have used Slackware for something around 7 years now. I have tried Redhat, Suse, and Stormix. Nothing against any of them, but they are not for me. I was taught BSD style UNIX, and I find Slackware fills the functionality I need. Yet it constantly gets negative press from this news site. I haven't even HEARD of the tool that was mentioned in the headline. Alot of Slackware users haven't either. It just simply amazes me, that, because a developer of a tool that isn't even very known amongst the users of a distrobution is some how the equivilant to the distrobution dying, or fading away.
This shows a severe lack of responsibility on the part of the person who posted this story, not to mention, it's extremly insulting to the thousands of people who use slackware. I honestly think that there should be a public apology posted. This is utterly rediculous, and I am getting sick and tired of having to read about how Slackware is old, dying, useless, or whatever. It is still one of the largest used Linux distrobutuins in existance, especially in an enterprise/server market.
This is specifically the sort of infighting that is causing problems with any sort of possible true unification of the GNU movement. If people could at least pay a little respect to other peoples methods and thinking, than I think that Free Software as a whole would go considerably further. Who cares whether or not a certain distro does something the way you want it to? It's more important that the code is free. And since Slackware, like a considerable amount of other distrobutions is GNU, through and though, it should be celebrated. So for the love of god, Download Slackware, Red Hat, or whatever, play with it to your hearts content. Crack open a beer. Smile. That's what it's all about, isn't it? You have the Freedom to do so.
Okay, I see absolutely nothing useful here. It is a fat, disturbingly bloated high level language, with no perticular improvment in theory or concept over something such as java, but with even -more- built in functions. Is there anyone else here who would rather see something more interesting than a CEO trying to get his name out?
Excuse me, I should re-iterate, a more potent graphical package tool is in development. There is a package tool out there, and it is incredibly easy to use, and efficient. Its 10:30 after a very very late coding run.
:-p
these mistakes can happen
Long Live Slackware!
If there is one thing I do not understand, is the neverending wave of criticism often dealt out to slackware linux. Either it is attacked for its lack of a package management system, or it is attacked for not being a modern OS, or whathave you.
First and foremost, Slackware linux was never intended to be a 'modern' operating system. It was not intended to follow the broken precident that Microsoft established for operating systems, which is that of bleeding edge dysfunctionality due to attempts at convenience. It was intended to follow the UNIX model of an operating system, more specifically the BSD model. Slackware was originally created because Patrick Volkerding couldn't get 386BSD working on his computer. So he took the time and created the basis of a truely UNIX based linux distrobution. It's a damn shame no one else seems to have followed his lead.
Also, another point: does anyone remember the early glibc nightmares, when redhat would break half the time? I never had that problem on my personal box, because the people at slackware waited until a more stable release came out. I have yet to use a more stable release of linux, having used a good 5 different distros since I have started my linux career back in 94. I never, and repeat -never- have had to deal with any eath shattering flaw out of a stable release of slackware. And it is considerably more secure out of the box than most other distrobutions I have useds.
To address the issue of packages; there is a package tool in development. And development is taking its time, to make sure a stable product is publicly released to the masses. And when it comes down to it, there is still no easier way to deal with source code than the tarbal. It is the one step short of having a CVS tree. Since source is the fundamental element of the GNU revolution,
it must be payed attention to, and Slackware certainly does. Sources are apart of every distrobution. And do you know something? Slackware tarballs are still cross platform compatable to other unixes, or windows. Or at least far more than RPMs or DEBs.
Slackware is a sourcefriendly distrobution that is rock solid from the bottom up. It is not a wonder that it doesn't die, It is only a wonder that people don't take the time to think about seriously using it.
I hate to disagree, however, I have had no library issues with Slackware whatsoever. Esound is happy, Enlightenment, Gtk, and anything else you care to throw at it. I am familiar with both RH and Slackware, and would have to say that I enjoy Slackwares lean, cognisant functionality over RH's, but when it comes down to it, they are both Linux, and they both function rather well.
I honestly believe this is one of the most ill-thought out pieces I have read in a long time. I think if anything, our blind acceptance of technology is at the very crux of the flaws of the twentieth century.I am hardly a Luddite, however, the human impact is often uncalculated. It is the letting go of those precious '-isms' as they were so referred to that have caused us to be in the trap that we are in now. As much as technology has the potential to benifit us as a whole, it is only a tool; and it takes an idealology to weild that tool. To worship the tool itself is just fool hearty.
I'll agree, but neither are viable lifestyle options. Everything in moderation. I've met both too many drunks, and too many burnouts to really embrace either as anything more than an occasional activity, preferably social at that. And of course, this is providing that the pot is pure, and not mixed/laced. I have to admit, though, from what I've heard, it does make for much easier coding, at least when you have to deal with C++ OO hierarchy. Either way, I find that geeks who've had a few to drink make much better company then geeks who've taken a few hits, for as you said, it makes for a better escape.