When Linux was ported to Alpha (the first 'official' port, BTW), it ran into many problems because of certain assumptions made by developers when writing code for x86 that was then ported to the Alpha. The worst assumption was that an int is always 32 bits, and that it matches the length of a pointer.
On a 64-bit platform, where the ints are 32-bit, you'll lose the top 32 bits of a pointer if you try and cram it into an integer. Unfortunately, there's a lot of code out there that does exactly that.
Solaris is dead on the low end. Sun knows it, their customers know it. The only place where Solaris still has a spark of life is in medium-to-large servers, say 6800-to-E15000 level, and even then the lower end of that is being pounded into sand by IBM. Sun has to realize that it can't hold back the tide, but it seems that they've this weird King Canute obsession that forces them to keep on whuppin' that corpse, long after the horse has taken the Big Ride into the Sky (to mix a few metaphors).
Actually, they seem to be sitting on a fairly fat pipe - with 100+ comments on/., I was still able to get an average speed of more than 50KB/s - from Japan!
If SCO are thinking of going after other Linux suppliers such as Sun and Red Hat, then what really gets my goat is that SCO (in their former life as Caldera) would have been as much in violation of the UNIX IP as any of these companies.
Maybe we'll be treated to the sight of SCO becoming the first company to file suit against itself (yeah right...).
In actual fact, they are free for commercial use if you only have a single processor. It used to be that only non-commercial users were permitted to use the free release, but that changed a while back.
The flip side is that you have to pay if you're using it on a dual-CPU machine or better, even if you're a non-commercial user.
It's not uncommon for these standards to change quite broadly between late drafts and the final standard. That said, a firmware upgrade should be sufficient (as you mentioned).
...as "dilution of copyright". You either have copyright on a work, or you do not. It's like saying "reduction of pregnancy".
That said, you were probably thinking of trademarks. If Atari had Pacman trademarked (which is likely), then a clone or near-clone of it would indeed dilute the trademark.
The other possibility is that the graphics of the clones were so close to the original as to be seen as a copy, in which case they would have been in breach of copyright.
Same here, although I had it set to a more reasonable "reload every five minutes".
It bans by IP, so if you're reading from work it can be a bit problematic... they tell you to mail/. to get unbanned, but I have my doubts about their response time.
Your verious Cygwin stuff must be chewing up a *lot* of memory, because nothing else there should be causing a 256MB machine to get even close to chugging (except maybe Mozilla).
Notice the proprietary app I mentioned? It can peak at ~200MB usage.
Yeah, but you're probably comparing Windows to a Linux box running something like twm..
Not quite;) Sawfish + Mozilla + kterm * ~20 + Sylpheed + a few applets + a few other bits and pieces, and it rarely hits 50% memory usage.
IIRC, memory addressing. The earlier Macs used 24-bit addressing, which lead to some application programmers stuffing things (against the advice of Apple) into the top byte.
When the Macs switched to 32-bit addressing, these apps broke. To allow users to keep running them, Apple provided that switch.
Just thought you'd like to know - the word is spelled "steal".
Not to mention the plural of "apostrophe" being "apostrophes".
The irony, the irony...
Informative? HAH!
When Linux was ported to Alpha (the first 'official' port, BTW), it ran into many problems because of certain assumptions made by developers when writing code for x86 that was then ported to the Alpha. The worst assumption was that an int is always 32 bits, and that it matches the length of a pointer.
On a 64-bit platform, where the ints are 32-bit, you'll lose the top 32 bits of a pointer if you try and cram it into an integer. Unfortunately, there's a lot of code out there that does exactly that.
Solaris is dead on the low end. Sun knows it, their customers know it. The only place where Solaris still has a spark of life is in medium-to-large servers, say 6800-to-E15000 level, and even then the lower end of that is being pounded into sand by IBM.
Sun has to realize that it can't hold back the tide, but it seems that they've this weird King Canute obsession that forces them to keep on whuppin' that corpse, long after the horse has taken the Big Ride into the Sky (to mix a few metaphors).
Let me call "bullshit". If it's your boss or a client, you'll use polite language whether you're on the phone or talking to them face-to-face.
Actually, they seem to be sitting on a fairly fat pipe - with 100+ comments on /., I was still able to get an average speed of more than 50KB/s - from Japan!
Peter Ustinov rocked!!
Dear IBM,
Please spend the $US25.68 million it would require to buy out SCO, and then fire every single member of their management and legal department.
Thank you,
A Linux user.
If SCO are thinking of going after other Linux suppliers such as Sun and Red Hat, then what really gets my goat is that SCO (in their former life as Caldera) would have been as much in violation of the UNIX IP as any of these companies.
Maybe we'll be treated to the sight of SCO becoming the first company to file suit against itself (yeah right...).
Hogsheads! Hogsheads, I say!
Slight correction: GOemon's katana (the Zantetsuken [Iron-Cutting Sword]) is unable to cut one thing - konnyaku, a kind of jelly made from arrowroot.
Well, want to tell me what this part means?
Now you can use the Solaris[tm] 9 Operating System at home or at work
So, what work would you be doing that's non-commercial?
In actual fact, they are free for commercial use if you only have a single processor. It used to be that only non-commercial users were permitted to use the free release, but that changed a while back.
The flip side is that you have to pay if you're using it on a dual-CPU machine or better, even if you're a non-commercial user.
It's not uncommon for these standards to change quite broadly between late drafts and the final standard. That said, a firmware upgrade should be sufficient (as you mentioned).
It was in production. It got killed sometime around the end of last year, I think.
Gack. You're right, of course.
Let's see... where did I put that procmail recipe to send an automatic reply saying "Bugger off bloodsucking retards" to any mail from bsa.org?
Thanks for the thoughtful reply. Much appreciated.
...as "dilution of copyright". You either have copyright on a work, or you do not. It's like saying "reduction of pregnancy".
That said, you were probably thinking of trademarks. If Atari had Pacman trademarked (which is likely), then a clone or near-clone of it would indeed dilute the trademark.
The other possibility is that the graphics of the clones were so close to the original as to be seen as a copy, in which case they would have been in breach of copyright.
BBN is Bolt, Beranek and Newman, the consulting company that did the original networking implementation for ARPANET.
See this timeline for more info.
Same here, although I had it set to a more reasonable "reload every five minutes".
/. to get unbanned, but I have my doubts about their response time.
It bans by IP, so if you're reading from work it can be a bit problematic... they tell you to mail
I wouldn't call it bare bones - it does everything I require of it, and very efficiently ;)
Well, the D and the A are on either side of the S, and the N is on the bottom row next to the M.
Your verious Cygwin stuff must be chewing up a *lot* of memory, because nothing else there should be causing a 256MB machine to get even close to chugging (except maybe Mozilla).
;)
Notice the proprietary app I mentioned? It can peak at ~200MB usage.
Yeah, but you're probably comparing Windows to a Linux box running something like twm..
Not quite
Sawfish + Mozilla + kterm * ~20 + Sylpheed + a few applets + a few other bits and pieces, and it rarely hits 50% memory usage.
Oops, forgot some:
- Word
- Excel
IIRC, memory addressing. The earlier Macs used 24-bit addressing, which lead to some application programmers stuffing things (against the advice of Apple) into the top byte.
When the Macs switched to 32-bit addressing, these apps broke. To allow users to keep running them, Apple provided that switch.