Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Introducing the programme in the UK (Score 1) 171

I'm UK based, and our only medical marijuana programme is the use of the synthetic variants such as Marinol, which doesn't do anywhere near as good a job of relieving pain. It's a Class-B drug here, so it's not technically illegal to prescibe it as a doctor as it does have medicinal value, but I imagine there are other regulatory roadblocks to doing that. Which is a shame, because I know people who have tried Marinol for their pain and found it wanting, but when introduced to a vaporiser and some good bud they can get a few hours relief. When you can see a cancer patient smile because they've attenuated their pain without having to reach for the opiates, it just beggars belief that the UK government won't try something like the approach they use in some US states. Hell, the UK government even admits they grow some good shit for research purposes.
Patents

Submission + - IBM Wants Patent for RegEx SSN Validation

theodp writes: "What do you get when you combine IBM contributors with the Dojo Foundation? A patent for Real-Time Validation of Text Input Fields Using Regular Expression Evaluation During Text Entry, assuming the newly-disclosed Big Blue patent application passes muster with the USPTO. IBM explains that the invention of four IBMers addresses a 'persistent problem that plagues Web form fields' — e.g., 'a social security number can be entered with or without dashes.' A non-legalese description of IBM's patent-pending invention can be found in The Official Dojo Documentation. While IBM has formed a Strategic Partnership With the Dojo Foundation which may protect one from a patent infringement lawsuit over validating phone numbers, concerns have been voiced over an exception clause in IBM's open source pledge."
Networking

Submission + - Documenting a network

Philip writes: "I was appointed as a network manager to a barely functioning MS-based network three years ago. Since then, I've managed to get it up and running — even thriving — but have been guilty of being too busy with the "getting things done" side of networking to document the changes and systems that are put in place. Now I look back, I realise that there is a lot of stuff that I've done and if I get hit by a bus or throw in the towel for any reason I'm leaving behind a network that requires some significant expertise to run and I am worried that I'm the only one that will ever know how it works. Ultimately, this won't be a good reference for me if they are forever trying to work out technical details for years to come. It's likely that I would be replaced with someone with less technical expertise (read "cheaper") and so the document needs to have all sorts of details that outside consultants could understand too (no, I don't want to be the outside consultant either...).

Are there any good templates out there for documenting networks? Has anyone done it before and have some experiences to share? What did you wish your predecessor had written down about a network that you inherited?

Thanks!"

Comment aaah (Score 1) 16

Just read a little more. Wasn't aware that simcard technology isn't being used in these phones. That certainly makes it difficult to remove the network lock. Damn, you guys have it bad over there for phones. You get screwed on prices, coverage, and now services it seems.

Slashdot Top Deals

Radioactive cats have 18 half-lives.

Working...