Forgot your password?
typodupeerror

+ - Oracle finally release Java MSI file.

Submitted by nosfucious
nosfucious (157958) writes "Oracle Corporation, one of the largest software companies and leading supplier of database and enterprise software quietly started shipping a MSI version of their Java Runtime (https://www.java.com/en/download/help/msi_install.xml). Java is the worlds leading software security vulnerability and keeping up with the frequent patches of nearly a job in itself. Added to this is the very corporate (read: Window on a large scale) unfriendly EXE packaging of the Java RTE. Sysadmins around the world should be rejoicing. However, nothing from Oracle is free. MSI versions of Java are only available to those with Java SE Advanced (and other similar products). Given that urgency and frequency of Java updates, what can be done to force Oracle release MSI versions publicly (and thereby reduce impact of their own bugs and improve Sysadmin sanity)."

Comment: Re:Iris or RFID (Score 1) 125

by Z00L00K (#48473189) Attached to: Ask Slashdot: Best Biometric Authentication System?

Reading the brain waves of a person may be better, harder to fake at least.

But a smart card with PKI and pin code authentication for every access needed will go a long way. If it's a facility with extreme security measures also add guards at checkpoints and make sure that some accesses requires counter-signed authentication.

Comment: Re:In Finland (Score 1) 501

by Z00L00K (#48468145) Attached to: Ask Slashdot: Why Is the Power Grid So Crummy In So Many Places?

I live in Europe and lumber is the most common building material around here.

Even at a dozen houses per square mile it's still paying off to have the services underground. When you go below one household per square mile then it may be a point in not burying the lines.

Especially since the service lifetime for buried lines is averaging 50 years.

Comment: Re:Aerial or underground ? (Score 1) 501

by Z00L00K (#48467837) Attached to: Ask Slashdot: Why Is the Power Grid So Crummy In So Many Places?

Just remind them their responsibility to provide telecom service for emergency purposes. It may even be in their contract that they have to ensure a certain level of service that they can't back out from. The price they did put up was just their way of trying to say that they don't want you as a customer but they couldn't cancel your contract.

Comment: Re:Aerial or underground ? (Score 5, Insightful) 501

by Z00L00K (#48465609) Attached to: Ask Slashdot: Why Is the Power Grid So Crummy In So Many Places?

No - it's not even a question. Bury the lines and you will remove a large number of causes for power outages.

Even more important - realize that each outage costs money for the community. In the long run buried lines will save money - even if you are in an area where the ground is filled with rocks.

Comment: Re:In Finland (Score 5, Informative) 501

by Z00L00K (#48465589) Attached to: Ask Slashdot: Why Is the Power Grid So Crummy In So Many Places?

Similar in Sweden, where I live there have been maybe 5 outages the last 15 years, none of them long enough to create any problems aside from having to set the clock radio again.

And we have underground wiring. Areas with above ground wiring sees more outages.

This is also what annoys me whenever I have been visiting the US - the air is filled with wires high and low, which definitely destroys the scenery of the otherwise picturesque towns that are common in New England among other places.

+ - It's Not Developers Slowing Things Down, It's the Process->

Submitted by Anonymous Coward
An anonymous reader writes "Software engineers understand the pace of writing code, but frequently managers don't. One line of code might take 1 minute, and another line of code might take 1 day. But generally, everything averages out, and hitting your goals are more a function of properly setting your goals than of coding quickly or slowly. Sprint.ly, a company than analyzes productivity, has published some data to back this up. The amount of time actually developing a feature was a small and relatively consistent portion of its lifetime as a work ticket. The massively variable part of the process is when "stakeholders are figuring out specs and prioritizing work." The top disrupting influences (as experienced devs will recognize) are unclear and changing requirements. Another big cause of slowdowns is interrupting development work on one task to work on a second one. The article encourages managers to let devs contribute to the process and say "No" if the specs are too vague. Is there anything you'd add to this list?"
Link to Original Source

Can't open /usr/fortunes. Lid stuck on cookie jar.

Working...