Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Nice, just had
Snipes was one of the two huge time killers for me too... what a classic game.
I'm betting Seagate dropped some serious $AU to get this passed.
I run a computer lab at the University of Washington. There's a few reasons why computer labs won't go away soon for us:
1) Expensive software - if we did away with labs students would have to buy software such as SPSS, and they would need it only for a few classes. We don't think its reasonable to expect students to incur this added expense.
2) Specialized hardware - Our video editing suites will always require video editing hardware and DVD/Blu-Ray readers and burners, and having nice scanners and color printing is an added incentive to come in to the lab.
We do make allowances for students with laptops though. I've made spaces for laptops where I've added power strips and networking points for those that don't use the 802 network. We're also looking at adding groupware to our lab to make it easier for groups to work and collaborate.
We also run our help desk out of a lab and we'll help students with their laptop issues. We allow students to come and eat and relax in this lab too. We've found that this atmosphere encourages students to come back to a lab environment.
My usual check list for this is:
1) Check the hard drive, SMART, or manufacturer diagnostics
2) Get the manufacturer diagnostics, and run a full hardware validation
3) If all is clean, check for things recently updated - a bad update may be clogging things
4) Check your anti-virus/anti-spyware software. Sometimes they can switch into extra-paranoid mode and slow things down horribly.
Assuming that you have spare drives, you can use mirroring as a backup solution.
I had a huge database that I was was responsible for and we'd lock the database and split the mirror, take the drive offsite.
If the system died, we had a spare drive available for immediate recovery.
It's all in how you do it.
This appears to be an extraordinarily spectacular attempt in suicide, lest the apperent new domain holder, a Mr. Martin Rusteberg of Germany, happens to hold prior rights in the string "google". A quick search revealed that there are no trade marks registered in Germany (https://dpinfo.dpma.de/protect/mar.html), with OAMI with respect to European trade marks (http://oami.europa.eu/CTMOnline/RequestManager/) nor with the WIPO with respect to so-called international trade marks that might have been extended to cover Germany (http://www.wipo.int/ipdl/en/search/madrid/search
This might be different though, should the current domain holder turn out to have any other kind of rights in the string "google" himself, e.g. using it as a company identifier prior to Goolge Inc.'s market entry in Germany.
Unlike other TLDs, the German registrar DENIC e.G. (http://www.denic.de)does not provide a dispute resolution procedure. That means that the possible kidnapping of the domain will be subject to German jurisdiction. That means that while, for example, the ICANN Uniform Dispute Resolution Policy (http://www.icann.org/udrp/) allows for "soft arguments" to be brought forward and domains to be transferred directly if there is no response by the defendant, arbitration in front of a German court could turn out to be more difficult that one might, at first sight, expect.
Whilst there can be little doubt that google would eventually succeed in regaining the domain due to it's overwhelming fame, the path to victory could turn out stony.
There is juristdiction by Germany's Federal Court of Justice that accepts that in a conflict of prior rights, the rights of a party that has what has been described as "an absolute reputation", prevail (BGH, Urt. v. 22.11.01, I ZR 138/99 — shell.de, http://netlaw.de/urteile/bgh_13.htm).
Still, it is rather unlikely that this concept would be sufficient to allow Google Inc. to achieve an injunction under German law. This is due to the requirement that no injunction must anticipate the final decision — which would be the case if the current domain holder was forced to cancel the domain.
By the way: under German law, no right holder can ask for a domain to be transferred. It has to be cancelled and can then be re-registered by the rights holder. Google Inc. will have to ask for a so called dispute entry by the registrar Denic e.G., which will bar the domain from any further transactions, and then go to court really, really quickly.
Depending on whether or not the current registrant has any prior rights, this might turn out as a finacial suicide or the easiest way to earn real money without any effort at all — if, which is not unlikely, Google Inc. decides to cut things short and buy the new registrant out. Which, I have a tinkle, may have been the idea in the first place.
Still, this is high rolling: from both a legal and a financial point of view, it would have been less risky just to rob a bank. It's probably just that geeks aren't any good at this sort of thing, in contrast to the fine detail of domain registration policies...
For further information on German internet law, visit http://www.netlaw.de/ or just ask: firstname.lastname@example.org.
Christian Franz, LL.M.
(Attorney at Law)