ZD Labs ran WebBench on the Dell Red Hat system and on the Ultra 10 Solaris system.
Apple ran NetBench on the Dell NT system and on the Mac OS X system.
Perhaps you might want to consider an English class or two. Perhaps you might want to consider reading more carefully before making an ass of yourself. Perhaps not.
Slackware, besides being obsolete shit, is not completely free software. Worse yet, there are no plans to change this. Slackware does nothing to help develop Linux. Slackware is a parasite.
What in Slackware is not "completely free"? Patrick Volkerding himself has written a fair amount of Linux software, some of it without credit, and provided us with a traditional unix-like distribution at the same time. How can you say Slackware contributes nothing?
Kernels must be renamed because some of the tools can't tell them apart otherwise. I think the modules stuff has problems.
Kernel packages do not need to be renamed, under any circumstances. I am not talking about your vmlinuz image, I'm talking about the actual package it originally comes in. If you download and install a tarball named 2.2.3, it damn well should be a 2.2.3 kernel, and not a 2.2.3-pre2 or some such thing. (Note: this is an example. I am not accusing Red Hat of distributing 2.2.3-pre2 and passing it off as 2.2.3, specifically.) Such practices have also been noted in the realm of libraries.
Marketing is good. Excessive QA lets the software get obsolete. Red Hat generally ships with the most recent kernel they can find, and then some.
Marketing is all well and good, yes. But your point about "excessive QA" puzzles me. You would rather have a system slapped together the day before yesterday from whatever was lying around than one that was put together and tested over a period of the last couple of months? There's a reason it's called "bleeding edge."
The problem with this is mainly on the corporate side. As companies begin to develop on and invest in Linux, it becomes increasingly important to ensure that a distribution does not grab all the support and run away with it. Think about it: for many people, the sole reason for not running Linux right now is that certain programs are not supported. Now suppose the current trend of "Red Hat as corporate Linux" continues, accelerated by their presence in the corporate world and the support of commercial software companies. Now suppose they decide to rename some pre-release library, and badness ensues. Do people say "Red Hat fooked up on me?" or do they say "Linux fooked up on me?"
Maybe it sounds paranoid, but then again maybe it deserves some consideration. Because the first half of that scenario is already occurring, and the second half (based on observations of Red Hat's past behavior) seems not at all unlikely.
The others are full of proprietary crap, including shareware and half-assed Open Source. If you want to write an open letter of complaint, try SuSE, Slackware, EasyLinux, or Mandrake. All of those are far worse behaved than Red Hat is.
Disclaimer: I may be considered a bit biased. But whatever.
Explain thyself? How is Slackware, for instance, worse than a distro (Red Hat) that renames their libraries and kernels so that they appear to be full releases when in actuality they're pre-releases? How is it worse than a distro whose install often ignores the user's wishes, and which actively presents and promotes itself as the Linux? How is it worse than a distro that is far, far more marketing and hype than QA and careful testing?
whoa. careful there, you might start a panic. (Or throw another stick on the ignorance fire.)
Slackware sends an email from Patrick Volkerding to root when installed, and asks very nicely for the newly-rooted to visit the Linux Counter and register.
I think you misinterpret what I mean by "unstable". Not "unstable" as in you link against it and your app crashes and burns. "Unstable" as in it's still in development and therefore subject to change. "Unstable" as in it's still in development, and therefore you can't be assured that everyone has the latest (probably not greatest) version.
GTK 1.0 is stable. Version releases occur infrequently, and people generally have the latest version. If they don't, you can be sure they can safely upgrade to it.
You miss the point... They're doing all of their development based on the development branches of various libraries. A lot of people are. A lot of silly, silly Gprimates.
How are they ever supposed to become stable, if they're basing all of their work on a shaky foundation? The stable versions of most of those libs are there. Use them.
Would you people stop coding every damn thing with experimental/developmental libraries? There's a reason it's called being "bleeding edge".
I use x11amp 0.7, because I have found nothing particularly better for X. (I'm a pretty big fan of nice GUIs, if I'm gonna have a GUI.) I was going to install 0.9a essentially for the double-size option.
But wow, check out the libraries I'd need:
glib 1.1.14
gtk+ 1.1.14
imlib 1.9.2
linuxthreads 0.71
gnu gettext 0.10
For imlib, I'd need:
giflib 3.0-2
libungif 3.0
libpng 1.0.1
zlib 1.1.2
jpegsrc 6b
ImageMagick 4.0.5
See a trend? Why do people write so much software that compiles only against developmental/experimental libraries?
Not to mention the stuff that the G-crowd (and E-flock) consider standard, but nobody else has or uses....
Yeah, these new libs (especially gtk) tend to have some neato-burrito whiz-bang wowie-zowie features, but can't we wait til they're something resembling stable? Isn't that why there're separate "stable" and "development" versions?
The idea was to announce, ahead of time, that they would be experiencing downtime. Posting it to their mailing list only gets that half-done. Of course everyone's going to find out after the fact.
Not that experiencing downtime for a server move is anything but unprofessional on their part, to begin with...
Try tx.us.mirrors.freshmeat.net or ct.us.mirrors.freshmeat.net, unfortunately, i think these mirrors are stale because the core freshmeat server hasn't been updating them because they are down.
Well, yeah. But to be reasonable (and yo0u really should be reasonable, if you feel the need to go down at all), you should go down during a time period when your traffic is at its lowest. Typically, that's night-time in the United States. (Yes, that's daytime elsewhere... but most traffic still originates in the U.S.)
Slackware.com, for instance, gets most of its hits right around lunchtime, EST.
Slashdot Mirror
so you really believe they're running a default configuration?
Come on, all prejudices aside, I'd be willing to bet the people running that server are reasonably competent.
I started on Red Hat. I'm co-webmaster of slackware.com.
:)
Clearly, I switched.
So glibc2.1 was the first official release of glibc2. 'til now, all the "glibc2-based" distros have been built on pre-release C libraries.
Does that make sense to you?
A glibc2-based version of Slack is next, after 4.0. (Based on an actual, honest-to-god release of glibc2. Go figure.)
Well, no.
ZD Labs ran WebBench on the Dell Red Hat system and on the Ultra 10 Solaris system.
Apple ran NetBench on the Dell NT system and on the Mac OS X system.
Perhaps you might want to consider an English class or two. Perhaps you might want to consider reading more carefully before making an ass of yourself. Perhaps not.
Slackware, besides being obsolete shit, is not completely free software. Worse yet, there are no plans to change this. Slackware does nothing to help develop Linux. Slackware is a parasite.
What in Slackware is not "completely free"? Patrick Volkerding himself has written a fair amount of Linux software, some of it without credit, and provided us with a traditional unix-like distribution at the same time. How can you say Slackware contributes nothing?
Kernels must be renamed because some of the tools can't tell them apart otherwise. I think the modules stuff has problems.
Kernel packages do not need to be renamed, under any circumstances. I am not talking about your vmlinuz image, I'm talking about the actual package it originally comes in. If you download and install a tarball named 2.2.3, it damn well should be a 2.2.3 kernel, and not a 2.2.3-pre2 or some such thing. (Note: this is an example. I am not accusing Red Hat of distributing 2.2.3-pre2 and passing it off as 2.2.3, specifically.) Such practices have also been noted in the realm of libraries.
Marketing is good. Excessive QA lets the software get obsolete. Red Hat generally ships with the most recent kernel they can find, and then some.
Marketing is all well and good, yes. But your point about "excessive QA" puzzles me. You would rather have a system slapped together the day before yesterday from whatever was lying around than one that was put together and tested over a period of the last couple of months? There's a reason it's called "bleeding edge."
The problem with this is mainly on the corporate side. As companies begin to develop on and invest in Linux, it becomes increasingly important to ensure that a distribution does not grab all the support and run away with it. Think about it: for many people, the sole reason for not running Linux right now is that certain programs are not supported. Now suppose the current trend of "Red Hat as corporate Linux" continues, accelerated by their presence in the corporate world and the support of commercial software companies. Now suppose they decide to rename some pre-release library, and badness ensues. Do people say "Red Hat fooked up on me?" or do they say "Linux fooked up on me?"
Maybe it sounds paranoid, but then again maybe it deserves some consideration. Because the first half of that scenario is already occurring, and the second half (based on observations of Red Hat's past behavior) seems not at all unlikely.
Apache, like pretty much everything else in Slackware, is installed according to the author's defaults.
This is a wee bit inaccurate, save for the title.
And no, I do not care to elaborate.
The others are full of proprietary crap, including shareware and half-assed Open Source. If you want to write an open letter of complaint, try SuSE, Slackware, EasyLinux, or Mandrake. All of those are far worse behaved than Red Hat is.
Disclaimer: I may be considered a bit biased. But whatever.
Explain thyself? How is Slackware, for instance, worse than a distro (Red Hat) that renames their libraries and kernels so that they appear to be full releases when in actuality they're pre-releases? How is it worse than a distro whose install often ignores the user's wishes, and which actively presents and promotes itself as the Linux? How is it worse than a distro that is far, far more marketing and hype than QA and careful testing?
This is true for some people, I suppose.
But most of this is people picking their heroes and pitting them against each other. Mostly harmless.
Yeah, run Slashdot on your NT box. Go for it.
whoa. careful there, you might start a panic. (Or throw another stick on the ignorance fire.)
Slackware sends an email from Patrick Volkerding to root when installed, and asks very nicely for the newly-rooted to visit the Linux Counter and register.
It does not "phone home" all by itself.
Get a grip.
Case in point.
You remember "fun", don't you?
From before you got that telephone pole lodged in your ass.
I've dropped hard drives down flights of stairs with no negative repercussions.
:)
But then, I always was lucky as hell.
Gtk 1.1 is perfectly stable
I think you misinterpret what I mean by "unstable". Not "unstable" as in you link against it and your app crashes and burns. "Unstable" as in it's still in development and therefore subject to change. "Unstable" as in it's still in development, and therefore you can't be assured that everyone has the latest (probably not greatest) version.
GTK 1.0 is stable. Version releases occur infrequently, and people generally have the latest version. If they don't, you can be sure they can safely upgrade to it.
You miss the point... They're doing all of their development based on the development branches of various libraries. A lot of people are. A lot of silly, silly Gprimates.
How are they ever supposed to become stable, if they're basing all of their work on a shaky foundation? The stable versions of most of those libs are there. Use them.
I use x11amp 0.7, because I have found nothing particularly better for X. (I'm a pretty big fan of nice GUIs, if I'm gonna have a GUI.) I was going to install 0.9a essentially for the double-size option.
But wow, check out the libraries I'd need:
- glib 1.1.14
- gtk+ 1.1.14
- imlib 1.9.2
- linuxthreads 0.71
- gnu gettext 0.10
For imlib, I'd need:See a trend? Why do people write so much software that compiles only against developmental/experimental libraries?
Not to mention the stuff that the G-crowd (and E-flock) consider standard, but nobody else has or uses....
Yeah, these new libs (especially gtk) tend to have some neato-burrito whiz-bang wowie-zowie features, but can't we wait til they're something resembling stable? Isn't that why there're separate "stable" and "development" versions?
You miss the point.
The idea was to announce, ahead of time, that they would be experiencing downtime. Posting it to their mailing list only gets that half-done. Of course everyone's going to find out after the fact.
Not that experiencing downtime for a server move is anything but unprofessional on their part, to begin with...
subscribe to a few.
It gets to be a pain in the ass.
Support from companies like Creative (especially Creative) will go a long way toward helping drag the game industry to our Operating System of Choice.
Try tx.us.mirrors.freshmeat.net or ct.us.mirrors.freshmeat.net, unfortunately, i think these mirrors are stale because the core freshmeat server hasn't been updating them because they are down.
It gets better:
fwhois freshmeat.net
*snip*
Domain servers in listed order:
NS.REDHAT.COM 207.175.42.153
SPEEDY.REDHAT.COM 199.183.24.251
Which is why I can't use the mirrors. Nobody's pointing to them.
Red Hat just doesn't have their shit together.
Well, yeah. But to be reasonable (and yo0u really should be reasonable, if you feel the need to go down at all), you should go down during a time period when your traffic is at its lowest. Typically, that's night-time in the United States. (Yes, that's daytime elsewhere... but most traffic still originates in the U.S.)
Slackware.com, for instance, gets most of its hits right around lunchtime, EST.
Freshmeat is hosted by Red Hat.
silly freshmeat.