For such a large software company, their bug tracking is a joke. I reported an issue where the select by location tool was not selecting accurately, and in the end they admitted it was a known bug with high severity but no planned fix date. Now this makes me anxious because I am worried that there could be other bugs affecting the accuracy of my work, but the bug tracker does not let you see all the open bugs for a given product, nor can you subscribe to updates on existing bugs!
As a resident in Mr Tredinnick's ward I am looking forward to voting him out at the next election. He also voted against the legalisation of gay marriage.
It is also available on newer Blackberry phones running BB10 (i.e. Q5, Q10 and Z30).
I looked at Digg Reader and The Old Reader. In the end, I went with AOL Reader as it seemed to be more feature complete and usable. I think they have done a really good job with their feed reader.
It might be worthwhile to define some "reserved" TLDs for private use, as we have 10/8/, 192.168/16, 172.16/18 for IP addresses, so we can ensure that anybody using a reserved TLD does not have to worry about it being allocated in the future.
Does it absolutely have to be Apache, or will it work on lighttpd too? Your client looks great and I am keen to use it.
Since every machine was running the same software, that means every single machine was defective so the casino should be entitled to every single cent of winnings on these machines where double-up was turned on.
In an ideal world there would be a government-controlled specification that all medical software would have to adhere to, and there should be a requirement for interoperability so that data from one system can be exported to a common format and imported into another. Of course there will be changes to the specification over time which means you will always have to pay a vendor for updates (unless there was free open-source software available).
Wrong. "American" refers to anyone from the Americas, not someone from the United States of America.
One of the rules is that you are not permitted to sell third-level domains (3LD) underneath a second-level domain (2LD) in the proposed plan.
If DNS providers would provide a standardised API (or even allow standard dynamic updates with TSIG) it would make it a lot easier to use multiple providers. The two main problems I have come across are that the providers often do not let you add any NS records other than their own servers (so when a resolver caches the NS records and that provider goes down, it won't try using the other provider until the TTL expires), and updating records is painful because it involves logging into each of your providers websites to make the changes.
The book "SAP - A Map of The Minefield" by Stephen Birchall is a good read.
I don't see how they work out that it is 17938 infringements when they only set up one server, so they have only infringed once.
No longer an admin, but I have always given servers names based on their asset label, e.g. SV-0700543. The benefit of this is that the servers must be recorded in the asset register before they can be set up. When it comes to virtual machines I simply used a counter, e.g. VM-000001. The important ones (fsmo roles, database servers, app servers, etc) get friendly names with dns cname records.
Amarok dropped Shoutcast support in version 2.2 (October 2009) because of this.