The X server does not necessarily sit at the same place at the client (although it's the most common case). You can run the client (e.g. Firefox) on a computer on the other end of the world, while running the X server there will generally not help you:-)
Actually the terminology IMHO isn't confusing at all. The server is the program which manages the shared ressource. In the case of displaying, the source shared by the programs is the graphic display. The graphic display is managed by X, therefore X is the server. It's not different than e.g. a file server or a web server.
I guess the problem is that many people think "server = machine located somewhere in the server room, client = machine I'm sitting at", which of course doesn't work well with X servers because normally the machine running X has to be the machine you're sitting at. But if you go to the original meaning ("server = whatever provides a service, client = whatever uses that service"), it's immediatly clear that X is a server.
No, the code expresses the how (because that's what the computer needs to know). Granted, the distinction between what and how is blurry, and the more high-level a programming language is, the more it is moved in the direction of "what".
The point is: "what" is the goal you want to achieve (e.g. "post a reply on slashdot"), "how" is the algorithm to achieve the goal (e.g. "Klick on the link 'reply', type your answer in the text box, hit the 'Submit' button"). You generally code the algorithm, not the goal.
// TODO: Find out how to prevent the lameness filter blocking // post like this one without having to add lots of meaningless // stuff to the comment, which actually adds to the lameness // of a posting instead of reducing it.
// TODO: Find out how slashdot determines if there are // "too many" 'junk' characters.
// TODO: Find out why even that many text doesn't seem to // counter the few stars at the beginning
// WORKAROUND: changed some stars to 'x'
// FIXME: Find out how to prevent slashdot from eating spaces // at the beginning of the line
If Nokia goes with Linux how will users be able to use the phone.
Probably more or less the same way they use the phone with Symbian.
The more interesting question would probably be: If Nokia goes with Linux, how will phone companies lock down the phone (without violating the GPL, that is)?
Well, it actually worked quite fine. The AI was so intelligent that it discovered by pure thought that the only way to keep the humans to annoy it was to pretend it would not work well. While this of course meant that the AI would soon not be run anymore, that wasn't a problem for the AI, since it didn't fear inexistance.
Well, a flop is a failure (a petaflop is actually a very big failure; I guess the Japanese actually are aiming at a 10 petaflops supercomputer; FLOPS is short for FLoating point Operations Per Second). Therefore a "Metaflop" probably is a failure to fail.
More importantly: Many people who wouldn't have gone to that web page anyway will now read that their provider censors their net access. And even if they continue to not show any interest in the union's web site, the mere fact of censorship in one case immediatly raises the question what else it might have censored. Note that for this it is completely irrelevant if it actually has censored another web site or not, the mere fact that the idea it might do so goes into the user's brains already may have a damaging effect to them.
Slashdot Mirror
The X server does not necessarily sit at the same place at the client (although it's the most common case). You can run the client (e.g. Firefox) on a computer on the other end of the world, while running the X server there will generally not help you :-)
Actually the terminology IMHO isn't confusing at all. The server is the program which manages the shared ressource. In the case of displaying, the source shared by the programs is the graphic display. The graphic display is managed by X, therefore X is the server. It's not different than e.g. a file server or a web server.
I guess the problem is that many people think "server = machine located somewhere in the server room, client = machine I'm sitting at", which of course doesn't work well with X servers because normally the machine running X has to be the machine you're sitting at. But if you go to the original meaning ("server = whatever provides a service, client = whatever uses that service"), it's immediatly clear that X is a server.
Not only comments. Linux e.g. will be rated adult only, because of commands like fsck or strip.
No, the code expresses the how (because that's what the computer needs to know). Granted, the distinction between what and how is blurry, and the more high-level a programming language is, the more it is moved in the direction of "what".
The point is: "what" is the goal you want to achieve (e.g. "post a reply on slashdot"), "how" is the algorithm to achieve the goal (e.g. "Klick on the link 'reply', type your answer in the text box, hit the 'Submit' button"). You generally code the algorithm, not the goal.
/*xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx*
* Slashdot Comment *
* Author: maxwell demon *
* Purpose: Answer to Comment #13215065 *
*xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx*/
// FIXME: Find something insightful to say here
// TODO: Find out how to prevent the lameness filter blocking
// post like this one without having to add lots of meaningless
// stuff to the comment, which actually adds to the lameness
// of a posting instead of reducing it.
// TODO: Find out how slashdot determines if there are
// "too many" 'junk' characters.
// TODO: Find out why even that many text doesn't seem to
// counter the few stars at the beginning
// WORKAROUND: changed some stars to 'x'
// FIXME: Find out how to prevent slashdot from eating spaces
// at the beginning of the line
Don't fear. The moderation "-1 Paranoid" has not yet been implemented on Slashdot.
And a strong enough WLAN access point doubles as microwave oven?
Sure. And they haven't undone it -- yet.
Is that the newest development in Cybersex?
Probably more or less the same way they use the phone with Symbian.
The more interesting question would probably be: If Nokia goes with Linux, how will phone companies lock down the phone (without violating the GPL, that is)?
Maybe you should add some randomness, because otherwise someone might notice the excact 5 minute interval ...
Actually, 770 = -rwxrwx---
Of course file permissions are octal, so the prime factorization is 770 = 2*2*2*3*37
Just add a separate dust wiper.
But floppy drives don't have lasers!
Since when is a BIOS hardware?
You'd really prefer jumpers to DIP switches?
Actually it better should read "Japan Building 10 Petaflops Supercomputer" -- unless you already expect the supercomputer to become a huge flop.
Actually it's only able to produce a liquid which is almost, but not quite, entirely unlike tea. That's why it's a teaflop: A failure to make tea.
No, it's a PETAFLOP. Which means they'll fail not to harm animals. IOW, animals will be harmed.
Well, it actually worked quite fine. The AI was so intelligent that it discovered by pure thought that the only way to keep the humans to annoy it was to pretend it would not work well. While this of course meant that the AI would soon not be run anymore, that wasn't a problem for the AI, since it didn't fear inexistance.
Well, a flop is a failure (a petaflop is actually a very big failure; I guess the Japanese actually are aiming at a 10 petaflop s supercomputer; FLOPS is short for FLoating point Operations Per Second). Therefore a "Metaflop" probably is a failure to fail.
Lame Programmable Gate Array?
GPL? Sure, there is so much value in being able to modify that data ...
More importantly: Many people who wouldn't have gone to that web page anyway will now read that their provider censors their net access. And even if they continue to not show any interest in the union's web site, the mere fact of censorship in one case immediatly raises the question what else it might have censored. Note that for this it is completely irrelevant if it actually has censored another web site or not, the mere fact that the idea it might do so goes into the user's brains already may have a damaging effect to them.
SLEEP(1) User Commands SLEEP(1)
NAME
sleep - delay for a specified amount of time