Or you could learn to use your accessibility settings.
remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Caps_Lock
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L
That's actually not the best way, because running it twice leaves you back where you started. And sometimes you do need to re-run it, like if you plug in a USB keyboard or Gnome decides that it knows better what mapping you want. If you're on Gnome, it's best to work with it, and set this in Keyboard Preferences|Layouts|Layout Options. A
There we go, a serious answer from a frivolous thread.
The truth is, the PRC is completely clueless about PR (public relations) and will continue to be roundly slaughtered in the court of public opinion because of this.
They're clueless about international PR. They manage the Chinese public's opinion very well. What we see as bad PR is partly that the message for China doesn't work outside China and partly that the government doesn't realize this and doesn't understand liberal culture.
If your date involved trying to play a movie on your computer.... you lost her before you even logged into the computer. (unless she's a computer geek, but then, she wouldn't have been frightened by the man page either)
My experience is otherwise. The only details I'll reveal are: Ubuntu, mplayer, and no glitches.
As Feynman said "For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." This was with regards to the Colombia disaster. Here was a case of faking up the science to support the conclusion that was wanted, which was that things were safe. Well, all that was for naught, as the reality was it was NOT safe and blew the fuck up.
There's a true genius if ever I saw one! Not only did he come up with a juicy quote like that, but it was about an accident that happened after his own death.
I don't see any need for exceptions because I can't find anything in RFC 1187 that we'd need to make an exception to.
I don't see any problem with MX records either. MX records exist precisely to solve this problem. The DNS tells you which server to send email to. That is, it delegates to a sub domain, if that's what you want. Nothing you do on your web server will break email.
Now, you may have services other than web and email, yes. And you may have some problem with routing by protocol. But, given that it isn't 1992 any more, and this web thing doesn't look like a passing fad, it makes sense to use the shortest domain name for the most used protocol. That does mean that the vast majority of "www" prefixes are completely redundant. But, hey, aren't people funny things?
Oh, Lordy, no replies to this so I'll be the one to go through it. I did, as it happens, read through the file in question. It shows that merging data from different academic projects with different source data and different analysis software, written by scientists, can be a real headache. Quite enlightening if you want to know how messy real science can get but nothing to do with a conspiracy to falsify global warming data.
What we're talking about is "data tampering". Remember that, children.
- "But what are all those monthly files?
I don't know. What are they?
DON'T KNOW, UNDOCUMENTED. Wherever I look, there are data files, no info about what they are other than their names. And that's useless " (Page 17)
So he has output files, and doesn't know where they came from. Somebody didn't document their code properly. Hold the front page!
- "It's botch after botch after botch." (18)
What is?
- "The biggest immediate problem was the loss of an hour's edits to the program, when the network died no explanation from anyone, I hope it's not a return to last year's troubles This surely is the worst project I've ever attempted. Eeeek." (31)
Maybe the network's shit. Irrelevant.
- "Oh, GOD, if I could start this project again and actually argue the case for junking the inherited program suite." (37) - " this should all have been rewritten from scratch a year ago!" (45)
Maybe the code's shit. Irrelevant.
- "Am I the first person to attempt to get the CRU databases in working order?!!" (47)
The database is a mess. Irrelevant.
- "As far as I can see, this renders the (weather) station counts totally meaningless." (57)
Right, the count of weather stations is meaningless. So we don't know how many individual weather stations are contributing to the data. That doesn't mean there's anything wrong with the data, let alone that it's been tampered with.
- "COBAR AIRPORT AWS (data from an Australian weather station) cannot start in 1962, it didn't open until 1993!" (71)
There you go, there's an error in the database. Do you think it was deliberately added by somebody not smart enough to check when the station opened? And this one mis-labeled data point from a weather station in Australia is responsible for the apparent trend of global warming? Really?
- "What the hell is supposed to happen here? Oh yeah -- there is no 'supposed,' I can make it up. So I have : - )" (98)
What's he making up? Temperature readings? The name of a weather station? Whether two different names refer to the same weather station or not? It's surely not as sensational as you imply.
- "You can't imagine what this has cost me -- to actually allow the operator to assign false WMO (World Meteorological Organization) codes!! But what else is there in such situations? Especially when dealing with a 'Master' database of dubious provenance " (98)
Yes, some stations are listed in the database without a code. The software uses the code as a unique ID. So each station needs to have one. If you don't know the right one, you add a false one. These are labels. We have falsification of labels, not data.
- "So with a somewhat cynical shrug, I added the nuclear option -- to match every WMO possible, and turn the rest into new stations In other words what CRU usually do. It will allow bad databases to pass unnoticed, and good databases to become bad " (98-9)
Yes, the database seems to be in a mess. Some weather stations are not labeled properly, and there may be duplicates. But the data are not falsified.
So give robots an inescapable urge to reproduce themselves.
What could possibly go wrong?
Bonus points for getting GConf to work with it.
In 1999 when I first tried *desktop* Linux (having used it as a server before), it was a piece of crap. A complete piece of crap. It shipped with NS4, which was a piece of crap. The font system was crap. The tools were crap (in the sense that very few of them had GUIs). The installer was crap. The hardware detection was crap. The video support was crap. Networking with Windows machines was impossible (Windows 2000 and NT4). The repository system was starting to take shape, but installing new software was a crapshoot at best (at least I learned how to install from source tarballs). Did you want sound? No problem, just download and compile ALSA!
Networking with Windows 2000 machines was certainly a tough proposition in 1999!
He has not acquired a fortune; the fortune has acquired him. -- Bion
