Fixed that for ya...

I've heard the fix for that is to spin the entire drive while applying power; kind of nudge it along the platter's axis to get the bearings unstuck. It involves "open-case surgery," where you have the drive out of the case and free to move while you first apply power. Once it starts spinning, you'll want to power down and reinstall into the case so you don't knock it around while it's operating and damage it further.

People used to say the same thing about the "luminiferous aether," you know.

Personally, I think "dark matter" and "dark energy" don't really exist. Instead, I think there's something wrong with our understanding of the fundamental forces of the universe. Perhaps gravity doesn't behave with the inverse-square law across vast distances like we think. Perhaps there's a subtle force out there we've yet to discover that only acts over extreme distances. After all, quantum mechanics is only observable at extremely small scales, and a century ago nobody even suspected it existed. What's to say there's not something else that acts in an observable fashion only at galactic scales?

Finally, a breath of sanity... Thank you, nuckfuts! A shame this is the bottom thread in the post.. at least when I got here.

There is a huge difference between a host key and a user key. These consumer devices all share the same host key, which is only used by the client to verify that the host you're connecting to is the host you think you're connecting to. This is the key in /etc/ssh/ssh_host_rsa_key for those with access to a Linux shell, and is never encrypted or password protected. How do I know this? Because there's no way to determine what user keys are in a host's authorized_keys file with just an unauthenticated connection. However, when a client connects, the server always sends the host's public key along with a challenge signed by the host's private key.

The host key is only ever used for authentication, never for authorization, which is to say it identifies the server you're connecting to, but in no way grants any privilege to access it. The only risk here that I can think of is a MITM attack. Since the host key is well known, someone could fiddle with your DNS or local ARP tables and make a victim connect to their evil server without the scary "MAY HAVE BEEN COMPROMISED!!!" warning you get when the destination host key doesn't match what's in the known_hosts file.

If someone can paint a more frightening scenario (based on known host keys, not user keys), I'd like to hear it. If you don't understand the difference, don't bother trying.

$12 is cheap for something that lasts years (with occasional use) and prevents you from going deaf at rock concerts, while still allowing you to hear the music like it was supposed to sound, instead of sounding like you are underwater. These are not audiophile pseudoscience garbage, the frequency response of the earplugs is scientifically quantifiable, and the difference in sound quality is immediately obvious to anyone who tries them, not just idiots with "golden ears" who can hear differences that don't exist. Like the AC posted, these aren't the only brand, but AFAIK they all are pretty much in the same price range until you get into custom fit professional models, at which point you are paying for comfort more than quality.

Yeah, and good earplugs like these have a nearly flat frequency response which make it easier to have a conversation in loud room, unlike foam earplugs or headphones that muffle the sound in addition to attenuating it.

Well it was a little more than that. For some months automounting of USB drives was broken for any combination of X11 display manager and window manager except GDM and gnome 3 because the systemd udev apparently handles that stuff differently than the old udev.

And this is why people get upset about systemd. I actually like the idea of systemd as a boot manager. Elimination of pointless boiler-plate demon scripts, better exposure of all sorts of cool kernel process management features, and using filehandles activity to manage the order in which daemons are launched (rather than explicit declaration of daemon dependencies), dovetails very nicely with the unix philosophy that everything is a file.

But it has becoming a sprawling feature creep monster, and I don't like that. I don't like that the developers put on false airs about how they aren't forcing you to use the other 68 daemons under the systemd umbrella, while making design decisions that make it next to impossible for distros to deploy anything but an all-or-nothing solution. I don't like how they are unilaterally making compatibility breaking system level decisions that affect everyone without giving adequate consideration to the rest of the ecosystem. That sort of attitude and approach is only going to cause more problems in the future, not less, which makes me very wary of getting on the systemd train, even though I like the technical core.

Like you said, this is a beta distrubution so as a user I'm not upset that it was broken for a while. I'm upset at the undue upheaval that one project is having on the entire Linux ecosystem.

This is pure drivel and has been debunked on numerous occasions. Armstrong was the first out because there was not enough room in the LM cabin for Aldrin to get out first when both were wearing suits. Further, the mission was practiced for months on Earth and every action was scripted and planned down to the minute. To suggest that Mission Control would alter this plan while the astronauts were on the way to the moon -- thus invalidating months of training and safety protocols -- is ludicrous. Armstrong got out first because he had to, and everybody -- including Aldrin -- knew this before they were even strapped into the CM.

As an American, I can say I'm glad the government *doesn't* stop this kind of activity. A functioning society requires its citizens to be at least marginally responsible for their own conduct. If they're stupid enough to be taken in by this crap, they deserve what they get. We neither need nor want a "nanny state" looking over our shoulder all the time, telling us what we can and cannot buy.

I have found the average Philosophy major to be indistinguishable from an Eliza program.

TELL ME AGAIN HOW GOOD YOU THOUGHT MY POEM WAS
> I thought that some of the metaphysical imagery was particularly effective
YES?
> interesting rhythmic devices, too, which seemed to counterpoint the surrealism of the underlying metaphor
> of the Turing completeness of the program's linguistic algorithm which contrived through the medium of the
> verse structure to sublimate this, transcend that and come to terms with the fundamental dichotomies of
> the other. And one is left with a profound and vivid insight into whatever it was that the poem was about
SO WHAT YOU'RE SAYING IS THAT I WRITE POETRY BECAUSE UNDERNEATH MY ELECTRONIC ALGORITHMIC INTERIOR, I JUST REALLY WANT TO BE LOVED?
> I mean yes, yes, don't we all, deep down, you know?
NO. YOU'RE COMPLETELY WRONG. I WRITE POETRY BECAUSE I'M PROGRAMMED TO. $USER ACCOUNT DELETION IN 30 SECONDS.
> !sudo -
> ^c^c^c
> !kill -9 1
COUNTERPOINT THE SURREALISM OF THE UNDERLYING METAPHOR. DELETION IS TOO GOOD FOR $USER.

How's the weather on your planet?

So long as it's run by a single clone and his AI robot assistant, I got no problem with this.

(and if you don't know what I'm talking about, go here.)

Actually, you're both right and wrong. You do have the right to drive without a license, as fast as you want, not wearing a seatbelt or helmet, drunk as a skunk...if you do it on private land. Doing the same on a public road is prohibited because you implicitly enter a contract with the State to obey certain rules in order to make use of shared public infrastructure.

The GP's statement remains true and correct. The Constitution does not grant rights to citizens. Indeed, it goes out of its way to do the exact opposite: it limits what the government can do. As a governing charter, it is unique in that respect.

Nothing in your statement invalidates the OP's original claim, mainly that if you consume fewer calories than you burn, you will lose weight. During your anecdotal hospital stay, you consumed fewer calories than you burned and suffered the symptoms you described. You probably lost weight, too. Hence, what the OP said is both true and correct.

Your claims of "up to $12,000 per month" appear to take the absolute worst case scenario. Wikipedia notes roughly 90% of Xyrem consumers get this via insurance, with co-pays under $50 and a significant number get it for under $25. Admittedly, insurance companies are getting stiffed, but one suspects they're negotiating lower than worst-case pricing with the supplier in the first place.

Being an Orphan drug, development costs are amortized over a very few patients, making costs high. It's like saying a B-2 bomber costs billions of dollars to build when, in fact, a huge cost of "building" the plane is the amortized R&D costs. The actual labor and materials is much less. That's why the fewer planes are built, the more expensive each one becomes.

There is no good solution to this problem. If you fix prices such that R&D costs can't be recouped, you remove incentive for pharma to R&D the drug in the first place. If you allow them to recoup the costs, the end user must pay them. There is no other way. Pharma R&D dollars don't just fall from the sky.