Yeah, but PDAs, small form factors, and low power are the future.
This is more of a proof of concept than a product. This is what we will be seeing in the future, little boxes like these spread around the house. One runs the private PBX system and handles serving the family home page and mail, one handles the entertainment center, one monitors the utility systems, doors, fire alarm, etc.
Processors will be a mix, but mostly ARM and Power. MSWindows will be represented, if at all, by a descendant of the thin client MS is now building, running on either Linux or a BSD.
Okay, let's think this through very carefully. Bugs in userland do not result in xSODs. Bug's in userland that cause processes to gimmick up result in exceptions that get written to some log somewhere.
xSODs are bugs on the other side of the wall, the same side of the wall where the file system tables are kept, the same side of the wall where the swapping code runs, and where the tables that point to the segments of the swap files live.
MSWxxx is monolithic. There is one wall. Until very recently, MSWxxx did not observe the conflict between writeable and executable, and there is still a lot of hardware out there that doesn't support the new (xpSP2) enforcement.
MMUs protect RAM. They do not protect disk.
In the moments before an xSOD, the processor has been out of control in system state. Very likely, it has been in system state trying to execute data or garbage.
Do you really want to trust the MMU to protect swap space when the CPU is out of control in system state?
Replace "Klingon" with "man", and "human-betazoid hybrid" with "woman" in the above statement, and you've got a stereotypical heterosexual relationship.
And vice versa.
Which is probably the pith of the arguments presented by the homosexual movements.
But also, conversely, probably the entire reason for sex.
(I say as my wife expresses disgust that I would be reading/. and laughing about this Star Trek thread.)
But Safari isn't intended to run in X11
on
Safari vs. KHTML
·
· Score: 1
X11 and Aqua are not compatible. Complaints that Apple's patches don't work in X11, well, okay, it's understandable to complain, but it's not reasonable to demand. You'd be asking them to make Aqua into another flavor of X11, and there are good technical reasons they shouldn't.
As a matter of personal opinion, I would suggest that assigning a liaison engineer to help move code between the two forks (and help weed out the code that doesn't move) would be mutually beneficial. I think Apple is being shortsighted if they don't do it.
But armchair quarterbacking never gets the job done.
Competing for the majority desktop, yes, but with whom are the competing? malware?
Perhaps the idea is that if enough companies come out with stores that compete with iTunes, there will be some some of critical mass and some sort of chain reaction.
Heh. Chain reaction.
No, this is primarily to distract us from writing our congresspeople about realstinkingIDiotcards.
But one question for all of you who assert science has all the answers, what was before the big bang?
In the end, we choose a place to end the recursion. Some find God there, some find random chance. The funny thing is that we basically all of us worship whatever we find there.
Worship? WORSHIP AND SCIENCE DON'T HAPPEN IN THE SAME HEAD!!!!!!!!!!
yeah, right.
But ending the recursion is the wrong answer. It does not make things simpler. The are no turtles under the earth.
Get lucky in getting the defacto industry leader to choose your product.
Lie, and bribe others to lie about your product being fit for the application.
Lie and bribe others to lie about your product being the standard.
Dump to undercut the competition. When the competition goes to the dumping model in defense because the courts will take too long, use kickbacks, bribes, rebates, etc. to push your product. If dumping still doesn't work, bribe the police to look the other way and send some muscle around.
When people complain, say it's "only software".
Microsoft's business model will catch up with them, but as long as we roll over and let them run their "business", we pay the consequences as well.
heh. Yeah, I know it's hard to read, I just forgot I had used the HTML Formatted.
Anyway, yes, the only thing I can think to do is have the user chose his own latinized domain name.
The registrar might provide a dictionary of suggested translations and a list of suggestions that haven't already been taken. But the customer would have to choose the actual latinization.
However, if they are going to hide the.cn from those who access within China, that would make it rather awkward to map the TLDs to the latin/English equivalents.
Slashdot Mirror
and what i want to know is the meaning of HR744, section 2.c.
See section 5, limitations.
Yeah, but PDAs, small form factors, and low power are the future.
This is more of a proof of concept than a product. This is what we will be seeing in the future, little boxes like these spread around the house. One runs the private PBX system and handles serving the family home page and mail, one handles the entertainment center, one monitors the utility systems, doors, fire alarm, etc.
Processors will be a mix, but mostly ARM and Power. MSWindows will be represented, if at all, by a descendant of the thin client MS is now building, running on either Linux or a BSD.
haven't received reports on?
It's not the times it works I'm worried about.
On the other hand, "works well enough to sell this year" has been Microsoft's motto for a long time.
{shrug/}
So, what you're suggesting is that the Apple IV should have had a 68008? With a software emulator for the 6502?
Or that Apple should have sold a Model of Macintosh with one of the numerous AppleII/6502 emulators bundled?
That might have worked.
Okay, let's think this through very carefully. Bugs in userland do not result in xSODs. Bug's in userland that cause processes to gimmick up result in exceptions that get written to some log somewhere.
xSODs are bugs on the other side of the wall, the same side of the wall where the file system tables are kept, the same side of the wall where the swapping code runs, and where the tables that point to the segments of the swap files live.
MSWxxx is monolithic. There is one wall. Until very recently, MSWxxx did not observe the conflict between writeable and executable, and there is still a lot of hardware out there that doesn't support the new (xpSP2) enforcement.
MMUs protect RAM. They do not protect disk.
In the moments before an xSOD, the processor has been out of control in system state. Very likely, it has been in system state trying to execute data or garbage.
Do you really want to trust the MMU to protect swap space when the CPU is out of control in system state?
And vice versa.
Which is probably the pith of the arguments presented by the homosexual movements.
But also, conversely, probably the entire reason for sex.
(I say as my wife expresses disgust that I would be reading /. and laughing about this Star Trek thread.)
Dang, now I have to break out links so I can post with two browsers at the same time.
/. didn't make me wait two minutes.
Well, I could have done that if
Heh.
Okay, back to work.
Dang, now I've got to break out links so I can post with two browsers at the same time.
of course, when the processor is out of control. (As in the moments before a xSOD.)
And, yeah, I can't tell my left from my right, either.
(Migi? Hidari? Iya, Hilary janeyah. MUGI!)
Miscalculated.
to the disk space reserved for swap?
X11 and Aqua are not compatible. Complaints that Apple's patches don't work in X11, well, okay, it's understandable to complain, but it's not reasonable to demand. You'd be asking them to make Aqua into another flavor of X11, and there are good technical reasons they shouldn't.
As a matter of personal opinion, I would suggest that assigning a liaison engineer to help move code between the two forks (and help weed out the code that doesn't move) would be mutually beneficial. I think Apple is being shortsighted if they don't do it.
But armchair quarterbacking never gets the job done.
are flash players.
Hmm.
Making apple cider?
You can get music anywhere. Apple competes with radios, CDs, antique tape decks, vinyl, not to mention mp3 and microsoft.
microsoft competes with, uhm, microsoft. and itty-bitty-teensy-weensy bit players like Linux and Apple.
And not praising wma to high heavens is somehow bashing microsoft?
IE?
Latest service packs?
No Linux? No BSD? No MacOSX?
Competing for the majority desktop, yes, but with whom are the competing? malware?
Perhaps the idea is that if enough companies come out with stores that compete with iTunes, there will be some some of critical mass and some sort of chain reaction.
Heh. Chain reaction.
No, this is primarily to distract us from writing our congresspeople about realstinkingIDiotcards.
Hang your flags at half mast, upside down.
Hide your guns where you can get them.
I guess somebody takes the time to tighten up your internet settings.
Our maybe you just haven't noticed when you weren't prompted in a theoretically "safe" zone.
But I agree, somebody's copying cool features without thinking.
a flame fest.
But one question for all of you who assert science has all the answers, what was before the big bang?
In the end, we choose a place to end the recursion. Some find God there, some find random chance. The funny thing is that we basically all of us worship whatever we find there.
Worship? WORSHIP AND SCIENCE DON'T HAPPEN IN THE SAME HEAD!!!!!!!!!!
yeah, right.
But ending the recursion is the wrong answer. It does not make things simpler. The are no turtles under the earth.
Microsoft, MPAA, and RIAA.
Get lucky in getting the defacto industry leader to choose your product.
Lie, and bribe others to lie about your product being fit for the application.
Lie and bribe others to lie about your product being the standard.
Dump to undercut the competition. When the competition goes to the dumping model in defense because the courts will take too long, use kickbacks, bribes, rebates, etc. to push your product. If dumping still doesn't work, bribe the police to look the other way and send some muscle around.
When people complain, say it's "only software".
Microsoft's business model will catch up with them, but as long as we roll over and let them run their "business", we pay the consequences as well.
the answer would be yes, no, or it used to be.
When you're talking about software, "adequate" is huge praise.
Microsoft Office's greatest claim to usefulness is that it is inadequate in so many areas.
heh. Yeah, I know it's hard to read, I just forgot I had used the HTML Formatted.
.cn from those who access within China, that would make it rather awkward to map the TLDs to the latin/English equivalents.
Anyway, yes, the only thing I can think to do is have the user chose his own latinized domain name.
The registrar might provide a dictionary of suggested translations and a list of suggestions that haven't already been taken. But the customer would have to choose the actual latinization.
However, if they are going to hide the
No manual entry for flamebait