While you do bring up some interesting points, I haven't changed my Windows machines since 98SE. They run pretty well. Most of the desktops get shutdown each night anyway, so trying to maintain an uptime measured in weeks, months, years isn't a priority. I'm not going to upgrade to 2000, XP, Longhorn, etc. The next time these machines get an update, they're going to Linux, and that's only when I know that things are going to work right. Also, I have the benefit of working for a smaller family-owned business which should be more flexible about switching.
Also, I was just pulling numbers for market share out of my ass. The point was, Linux isn't a major market share holder yet, and until it becomes one, the Linux community will have to play by the current rules, no matter how unfair they may seem. And those rules are, more people are running Windows in some variant than are running Macs or Linux systems.
Finally, and just being nitpicky, but I find it hard to take someone seriously who feels compelled to abbreviate Microsoft (M$)
And when Linux holds the market share, and innovates new ideas and concepts, it will be up to Microsoft to play catch-up and maintain compatability. However, until that point comes, the Linux community will have to play catch-up, and there's really no way around that.
Now the question should be, do you want 80% of your IT environment to depend on a product from a company that behaves this way?
My answer is, No. That's why we've been slowly moving things like purchasing, work orders, etc. to a web-based system running on Linux. The Windows machines can use it just fine, and once everything's running on the servers, it won't be a problem to migrate the desktops over to Linux and be free of Microsoft.
Ok, there's plenty of posts that say "just get rid of Windows" as a solution to the interoperability problem. However, if I'm generous and give Apple and Linux each 10% of the desktop market, that still leaves 80% to MS. You don't throw out a product with 80% of the market just because you can't get your minority system to work correctly with it.
When will Linux take over? When it interoperates with everything, so that people can get used to using it. Then, you can slowly migrate systems as needed, instead of going all out with one system, then having to re-train all your workers, and iron out all the bugs at once.
While your idea about BSD being "safe" from SCO because of a lack of popularity is interesting, I think that the real reason is that, BSD derived from a different code base than that of AT&T, which IIRC became System V Unix. Since BSD isn't derived from the AT&T code, things like the SMP etc. will be handled differently, and thus not infringe on SCO's IP.
Of course, I'm no Unix historian, so I could be wrong.
Ok, you have SCO attacking Linux over licensing code. You have this small company (but backed by larger companies SONY and Phillips) attacking Microsoft. Where does someone turn to get away from all the legal hassles?
Ignoring the trolls, would a *BSD system be better off, because SCO doesn't seem to be claiming anything related to BSD.
Also, could this be a nail in the coffin of DRM? Or, would MS just pay the license fee, and jack the consumers for it anyway?
I wonder if they will count the costs of the commercials in the money they are loosing every year to piracy...
They wouldn't have before you suggested this.
All kidding aside, doesn't the government count the money spent on drug education as part of the costs of drug use? So I would guess that, yes, the MPAA will count the costs of these commercials as piracy costs. Maybe they'll get Dreamworks/SKG to do the commercials, just to inflate the numbers.
Although they didn't specify which files or lines of code are the problem, they were pretty specific that it was NUMA, SMP, and RCU that was introduced by vendors in the 2.4 kernel.
So, on my single processor box, I'm never going to be in "trouble" with SCO, because I'm not using any of those features, right?
Ok, one other poster suggested C and making a portable build. I would suggest something like Python. Look at the success of Bittorrent, for example. It runs on all the major platforms, it's consistent in its usage on all platforms, and Bram only really has to maintain one branch of code.
Any particular reason that it couldn't be ported over?
<voice char="Forrest Gump">Stupid is as stupid does</voice>
Seriously, I understand how the trolls have multiple accounts, get points in one, post crap in another, and use the first to mod up the second. However, the editors have unlimited points, along with the rest of the "legit" moderators, and comments like that shouldn't stay at +2 informative for that long.
Thanks for the concern, but don't worry about my karma. I've said it before, I have plenty to burn. I just wish moderators would actually read the comment before going "Look, it's really long, therefore it must be at least interesting"
One, is the MAME version accurate enough to have this "kill-screen"?
Two, does anyone know of a cheat to get to this "kill-screen"? After all, I doubt I'd ever play for 2 hours just to get there, but I would be interested in seeing what lies ahead for the poor guy.
Linux Trace
Trollkit (LTT): http://www.uwsg.iu.edu/hypermail/linux/kernel/0204.1/0832.html
I know it's a typo, but that would make slashdot much more interesting, wouldn't it?
Re:Why use Amplifiers?
on
dB Drag Racing
·
· Score: 2, Informative
Surely, if they're after max volume, then they don't care about distortion. I'd be tempted just to use solid state relays to drive the speakers with a square wave. That saves lots on cost/complexity/power-disspiation, leaving more for the speakers. (You could also modify the square wave using n batteries in parallel, switched in for slightly different fractions of the waveform - this would get more power into the fundamental frequency.)
In fact, that's exactly what many competitors do. They overload the input to the amplifier to produce square waves at the tuned frequency of the enclosure/vehicle.
As for the battery thing, many multiple serial/parallel setups in use, along with external regulators, etc. to keep the voltage level up while banging.
For those who have never seen it, The official dB drag website. Wayne Harris, they guy who started this, used to work for Rockford Fosgate.
Slashdot Mirror
While you do bring up some interesting points, I haven't changed my Windows machines since 98SE. They run pretty well. Most of the desktops get shutdown each night anyway, so trying to maintain an uptime measured in weeks, months, years isn't a priority. I'm not going to upgrade to 2000, XP, Longhorn, etc. The next time these machines get an update, they're going to Linux, and that's only when I know that things are going to work right. Also, I have the benefit of working for a smaller family-owned business which should be more flexible about switching.
Also, I was just pulling numbers for market share out of my ass. The point was, Linux isn't a major market share holder yet, and until it becomes one, the Linux community will have to play by the current rules, no matter how unfair they may seem. And those rules are, more people are running Windows in some variant than are running Macs or Linux systems.
Finally, and just being nitpicky, but I find it hard to take someone seriously who feels compelled to abbreviate Microsoft (M$)
And when Linux holds the market share, and innovates new ideas and concepts, it will be up to Microsoft to play catch-up and maintain compatability. However, until that point comes, the Linux community will have to play catch-up, and there's really no way around that.
My answer is, No. That's why we've been slowly moving things like purchasing, work orders, etc. to a web-based system running on Linux. The Windows machines can use it just fine, and once everything's running on the servers, it won't be a problem to migrate the desktops over to Linux and be free of Microsoft.
Ok, there's plenty of posts that say "just get rid of Windows" as a solution to the interoperability problem. However, if I'm generous and give Apple and Linux each 10% of the desktop market, that still leaves 80% to MS. You don't throw out a product with 80% of the market just because you can't get your minority system to work correctly with it.
When will Linux take over? When it interoperates with everything, so that people can get used to using it. Then, you can slowly migrate systems as needed, instead of going all out with one system, then having to re-train all your workers, and iron out all the bugs at once.
Naked Sunbathing
While your idea about BSD being "safe" from SCO because of a lack of popularity is interesting, I think that the real reason is that, BSD derived from a different code base than that of AT&T, which IIRC became System V Unix. Since BSD isn't derived from the AT&T code, things like the SMP etc. will be handled differently, and thus not infringe on SCO's IP.
Of course, I'm no Unix historian, so I could be wrong.
Ok, you have SCO attacking Linux over licensing code. You have this small company (but backed by larger companies SONY and Phillips) attacking Microsoft. Where does someone turn to get away from all the legal hassles?
Ignoring the trolls, would a *BSD system be better off, because SCO doesn't seem to be claiming anything related to BSD.
Also, could this be a nail in the coffin of DRM? Or, would MS just pay the license fee, and jack the consumers for it anyway?
They wouldn't have before you suggested this.
All kidding aside, doesn't the government count the money spent on drug education as part of the costs of drug use? So I would guess that, yes, the MPAA will count the costs of these commercials as piracy costs. Maybe they'll get Dreamworks/SKG to do the commercials, just to inflate the numbers.
Or FreeBSD, OpenBSD, or NetBSD would all be options, considering they came from the Berkeley BSD base of code, not the AT&T System Unix code.
So, on my single processor box, I'm never going to be in "trouble" with SCO, because I'm not using any of those features, right?
Ok, one other poster suggested C and making a portable build. I would suggest something like Python. Look at the success of Bittorrent, for example. It runs on all the major platforms, it's consistent in its usage on all platforms, and Bram only really has to maintain one branch of code.
Any particular reason that it couldn't be ported over?
It's getting them to stop that's the problem.
[rimshot]
But hey, it's progress, right?
About your sig: how does bash.cx relate to bash.org?
See previous /. article for more information
<voice char="Forrest Gump">Stupid is as stupid does</voice>
Seriously, I understand how the trolls have multiple accounts, get points in one, post crap in another, and use the first to mod up the second. However, the editors have unlimited points, along with the rest of the "legit" moderators, and comments like that shouldn't stay at +2 informative for that long.
Thanks for the concern, but don't worry about my karma. I've said it before, I have plenty to burn. I just wish moderators would actually read the comment before going "Look, it's really long, therefore it must be at least interesting"
What's funnier is that I get a -1 Flamebait for pointing out the fucked up moderation.
Oh well. I have karma to burn. Bring it on bitches
WHO THE FUCK MODERATED THIS AS "INTERESTING"? DID YOU READ IT? -1 TROLL, -1 OFFTOPIC, -1 FLAMEBAIT
Posting logged in, with bonus to point out the egregious nature of this posting
One, is the MAME version accurate enough to have this "kill-screen"?
Two, does anyone know of a cheat to get to this "kill-screen"? After all, I doubt I'd ever play for 2 hours just to get there, but I would be interested in seeing what lies ahead for the poor guy.
Wouldn't multi-player Unreal II be UT2003?
Mom: Quit playing that game and go do your homework
Kid (using sword attached to TV): n0 w4y! SuX0r! ph34r m3!! (Kid begins swinging sword violently at mother)
Alternate scenario: mom grabs sword attached to TV and whips kid's monkey a$$ with it
I know it's a typo, but that would make slashdot much more interesting, wouldn't it?
In fact, that's exactly what many competitors do. They overload the input to the amplifier to produce square waves at the tuned frequency of the enclosure/vehicle.
As for the battery thing, many multiple serial/parallel setups in use, along with external regulators, etc. to keep the voltage level up while banging.
For those who have never seen it, The official dB drag website. Wayne Harris, they guy who started this, used to work for Rockford Fosgate.
I was really (and foolishly) hoping that no one would post this. Oh well.