> you would be using an AT&T cell phone, and > paying $30/hr to call the next state
\sarcasm{Gosh, why not $30/MINUTE?!? They are a monopoly, right? Why not $300? What's that? Because AT&T couldn't make money because no one would use it?}
> you would be running windows, because the PC 99 > specs would have limited the ability to run > linux
Actually, I'm writing this on a DEC Alpha -- amazing that these exist, seeing as Intel has/had that monopoly in the 80's, eh?
> If anyone mentions morals, I tune out.
Your (plural) apathy isn't an effect of bad ethics, it's a cause of it, first.
I think it _is_ NT's fault, tho, else why reboot? Just kill the process, and a decent OS will reclaim the memory. If your OS doesn't, then it's only doing half of its job!
For kernel developers, uptime is rarely an immediate personal issue, as they frequently boot their new code and reset the jiffy counter.
Because of this, there were occasionally bugs in handling the overflow back to zero. There were no showstopper bugs, mind you. At worst, you'd have to reinitialize the code (unload and reload a module containing bad code).
However, being clever people, for several versions of the kernel we set the jiffies to MAXINT-6000, so that jiffies would overrun after about ten minutes. The bugs that existed were actually debuggable, and most (if not all) of jiffy-related bugs were cleaned up.
Since then, it's become more of a visible issue, and code that is submitted is prolly checked for clean handling of jiffy overflow.
You might have a version that has buggy code, but it certainly won't Micros~1 on you.
Slashdot Mirror
Er, it's the idea of guilt that is arbitrary. How can the Sherman Act destroy your business?
If you charge prices ``too low'' (undefined), you're ``anticompetitive,'' and the gov't destroys you.
If you charge ``too high'' (also undefined), you're ``price gauguing'', and the gov't can destroy you.
If you charge the same, you're ``price fixing'', and it's _your_responsibility_ to prove otherwise, and the gov't can destroy you.
Thus is the nature of antitrust law. You can't know you're guilty until the trial's over.
> you would be pumping gas from a Getty Station,
Perhaps. Perhaps not.
> you would be using an AT&T cell phone, and
> paying $30/hr to call the next state
\sarcasm{Gosh, why not $30/MINUTE?!? They are a monopoly, right? Why not $300? What's that? Because AT&T couldn't make money because no one would use it?}
> you would be running windows, because the PC 99
> specs would have limited the ability to run
> linux
Actually, I'm writing this on a DEC Alpha -- amazing that these exist, seeing as Intel has/had that monopoly in the 80's, eh?
> If anyone mentions morals, I tune out.
Your (plural) apathy isn't an effect of bad ethics, it's a cause of it, first.
A corporation _is_ its owners, who do have rights.
>Claiming enforcing laws passed long ago against a
>corporation as being wrong, then, is an insult to
>anyone who has really been wronged.
I don't mind if ``anyone'' feels insulted at the idea that others are wronged.
No, that's ``wrong'' as in morally wrong. The Sherman Antitrust Act is arbitrary law.
http://microsoft.aynrand.org/
http://www.moraldefense.com/microsoft/
I dislike Microsoft and its products, (and haven't used any in the past few years, IIRC), but this
case is a disgrace for me, as an American.
Your solution (cluster machines) is sensible.
I think it _is_ NT's fault, tho, else why reboot? Just kill the process, and a decent OS will reclaim the memory. If your OS doesn't, then it's only doing half of its job!
For kernel developers, uptime is rarely an
immediate personal issue, as they frequently boot
their new code and reset the jiffy counter.
Because of this, there were occasionally bugs in
handling the overflow back to zero. There were no
showstopper bugs, mind you. At worst, you'd have
to reinitialize the code (unload and reload a
module containing bad code).
However, being clever people, for several versions
of the kernel we set the jiffies to MAXINT-6000,
so that jiffies would overrun after about ten
minutes. The bugs that existed were actually
debuggable, and most (if not all) of jiffy-related
bugs were cleaned up.
Since then, it's become more of a visible issue,
and code that is submitted is prolly checked for
clean handling of jiffy overflow.
You might have a version that has buggy code, but
it certainly won't Micros~1 on you.
- chad
This suit is wrong, for only one good reason, AFAICT: Trademarkable spelling.
The name in question is like any stupid spelling of a word -- Fruit->Froot, Clean->Kleen, Happening->Happenin'.
If a name is spelled incorrectly, then it becomes a proper noun, not a word that has meaning that can be translated into another language.
-chad
I've heard _nothing_ from them. Had anyone heard anything about Friday allotments??? (cc me directly, pls.)
Don't you people know anything!??