I'm using a small local provider that somehow escaped unscathed from the raping of most of the local providers here (they all pretty much went out of business or were bought by large national/regional shops). I believe they charge us about US$200/month to get 1 IP address and 1 100mbit ethernet port. They have DS3 connectivity, and we get charged extra if we go over 10GB of traffic per month. They give us a small locked cabinet (1/4 of a rack) that could probably fit about 10U of equipment. They have multiple grid feeds from the power company to reduce the likelyhood of total outage, but you're on your own for supplying a small UPS for your equipment. Prices go up for more GB/month and/or more IPs and ethernet cables.
All of these points on RMS are true, but please also remember that everyone has their place. A strong grassroots movement like GPL/OSS stuff doesn't only need polished presenters, they also *need* fringe lunatics. RMS and his kind are a driving force, they're the fringe that helps offset the other side and helps the rest of us to find a happy medium.
For functional bugs a tool such as Bugzilla works well in supporting developers, but presents complex interfaces to other potential contributors
I don't think even many developers find Bugzilla to be a simple interface. I would find it easier to type in SQL queries againsta bug database manually than use the Bugzilla web interface.
I'm a big fan of the notion that there's a distinct if somewhat grey line between Invention and Discovery, and that only Invention should be patentable. Discovering a new species of mouse in the wild does not give one the right to patent it. Inventing a new species of mouse through genetic manipulation does, although it raises ethical questions, especially if applied to a more emotionally developed mammal like a dolphin, a dog, or a human.
Their results are not accurate
on
IDE RAID Examined
·
· Score: 5, Informative
First off, they've failed to note that some of their contestants are in fact just IDE controllers, with the RAID functionality implemented in the software driver (WinRAID, like WinModems), whereas others are Hardware. I don't know all four products well, so I'm unsure on at least one of them as to which are which.
They tested CPU utilization, and seperately various speed tests, but never a comprehensive "loaded system" test. As expected they ranked the Adaptec (a true hardware RAID) lowest, while ranking the WinRAID's higher. This couldn't be further from the real truth. Sure, the idle P4 cpu does a great job of fast software RAID compared to the embedded RAID ASIC on Adaptec's card. However, if you had a heavily loaded server machine, where the processors were loaded down doing other things (say SSL-encrypting for an secure web server), the machine with the Adaptec would trounce the others, as the RAID processing speed will not decrease while your applications are using most of the CPU (or depending on the device driver's pre-emptability, it could be the other way around, that the CPU simply wouldn't be as available to your CPU-hungy SSL server as it's busy with the RAID).
It may be a matter of little import to 99% of the population, but it is relevant to the dicussion, and it's an extreme case that highlights the norm well. It also means that a 2.2 kernel that's been running for years on a IBM Quad Pentium with mixed cpu frequenices (I had one of these once, 2x 133 and 2x 166, quite silly design), you're covered with Linux - and again if you had problems just try getting Microsoft to help you debug it, especially for free.
I'll agree with you there. But then again, I don't use Redhat, and I don't subscribe to applying the standard commercial support model to Open software.
IMHO, if a company goes Open Source (as in using it, not writing it), part of their support plan should be to hire their own in house Open Source Support person(s). These people are internally responsible for maintaining any open soruce the company uses, and forwarding trouble requests that are real out to public newgroups and maintainers and whatnot. The person should have basic open-source hacking skills (be able to apply patches and edit trivial source code), and know his way around the community. Ideally you might already have that person on your staff, but if not consider that person (or persons depending on the workload)'s salary to be your support contract feeds for your new Open vendor.
When you set things up like that, you don't have to worry about these issues. You've got it covered.
I'm annoyed that moderators have called me flamebait yet again for a valid opinion, and that the responders assume that I must not know what I'm talking about.
I'm just now going through QA testing on a commercial web application load-tested for 1000's of users, all highly secure, handling sensitive medical transactions. It backends to a complex postgreSQL database tracking user transactions and security audit trails, etc, etc...
It's well beyond a web banking interface or anything as trivial as that (referring to the other reply to parent). And yes, I can read my code after the holidays are over. The only practical consideration is that most of the world's web programmers are Java now, so if we ever sell the source/company nobody will buy it for fear of not finding an adequate person to maintain it perhaps. But as long as it's our company and we can hire replacement Perl programmers, it's all good.
2.0 is still a supported kernel release. If you have an issue, there's a maintainer out there supporting you. For that matter, all versions including 2.4 are still supported on a 386-25 with 16M of ram if you happen to have such a beast in working order. Given the timeframes, that would be equivalent to Microsoft still supporting customers that are running Win95 or NT3.51 on that same 386 today and on into the future. Not likely.
I don't need a diatribe on MVC or that whole list of blubber strapped to a bloated environment to write good web apps. Perl generating XHTML and CSS makes wonderfully simple and easy-to-use web apps for me.
Fucktard spelling nazi. Websters recognizes "guarantee" as well as "guaranty", which means in my typing haste I swapped the initual "ua" to "au", not a bad mistake at all, especially seeing as I don't give a shit about small grammar and spelling mistakes (see my journal). It has been my experience that the "ee" ending is used more commonly in the US. And don't bitch at me for being US-centric either, there's a US-centric population here, get used to it.
It's worse than that. If they root the webmail server (or a little more difficult if they just get the webserver UID), they can read the SSL traffic, including your passphrase. In short the only way to have securely encrypted email is to store the private key on your own private local machine - a webmail service simply cannot gaurantee you jack.
And I'd like to add that this last comment you made is getting a bit offensive now. In your world you're making a stupid comment about something fake. Over here in reality-land, you're talking about my future wife. Tone it down.
Troll and Flamebait moderations from the peanut gallery. Is anybody metamodding this crap? If you don't agree, post, don't abuse your mod provs. Everything above is either dead-on fact, or my arguably relevant opinion. It's not a troll, and it's not flamebait.
1. Buy Java for Dummies book, write a cute web applet 2. Get $100,000 job coding Java for some corporate application. 3. Watch your self-esteem fall through the floor over the course of 3 years at that job, from realizing that the only language you know sucks ass, your products are all bug-ridden and bloated, and your source-code is grossly inefficient and unreadable. 4. Quit job, become crack addict bum on downtown street that other Java developers at an earlier stage than yourself stare at and don't give money to. 5. In a drunked cracked-out haze, have a moment of Zen enlightenment, and dawn upon the reality of computers, unix, and all the better languages out there. 6. Clean up, move in with parents, learn , get a real job, feel good about your code, live happily ever after.
Putting layer-3 switching only (no pure L2 devices) all the way uot to the workstations is prohibitively expensive. Anytime you've got multiple L2 switches in a segment, you should have spanning tree turned on. Turning it off will seem like a gain, till some dumb user plugs two of your network connections into a 4-port hub under his desk and you start getting broadcast storms. Spanning Tree saves you from these types of disasters and a myriad of other possibilities.
Even Sun knows where the future lies. Maybe if the OpenBSD guys could get SMP working or something, someone might take them seriously. I still use OpenBSD for a firewall, but I'd rather have the OpenBSD guys auditing linux code instead, it would be effort better spent.
Heh, a freind of mine and I, about 8 years ago we had an x86 assembler programming contest between us. This contest was to reproduce a pager program under DOS (like the "more" command) that would take a filename argument and page it to the screen, one page per keystroke. He beat me just barely, the final numbers of bytes were like 97 and 102.
Slashdot Mirror
I'm using a small local provider that somehow escaped unscathed from the raping of most of the local providers here (they all pretty much went out of business or were bought by large national/regional shops). I believe they charge us about US$200/month to get 1 IP address and 1 100mbit ethernet port. They have DS3 connectivity, and we get charged extra if we go over 10GB of traffic per month. They give us a small locked cabinet (1/4 of a rack) that could probably fit about 10U of equipment. They have multiple grid feeds from the power company to reduce the likelyhood of total outage, but you're on your own for supplying a small UPS for your equipment. Prices go up for more GB/month and/or more IPs and ethernet cables.
All of these points on RMS are true, but please also remember that everyone has their place. A strong grassroots movement like GPL/OSS stuff doesn't only need polished presenters, they also *need* fringe lunatics. RMS and his kind are a driving force, they're the fringe that helps offset the other side and helps the rest of us to find a happy medium.
From the article:
I don't think even many developers find Bugzilla to be a simple interface. I would find it easier to type in SQL queries againsta bug database manually than use the Bugzilla web interface.
I'm a big fan of the notion that there's a distinct if somewhat grey line between Invention and Discovery, and that only Invention should be patentable. Discovering a new species of mouse in the wild does not give one the right to patent it. Inventing a new species of mouse through genetic manipulation does, although it raises ethical questions, especially if applied to a more emotionally developed mammal like a dolphin, a dog, or a human.
First off, they've failed to note that some of their contestants are in fact just IDE controllers, with the RAID functionality implemented in the software driver (WinRAID, like WinModems), whereas others are Hardware. I don't know all four products well, so I'm unsure on at least one of them as to which are which.
They tested CPU utilization, and seperately various speed tests, but never a comprehensive "loaded system" test. As expected they ranked the Adaptec (a true hardware RAID) lowest, while ranking the WinRAID's higher. This couldn't be further from the real truth. Sure, the idle P4 cpu does a great job of fast software RAID compared to the embedded RAID ASIC on Adaptec's card. However, if you had a heavily loaded server machine, where the processors were loaded down doing other things (say SSL-encrypting for an secure web server), the machine with the Adaptec would trounce the others, as the RAID processing speed will not decrease while your applications are using most of the CPU (or depending on the device driver's pre-emptability, it could be the other way around, that the CPU simply wouldn't be as available to your CPU-hungy SSL server as it's busy with the RAID).
It may be a matter of little import to 99% of the population, but it is relevant to the dicussion, and it's an extreme case that highlights the norm well. It also means that a 2.2 kernel that's been running for years on a IBM Quad Pentium with mixed cpu frequenices (I had one of these once, 2x 133 and 2x 166, quite silly design), you're covered with Linux - and again if you had problems just try getting Microsoft to help you debug it, especially for free.
I'll agree with you there. But then again, I don't use Redhat, and I don't subscribe to applying the standard commercial support model to Open software.
IMHO, if a company goes Open Source (as in using it, not writing it), part of their support plan should be to hire their own in house Open Source Support person(s). These people are internally responsible for maintaining any open soruce the company uses, and forwarding trouble requests that are real out to public newgroups and maintainers and whatnot. The person should have basic open-source hacking skills (be able to apply patches and edit trivial source code), and know his way around the community. Ideally you might already have that person on your staff, but if not consider that person (or persons depending on the workload)'s salary to be your support contract feeds for your new Open vendor.
When you set things up like that, you don't have to worry about these issues. You've got it covered.
I'm annoyed that moderators have called me flamebait yet again for a valid opinion, and that the responders assume that I must not know what I'm talking about.
I'm just now going through QA testing on a commercial web application load-tested for 1000's of users, all highly secure, handling sensitive medical transactions. It backends to a complex postgreSQL database tracking user transactions and security audit trails, etc, etc...
It's well beyond a web banking interface or anything as trivial as that (referring to the other reply to parent). And yes, I can read my code after the holidays are over. The only practical consideration is that most of the world's web programmers are Java now, so if we ever sell the source/company nobody will buy it for fear of not finding an adequate person to maintain it perhaps. But as long as it's our company and we can hire replacement Perl programmers, it's all good.
See response to other comments above
2.0 is still a supported kernel release. If you have an issue, there's a maintainer out there supporting you. For that matter, all versions including 2.4 are still supported on a 386-25 with 16M of ram if you happen to have such a beast in working order. Given the timeframes, that would be equivalent to Microsoft still supporting customers that are running Win95 or NT3.51 on that same 386 today and on into the future. Not likely.
I don't need a diatribe on MVC or that whole list of blubber strapped to a bloated environment to write good web apps. Perl generating XHTML and CSS makes wonderfully simple and easy-to-use web apps for me.
Fucktard spelling nazi. Websters recognizes "guarantee" as well as "guaranty", which means in my typing haste I swapped the initual "ua" to "au", not a bad mistake at all, especially seeing as I don't give a shit about small grammar and spelling mistakes (see my journal). It has been my experience that the "ee" ending is used more commonly in the US. And don't bitch at me for being US-centric either, there's a US-centric population here, get used to it.
It's worse than that. If they root the webmail server (or a little more difficult if they just get the webserver UID), they can read the SSL traffic, including your passphrase. In short the only way to have securely encrypted email is to store the private key on your own private local machine - a webmail service simply cannot gaurantee you jack.
Yes, I did.
I did send it, check the mailbox
Did I say Playmate? get off it slashstalker
And I'd like to add that this last comment you made is getting a bit offensive now. In your world you're making a stupid comment about something fake. Over here in reality-land, you're talking about my future wife. Tone it down.
Still waiting for somewhere to send it, you dumb shit AC.
Oh fuck off loser. It was funny. And no, it's not from experience, I just made that up because I hate Java, in case you couldn't get that.
No, I don't know where to send it. Honestly I can't believe you're still hung up on it. Hurry up a post soe identifying info then jerkoff.
Troll and Flamebait moderations from the peanut gallery. Is anybody metamodding this crap? If you don't agree, post, don't abuse your mod provs. Everything above is either dead-on fact, or my arguably relevant opinion. It's not a troll, and it's not flamebait.
1. Buy Java for Dummies book, write a cute web applet
2. Get $100,000 job coding Java for some corporate application.
3. Watch your self-esteem fall through the floor over the course of 3 years at that job, from realizing that the only language you know sucks ass, your products are all bug-ridden and bloated, and your source-code is grossly inefficient and unreadable.
4. Quit job, become crack addict bum on downtown street that other Java developers at an earlier stage than yourself stare at and don't give money to.
5. In a drunked cracked-out haze, have a moment of Zen enlightenment, and dawn upon the reality of computers, unix, and all the better languages out there.
6. Clean up, move in with parents, learn , get a real job, feel good about your code, live happily ever after.
Putting layer-3 switching only (no pure L2 devices) all the way uot to the workstations is prohibitively expensive. Anytime you've got multiple L2 switches in a segment, you should have spanning tree turned on. Turning it off will seem like a gain, till some dumb user plugs two of your network connections into a 4-port hub under his desk and you start getting broadcast storms. Spanning Tree saves you from these types of disasters and a myriad of other possibilities.
Even Sun knows where the future lies. Maybe if the OpenBSD guys could get SMP working or something, someone might take them seriously. I still use OpenBSD for a firewall, but I'd rather have the OpenBSD guys auditing linux code instead, it would be effort better spent.
Heh, a freind of mine and I, about 8 years ago we had an x86 assembler programming contest between us. This contest was to reproduce a pager program under DOS (like the "more" command) that would take a filename argument and page it to the screen, one page per keystroke. He beat me just barely, the final numbers of bytes were like 97 and 102.