By blocking p2p, you could prevent useful transfers such as linux ISOs
You're kidding, right? Who would download linux binaries, or even linux source, from a 'peer.'
It's much better to get software like that from an official source. There's no additional bandwidth chewed up by the user to do so. No way in hell I'd run binaries gotten off a p-p network, particularly not Free Software that I can download legitimately from an official source.
I agree strongly. Some of my favorite hardware to set up and configure are old SparcStations, because I can configure and use them without anything connected but a serial console.
Needless to say, this goes over well for the client ($8000 expense is better than $10000 expense), and also for us ($7000 revenue is better than $5000 revenue ).
You forgot to include the other reasons it goes over well for you. The vendor lock-in you can achieve by using less well-known software that requires command-line configuration, regular updates (because it's open source, more people are crawling through the source discovering exploits, which are published in IRC and on Usenet, then fixes are implemented, etc. etc.), and so on. The client can't just pull in any run-of-the-mill certified MSCE to maintain the OS system. They will need YOU.
Remember, Linux Advocates are the Palladins of OS advocacy. They are on a Holy War and compelled to do battle with evil. As such, they may make occasional errors, but they are always Right.
If you read the footnotes in the article, you'll see that it was a published post in comp.risks. That's sorta the equivalent of being an entry on a blog, except comp.risks usually has more credibility than this one.
When are we going to start seeing more links to articles from The Onion?
A lot of dogs aren't leashed, so they don't have that psychotic behavior when they get loose. Any dog that's just kept in a fenced yard is for some reason more clueful. Maybe an animal psychologist can explain it.
Hope you don't get hit by a truck digging in that trash can for food.
That's the same reason most of the hardware vendors, i.e. Compaq, didn't want to bundle OS/2. They would then have been giving a substancial amount of money to IBM, a competing hardware vendor, for each copy of OS/2 sold.
This isn't often brought up, though, because it doesn't slag Microsoft, and it actually weakens the arguement that OEMs wouldn't bundle OS/2 because of Microsoft pressure.
When I compare how far NT has come in 5 years, I bear in mind that my present W2K system hasn't totally crashed more than a few times since I started using it when W2K came out. With NT 4.0 bluescreens were as frequent as a Linux zealot's fantasy of them happening.
They've come quite a ways in 5 years. So has Linux.
Your folkloric description of Linux programmers sounds a little eggagerated, by the way. You described the Slashdot demographic, not the kernal hacker demographic. Also, lots of the best stuff going into the Linux kernal these days is coming out of cube farms at places like IBM.
No, it's kinda like what a Red Hat dot.zero release would be like if they took an additional 9 months to test it.
I mean, I have not-so-fond memories of using Red Hat 5.0 for a short while. They included a new graphical tool for installing and administering RPMs to the system called Glint. However, the Glint binary was broken that they bundled with the system. So one had to download the bugfixed glint rpm and manually install it.
At the time I found this amusing. Then I went back to using the Slackware I'd already had good luck with for several years.
It should be pretty clear to anybody with a clue that Windows ME was a market-driven product, a stopgap to bridge from Win98SE to XP. As such, it was probably considered a stinking ghetto of a project to work on at Microsoft.
I recall reading a Usenet post or two written by someone who had just loaded and ran Opera for the first time. It's similar to the behavior of people who get online with Linux for the first time.
They act like a dog that's gotten off a leash for the very first time.
They are soo, soo, sooooo liberated and free. Or something.
It has always amazed me that Steve Ballmer and his 'Developers, developers....' rant gets so much play, and everybody forgets that it's yet another thing that Microsoft stole from Apple. I mean, Ballmer may be somewhat amusing to observe, but the real court jester of that kind of highjinx was good old Guy Kawasaki. What a clown he was!
I have a Compaq OEM Windows NT 4.0 CDROM, and it boots on Alpha or Intel boxes, if they support bootable CDROM.
Mind you, this is a Compaq OEM CD from long before Compaq bought Digital. There was NO REASON for them to be distributing a CD that booted on a competitors architecture at that time.
It's not labelled 'Compaq', btw, it's just one that was bundled with a Compaq system originally.
Linux zealots tearing at Windows all the time is just as stupid and as much FUD as Windows zealots that tear at Linux all the time.
There's a history behind this phenomenon in the 'Linux community.'
In the early days of Linux, everyone involved was a Unix enthusiast. There was a snobbish tendency at that time to dismiss anything Microsoft, but there wasn't the anger and hostility that there is now.
As the Microsoft Batallion rolled on, the expatriates from all the losing platforms (Amiga, Atari, OS/2, some Mac people) crowded onto the Linux 'ship.' Now there is a solid subsection of the 'Linux community' that actually represents the majority of vocal Linux users, who are bitter 'Anything-But-Microsoft' naysayers.
These people really foul things up. They bring a strong taint of negativity to the community. Much of what they constantly push Linux to become (these are the 'We need ONE UNIFIED DESKTOP to DEFEAT MICROSOFT' people) actually ends up hurting Linux and Open Source.
I accidentally overclocked my video card for quite awhile. This was years ago.
Back when I had a 386DX-25 motherboard, there was an 'AT Bus Clock Ratio' setting in the BIOS. Basically you were supposed to set it so that the ISA slots got the regular 8 MHz clock they're supposed to see. Depending on your CPU speed at the time, there were ratio settings to configure this.
I inadvertantly had mine set for an AT Bus clock speed of 12 MHz. I think it was set to a 2/1 ratio when I should have used a 3/1 ratio, because I had a 25 MHz chip, not a 16. It made Doom and Wolfenstein 3D run much snappier, which I determined after discovering my error and setting it back to where it should have been. I also found that it made some ISA cards unstable or completely unfunctional in the system.
Slashdot Mirror
Furniture dealerships with a half dozen outlets make $300,000 profits. A 300K profit is what, about 1/50 of their payroll? Or less?
That's a pathetic figure for a company with international exposure.
I liked the Linux playpus logo a lot more than I like that stupid penguin.
It was an unfortunate day that that penguin bit Linus.
That's what libraries in Iraq are like.
Thousands and thousands of people marched last weekend to uphold the right of the authorities in Iraq to stay in power.
People weren't stealing horse buggy whips to machine into auto parts.
Yeah, I know, the analogy breaks down. Not any more than yours, though.
By blocking p2p, you could prevent useful transfers such as linux ISOs
You're kidding, right? Who would download linux binaries, or even linux source, from a 'peer.'
It's much better to get software like that from an official source. There's no additional bandwidth chewed up by the user to do so. No way in hell I'd run binaries gotten off a p-p network, particularly not Free Software that I can download legitimately from an official source.
I agree strongly. Some of my favorite hardware to set up and configure are old SparcStations, because I can configure and use them without anything connected but a serial console.
Why the heck do I want a fancy graphical startup?
Needless to say, this goes over well for the client ($8000 expense is better than $10000 expense), and also for us ($7000 revenue is better than $5000 revenue ).
You forgot to include the other reasons it goes over well for you. The vendor lock-in you can achieve by using less well-known software that requires command-line configuration, regular updates (because it's open source, more people are crawling through the source discovering exploits, which are published in IRC and on Usenet, then fixes are implemented, etc. etc.), and so on. The client can't just pull in any run-of-the-mill certified MSCE to maintain the OS system. They will need YOU.
It's JALAA.
(Just Another Linux Advocacy Article)
Remember, Linux Advocates are the Palladins of OS advocacy. They are on a Holy War and compelled to do battle with evil. As such, they may make occasional errors, but they are always Right.
If you read the footnotes in the article, you'll see that it was a published post in comp.risks. That's sorta the equivalent of being an entry on a blog, except comp.risks usually has more credibility than this one.
When are we going to start seeing more links to articles from The Onion?
A lot of dogs aren't leashed, so they don't have that psychotic behavior when they get loose. Any dog that's just kept in a fenced yard is for some reason more clueful. Maybe an animal psychologist can explain it.
Hope you don't get hit by a truck digging in that trash can for food.
Well, is it a fake?
What backs up your claim that it's real? Or is it just a parody page?
Hell, why be so obvious.
Get a signature for DR-DOS and use loadlin.com
Okay, then. Solaris.
That's the same reason most of the hardware vendors, i.e. Compaq, didn't want to bundle OS/2. They would then have been giving a substancial amount of money to IBM, a competing hardware vendor, for each copy of OS/2 sold.
This isn't often brought up, though, because it doesn't slag Microsoft, and it actually weakens the arguement that OEMs wouldn't bundle OS/2 because of Microsoft pressure.
Yes. It reminds me of NetBSD, too.
When I compare how far NT has come in 5 years, I bear in mind that my present W2K system hasn't totally crashed more than a few times since I started using it when W2K came out. With NT 4.0 bluescreens were as frequent as a Linux zealot's fantasy of them happening.
They've come quite a ways in 5 years. So has Linux.
Your folkloric description of Linux programmers sounds a little eggagerated, by the way. You described the Slashdot demographic, not the kernal hacker demographic. Also, lots of the best stuff going into the Linux kernal these days is coming out of cube farms at places like IBM.
No, it's kinda like what a Red Hat dot.zero release would be like if they took an additional 9 months to test it.
I mean, I have not-so-fond memories of using Red Hat 5.0 for a short while. They included a new graphical tool for installing and administering RPMs to the system called Glint. However, the Glint binary was broken that they bundled with the system. So one had to download the bugfixed glint rpm and manually install it.
At the time I found this amusing. Then I went back to using the Slackware I'd already had good luck with for several years.
It should be pretty clear to anybody with a clue that Windows ME was a market-driven product, a stopgap to bridge from Win98SE to XP. As such, it was probably considered a stinking ghetto of a project to work on at Microsoft.
I recall reading a Usenet post or two written by someone who had just loaded and ran Opera for the first time. It's similar to the behavior of people who get online with Linux for the first time.
They act like a dog that's gotten off a leash for the very first time.
They are soo, soo, sooooo liberated and free. Or something.
It has always amazed me that Steve Ballmer and his 'Developers, developers....' rant gets so much play, and everybody forgets that it's yet another thing that Microsoft stole from Apple. I mean, Ballmer may be somewhat amusing to observe, but the real court jester of that kind of highjinx was good old Guy Kawasaki. What a clown he was!
I have a Compaq OEM Windows NT 4.0 CDROM, and it boots on Alpha or Intel boxes, if they support bootable CDROM.
Mind you, this is a Compaq OEM CD from long before Compaq bought Digital. There was NO REASON for them to be distributing a CD that booted on a competitors architecture at that time.
It's not labelled 'Compaq', btw, it's just one that was bundled with a Compaq system originally.
Linux zealots tearing at Windows all the time is just as stupid and as much FUD as Windows zealots that tear at Linux all the time.
There's a history behind this phenomenon in the 'Linux community.'
In the early days of Linux, everyone involved was a Unix enthusiast. There was a snobbish tendency at that time to dismiss anything Microsoft, but there wasn't the anger and hostility that there is now.
As the Microsoft Batallion rolled on, the expatriates from all the losing platforms (Amiga, Atari, OS/2, some Mac people) crowded onto the Linux 'ship.' Now there is a solid subsection of the 'Linux community' that actually represents the majority of vocal Linux users, who are bitter 'Anything-But-Microsoft' naysayers.
These people really foul things up. They bring a strong taint of negativity to the community. Much of what they constantly push Linux to become (these are the 'We need ONE UNIFIED DESKTOP to DEFEAT MICROSOFT' people) actually ends up hurting Linux and Open Source.
It sure used to be a lot more fun to run Linux.
Marketroid driven closed source software does not work.
I feel ridiculous for even having to say this, but the first line in your comment was 'Blanket statements are stupid....'
Don't you feel like an idiot now? You should have clicked 'review' and looked closely at your message body before submitting.
Wow. There are still OS/2 zealots out there.
I accidentally overclocked my video card for quite awhile. This was years ago.
Back when I had a 386DX-25 motherboard, there was an 'AT Bus Clock Ratio' setting in the BIOS. Basically you were supposed to set it so that the ISA slots got the regular 8 MHz clock they're supposed to see. Depending on your CPU speed at the time, there were ratio settings to configure this.
I inadvertantly had mine set for an AT Bus clock speed of 12 MHz. I think it was set to a 2/1 ratio when I should have used a 3/1 ratio, because I had a 25 MHz chip, not a 16. It made Doom and Wolfenstein 3D run much snappier, which I determined after discovering my error and setting it back to where it should have been. I also found that it made some ISA cards unstable or completely unfunctional in the system.
Them were the days.