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


Forgot your password?

Comment Oracle wanted it to die (Score 1) 82 82

I was a big SPARC fan. I've still got two old Sun Netra sparc64 1u servers in my basement. I used to have used sun workstions, and even had MidnightBSD running on some Sparc64 systems early into my project.

The problem is that when Sun was sold to Oracle, they closed up patches, documentation on old hardware and anything useful for supporting old Sun hardware. That meant that the used market dried up. They then put out only super expensive systems and got rid of workstations. This caused developers to lose access to modern systems and most ports of Linux and BSD gave up over time. Now you have to run Solaris on Sparc and you pay a lot of money to do so.

It's just not worth it. Solaris has lost momentum due to these moves. Everyone moved to Linux or BSD. It's over guys. Just give up and push Oracle databases on Linux and Windows now.

Submission + - AMD's $550 Radeon R9 Fury On Linux Competes With $200~350 NVIDIA GPUs->

An anonymous reader writes: Earlier this month AMD released the air-cooled Radeon R9 Fury graphics card with Fury X-like performance, but the big caveat is the bold performance is only to be found on Windows. Testing the R9 Fury X on Linux revealed the Catalyst driver delivers devastatingly low performance for this graphics card. With OpenGL Linux games, the R9 Fury performed between the speed of a GeForce GTX 960 and 970, with the GTX 960 retailing for around $200 while the GTX 970 is $350. The only workloads where the AMD R9 Fury performed as expected under Linux was the Unigine Valley tech demo and OpenCL compute tests. There also is not any open-source driver support yet for the AMD R9 Fury.
Link to Original Source

Comment Re:But don't equate coding with comp-sci (Score 2) 132 132

Not only is there concern about that, who is teaching it? Districts don't have the money to get someone with a CS degree that is also willing to give up $50,000 a year to teach it instead. You're going to get the math teacher with some intro course a large company wrote a text book on. It's going to be bad.

Where is the money for the computers, software and teachers to do this?

Comment Re:The problem is systemic (Score 1) 36 36

Without knowing the GS/contractor divide at OPM, it's hard to say who is ultimately to blame. If OPM gave carte blanche to the contractor, the latter is generally the one at fault. If the government micro managed the contract and ignored suggestions, the blame is back with them.

Comment Re:Flawed statistics are flawed (Score 1) 114 114

The other difference is that Yahoo and Google have locked down email so that legitimate email isn't getting delivered. Now other providers are following the same rules. When you block a lot of email, it never gets delivered.

There are certain people I just can't mail anymore.

Comment Re:Good (Score 1) 628 628

Windows XP prior to SP1 had a very nasty update. Even SP1 had some bugs when it first came out. Vista had a few bad drivers that weren't 64bit clean that caused me total data loss. (File system corrupted)

It has happened in the past. Microsoft has a good track record with recent updates. I'd also point out that as recent as the Windows 8.1 update failed because of my MOUSE DRIVER. Granted, I had a gaming mouse with firmware for profiles and LEDs but still...

Comment Re:That is the problem. (Score 1) 30 30

That's not true. Script kiddies have to wait for someone to write a tool for them to use to actually exploit it. It takes a few days for these things to get out there in mass.

When an upstream has a security advisory, I have to run around in circles to get the patch out to my users and then they have to run around patching everything. That's just how it works. When you don't get enough information to make a decision, it makes it hard to know if you should risk patching. For some folks, they're in system freeze for a busy time of year or have a lot of other risks by patching something. You really need as much info as possible to make this decision sometimes.

For example, at work we have a vendor who recently told us they had a huge security issue. Anyone on the internet can change a setting and that in turn can change a link to an admin area of our product. The catch is that we never use the admin link it changes. They threatened to drop support of their product for us if we didn't patch immediately. However, we don't use that admin link. Further, the number of users in our org that uses it are on one team of 10 people. A huge risk in general does not mean a huge risk for one org.

The OpenSSL team did the right thing on their end, but there are two dimensions to vulnerabilities, the severity in terms of the software and the number of users impacted. The latter in this case, was small.

Living on Earth may be expensive, but it includes an annual free trip around the Sun.