As you most likely purchased the game second hand the activation code would indeed be consumed. The activation key is for one time use only and if you wish to play SimCity you would need to purchase the game yourself, from your local retailer or from
i bought the game from a person but sai he never used it and when received the game it was still in is original packing. when I go to install the redeem code sais is already been use. How is it posible if the game is new
If you cannot find the serial number, or you have deleted the email, you can find your code in your Order History by going to Origin > EA Account and Billing... > Order History or directly by clicking My Account.
A digital code will be sent to your email address which you will then be able to redeem in Origin. Then you can just download, install and enjoy your new game! You can find more specific instructions under Code Activation Guide.
Which just goes to show how hard it was to do before PulseAudio. I did per application volume control with a nasty hack in asound.conf to set up a default PCM with a softvol control named using an environment variable. Not trivial, the way it is in PulseAudio, but not impossible either. Similarly, using some nasty hacks with the copy and route plugins, you could make ALSA redirect streams between devices. Again, not nearly as easy as it is in PulseAudio, but it works.Socket activation is explicitly modelled on the inetd way of working (where a socket is passed to a newly started daemon) - again, not made as simple as it is by systemd, but quite possible before. Poettering: systemd for Administrators, Part XII Posted Jan 22, 2012 10:21 UTC (Sun) by hongli (guest, #75254) [Link]
For example the old init system uses shell scripts all over the place. The problem with shell scripts is that *a lot* of operations require a fork() and an exec() which makes things less efficient than they should be. Reading the contents of a PID file Exec cat. Sending a signal to a process Exec kill. Each of those commands in turn execute a lot of redundant code, like loading glibc, allocating memory, etc. A lot of people usually respond to this by saying \"who cares, I boot my system and never shut it down\". I'm baffled by their apparent ignorance of (or indifference to) desktops, laptops and mobile devices. Poettering: systemd for Administrators, Part XII Posted Jan 22, 2012 13:37 UTC (Sun) by farnz (subscriber, #17727) [Link]
Absolutely - I can't think of a Poettering project that isn't a net improvement on what came before. But that's the reason Poettering comes in for criticism; he's not doing stuff that couldn't be done before his project started, so when you hit one of the bugs (either in his code, or merely exposed by his code), it's all too easy to go \"Poettering sucks! systemd/avahi/PulseAudio/ifplugd/project-of-the-day doesn't work nearly as well as sysvinit/dynamic-dns/asound.conf-of-doom/ethtool-based-hacky-shell-script/thing-that-did-this-before because its bugs make it completely unusable!\".It doesn't matter that once the bugs are fixed, the project is a net improvement on what came before; it doesn't even matter that there already improvements if you don't trip over the bugs. What the complaining users see is \"it worked before, now it doesn't. Must be Poettering's fault, as that's the last thing I changed\". Heck, to the complaining users, it doesn't even matter that they've seen a pile of other small improvements from Poettering's code, as they've hit a bug, and all they can see is \"it worked before PoetteringProject, it doesn't work now\". Poettering: systemd for Administrators, Part XII Posted Jan 22, 2012 18:39 UTC (Sun) by hongli (guest, #75254) [Link]
I try to build as much \"reputation management code\" in my software as possible so that people don't blame me for problems I'm not responsible for. For example one of the software that I write is a web application server. When something goes wrong, my software tries very, very, very hard to explain to the user what went wrong, why it went wrong, where it went wrong, and how to fix it. To further reduce user annoyance, the message is displayed in an aesthetically pleasing way. It's all psychology you see - if people see a beautiful error message page then they're less likely to be annoyed or to feel anxious and blame all the problems on my software. My software also actively works around broken environments. Some people set their ulimit stack size to 80 MB by mistake. Because my software is heavily multithreaded, they would exhaust their virtual memory if they launch my software, or they would wrongfully conclude that my software is a memory hog because the VSIZE is large. To prevent that kind of things I force a thread stack size of 128 KB in my software.I realize that this sounds like a huge pain in the ass and that from a technical point of view you shouldn't need all these things. But we're working with people here so I think these things are very very important. Poettering: systemd for Administrators, Part XII Posted Jan 22, 2012 19:38 UTC (Sun) by obi (guest, #5784) [Link]
If my experiences are typical, part of the reason for less noise than you might expect is that the people who make lots of noise are generally not the people who make the decisions; a big clue is when someone says \"[projectname] is about choice\" - those people tend to make noise rather than help get things done. As long as the distro guys who actually make decisions don't push code before it's ready for prime time, the noisemakers don't see the code in unfinished buggy state.With PulseAudio, it got pushed as a default to users when it wasn't quite stable enough to be useful. The noisy people got compelled to use it even though it didn't always work perfectly, and thus generated lots of noise.With systemd, they deliberately delayed pushing it as a default (it was supposed to land for Fedora 14, but missed), because it wasn't quite ready. By the time systemd was pushed as a default, it was actually quite good (and getting better all the time); as a result, the noisy people didn't have a huge amount to complain about. Poettering: systemd for Administrators, Part XII Posted Jan 21, 2012 17:18 UTC (Sat) by tetromino (guest, #33846) [Link]
On a repository based system you have an additional layer of people reviewing the software that you will end running in your machine. Part of the responsibility for the excellent track record of desktop Linux with regards to malware is by this layer of people. A tightly controlled App Store, like Apple's, has a similar effect, but having access to the source code makes repositories much more effective. Yesterday... Posted Jan 24, 2012 15:43 UTC (Tue) by dgm (subscriber, #49227) [Link]
Most of them. Some are coded incorrectly and don't react well to the different theme, but they are rare. And till Windows Vista most had trouble with DPI changes. But then, again, to properly support different DPIs in Linux you need to use modern libraries which are in constant flux, ages-old stable ABI approach will only give you bitmap fonts.
The whole story makes me kinda sad: Linux desktop developers (GNOME, KDE and others) do enormous work to make desktops pretty - and the goal here is, apparently, to attract users. Yet they do everything they could to make absolutely sure there will be no hundreds of thousands of pretty apps for said desktop - which makes the rest of their work pretty pointless. Why They are intelligent, absolutely not crazy people so... why I just can not understand.I can't speak for those developers, but I'll take a guess: They only care about source-code compatibility (at most). With free software, the developers feel they can break the ABI without a second thought because you \"just\" recompile. And you can break the API with only a passing thought because developers are supposed to keep up.I do agree that this is a large barrier to proprietary Linux desktop apps. But I disagree that it makes the Linux desktop technically inferior to the Windows desktop. It hurts the marketing and it annoys proprietary developers, but those are political issues, not really technical ones. GNOME, KDE etc. ABI breakage Posted Jan 24, 2012 0:28 UTC (Tue) by dlang (guest, #313) [Link]
This is in stark contrast to the server offerings on Linux, where aside from directory services and management the Linux/FOSS offerings are leading edge in terms of quality, features, and performance.An SDET is a QA engineer; Software Development Engineer in Testing (compared to a regular dev at MS, called an SDE). The folks who write tests, test harnesses, etc. A lot of folks in the Windows OS SDET groups are actually Linux nerds, surprisingly enough (surprised me, at least), and Cygwin and various Linux/UNIX tools play a pretty big role in their work. You're not likely to hear that advertised much, naturally. :)XBL is the Internet services division for XBox (XBox Live) and Games for Windows Live. It's a tiny division compared to the Windows Desktop division. And, btw, not recognizing what XBL is puts you at odds with about 60% of normal consumers, which is just another tiny bit of evidence that Linux folks are completely out of touch with what normal non-nerd computer users care about or do with their PCs and electronics. Meeting computer geeks who aren't also gamers is so \"weird\" feeling. It's like meeting cinema buffs who don't know what Netflix is. :)Also, hating Microsoft had nothing to do with hating QA. I've met very, very few Microsoft employees who hate the company in any way; the few I have met were mostly just unhappy with how various dev divisions at Microsoft are still using the waterfall dev model (mostly the business software groups; one might note that SCRUM was invented at Microsoft in the Visual Studio division). Microsoft treats its people very well, theres a lot of really cool people who work there, lots of great parties and social events... honestly most people outside the F