Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment A simple solution? (Score 1) 264

Since they're attacking using high frequency sound, maybe have the machine emit some random noise in the same spectrum using its sound hardware while encrypting or decrypting or performing key generation. Wouldn't something like that jam such an attack (at least from a distance; if someone got microphones into your hardware that might be a different story)?

Submission + - Dice Ruins Slashdot (slashdot.org) 12

An anonymous reader writes: In an attempt to modernize Slashdot, Dice has removed everything that made Slashdot unique and worthwhile and has turned it into a generic blog site. User feedback has been unanimously negative, but this is to no avail, and users will have to head elsewhere for insightful and entertaining commentary on tech news.

Comment Re:Improvements (Score 3, Insightful) 38

I'm not disappointed in a slower release cycle. It should improve the quality of each release.

I think so too. I've been using openSUSE since it was SuSE Linux Professional and, before that, just S.u.S.E. Linux. They had an approximately annual release schedule for the newer, pre-Novell, versions and didn't try to stuff in every single newest thing going. I like to think this gave them the time to make sure that the vast majority of what they did ship worked well.

Unfortunately, a combination of changing to the "me-too" scheduling of releases (IIRC, the original discussion of the release schedule was calling for 6-month releases so they could be just like Fedora; after an attempt or two to maintain that, they switched to the schedule they're on now) and turning it into a beta-test for unfinished and premature software (systemd, pulseaudio, KDE 4.0, and the disaster that was online updates starting in the 10.x versions) have really degraded the distribution from what it once was.

From what I can see this moved the emphasis from shipping a distribution with what I'd call good "fit and finish", a good selection of software almost all of which worked correctly, no nasty surprises in the base functionality of the OS, etc., to trying to ship to a schedule, ready or not and ignoring anything that didn't get them there. I know the majority of bug reports I've made in newer versions got marked "wont fix"; not "can't duplicate" or "working as designed", but "won't fix", i.e. "yes, we know about it and know that it's broken but won't do anything about it". Not a good sign for a distribution that had been previously known for its functionality and stability.

I'm hoping that this serves as a wake-up call to the developers and that the suggestions coolo and others in the discussion are making will get them back toward shipping a distribution that's closer to what the old SuSE Linux was known for. What I'm seeing in the discussion is looking good so far.

Comment Because GNOME is too stupid and KDE is too slow. (Score 4, Interesting) 818

I completely gave up on GNOME back in the 2.x range as I saw features get continually moved, removed, or just made harder to configure. I loved KDE3 and tolerated KDE4 between crashes (now, thankfully, gone in newer versions) until I realized that as KDE versions got newer and newer, they also got slower and slower on my, admittedly aging, hardware. I've since switched to XFCE and haven't looked back. Much.

Security

Submission + - Henry Kissinger Gets TSA Pat-Down (washingtonpost.com) 1

TheGift73 writes: "Seems no one is immune from the tender mercies of the TSA pat-down. First, we learned that Sen. Dianne Feinstein (D-Calif.), the chair of the Senate Intelligence Committee, was subjected to a handsy search. And now we learn of the latest high-profile search-ee: former Secretary of State Henry Kissinger.

Yeah, the guy who was once an advisor to presidents, the one who helped negotiate the end to the Vietnam War...and, oh yeah, he’s got a Nobel Peace Prize."

Power

Submission + - Is the SATA power connector design flawed? 8

An anonymous reader writes: My computer caught fire today. I saw flames and smoke coming out. When I opened it I saw that the SATA power connector on the back of my samsung DVD drive was cooked. I looked around on the internet and found that I was not alone. A lot of other people have already reported their computer catching fire and almost all of them caught fire exactly the same way, the SATA power connector was burnt. In some cases it was an HDD and in others it was a DVD or blue ray drive but invariable the fire started at the SATA power connector.

Now I am wondering if the there is a fundamental flaw in the power connector design causing the fire? I am not sure where to complain or send feedback so that it gets aggregated and someone in the industry can take action and possibly work on changing the connector design. So I am writing on slashdot.

Slashdot Top Deals

"I've seen it. It's rubbish." -- Marvin the Paranoid Android

Working...