I liked Shrillary better back when she was letting interns do her real job for her.

That just shows that she knows how to delegate important tasks to someone competent to perform them - which is an important presidential qualification.

Scooter Libby was convicted on two counts of perjury, one count of obstruction, and one count of making false statements. ...

Hillary will likely get the same: no conviction for anything to do with missing emails.

But will she get penalized for the coverup, as Scooter Libby was? Wiping, rather than producing, the system disk sure looks like "one count of obstruction". (For perjury and false statements we'll have to wait for the mill to grind some more, but the TFA says it doesn't look good for her right now on those, either.)

You would get fired if someone outside sent non classified data to an individual inside ?
Thats what happened

No, that's NOT what happened. Hillary gave out her home-administered email address to her State Department contacts and they then sent email containing classified info, as she (did or should have) expected them to do.

This is more likely misdemeanor mishandling of classified information.

Which, you'll recall, is what they let General David Petraeus plea-bargan to when they canned and prosecuted him.

During his affair with his female biographer he had given her access to his classified email account - so they could exchange love letters in the "drafts" folder. They apparently did this in the hope of avoiding the creation of an archived email trail, which they knew would occur if they sent the mail but didn't know would also occur with the system backups of the drafts folder.

The "mishandling of classified info", if I understand it correctly, is because she could, in principle, have read his other mail. Just as anyone who participated in the administration of Hillary's private mail server or the network connection to it could, in principle, have read or copied the State Department related emails containing classified info.

the Emacs vs VI war is over (Emacs won)

Nope. B-)

When I got my first UNIX box, back in the '80s, it had two megabytes and did NOT have demand paging, which would have allowe a larger virtual image to run. That was too small to compile emacs. (The joke at the time was that the name was really an acronym for Eight Megabytes And Constantly Swapping. B-) )

So I learned VI. Then I used it VERY heavily for years, on the original conferencing system whose software was later ported to The Well. After that a number of editing idioms were "wired into" my hindbrain and I could do the things I wanted to do with text very efficiently with vi.

As machines improved I tried emacs several times. Each time I found that the stuff I depended on took about 1.5 to 3 times as many keystrokes. This was too much of a penalty to pay for the handful of features it offered.

At one point I considered going to it but running in a vi emulator mode and gradually migrating to native idioms. But I discovered that, kitchen sink that it was, it had TWO vi emulator modes, each with distinct deviations from vi (alias "bug sets"). With one vi emulator, even with substantial shortcomings, I might still have made the shift. With two there was no easy way to chose, so I didn't bother.

Now I'm using vim, which is close enough. One of my regular colleagues is an emaxian rather than a vithian and we get along just fine. B-)

Also: It's not clear to me which group should be handling this. It seems to be a conflict between how two projects downstream of the compiler itself are handling a global namespace.

I'd only expect the compiler guys to fix it if they decided the downstream stuff was a problem and pulled part of it into their own stuff to settle the matter.

Wouldn't it be easier to check your bugzilla ticket?

There were already several tickets out on it (and flames from the maintainers about duplicates) so I didn't file another. None of them seemed to indicate that anyone, let alone the core compiler crew, were intending to do anything abut it.

I was hoping someone more actively engaged in either reporting or dealing with the issue might happen to be participating here and care to chime in. B-)

Meanwhile, others should know that there IS (or, we can hope, WAS) an issue before they make plans to try to use the toolset for a new project.

Did they fix the conflict between gcc-multilib and gcc-arm-linux-gnueabihf?

Since Ubuntu Trusty was released, over a year ago, there has been a conflict between gcc-multilib (needed for building and running 32-bit application on 64-bit Intel/AMD architectures) and several cross compiler suites including gcc-arm-linux-gnueabihf (the cross-compiler suite needed for developing applications for ARM processors, such as those on the BeagleBones and many Internet of Things devices.)

This means if you want to do cross-development and you have a 64-bit machine running a 64-bit install and doing builds for itself for both 64 and 32 bit environments, or running some 32-bit applications, you can't just install the cross-tools from the repository and dig in. You need a separate machines for cross-development, or you need to take time out to do your own hacking of the tools.

I've looked around the net for solutions: The issue seems to be a disconnect between teams, primarily over conflicting uses of the symlink at /usr/include/asm. But I haven't found any clear description of how to work around this, nor has the problem been fixed in the repositories. After over a year I find this very disappointing.

Has this been addressed with this new release of the underlying compilers?

I went thru that exact same argument a number of years ago. The executives liked the look of the check boxes better and demanded I "make it work". Ugh.

It was almost as much fun as the idiots who insisted on the web page layout exactly matching -- fonts, graphics and all -- their magazine page layout. They ended up doing their web page as one big GIF with polygonal hot spots. You should have heard them scream when someone used a different resolution screen, or resized the browser on their oh-so-perfect page.

I am so glad I'm not in that business any more.

In the end, companies will do what's best for stockholders, which is immediate financial gains, which is bringing in cheap slaves.

No, in the end they'll do what is perceived, by upper management, as being best for upper management.

This includes immediate financial gains, or at least the appearance of them on the bottom line. But it also includes a smooth ramp-up of this bottom line: A sudden opportunity must often be delayed or abandoned, rather than seized, because it would lead to a spike-and-dip on consecutive quarters.

It also includes cutting expenses - particularly R&D and salaries - giving the appearance of building the future while abandoning it and gradually tearing down the present as well. The quality of the current output shrinks while future products aren't finished or don't work. But the bottom linen looks great for a couple years. The executive suite pats themselves on the back, collects their bonuses, and moves on to the next victim company. Their successors inherit the house of cards, and the blame when it collapses.

Great for the execs. Rotten for the stockholders. But a necessary skill for executives is the ability to convince the stockholders (and maybe some of the board members) that they're really doing great - until they've moved on to the next suckers.

I see a lot of hand waving about the temperature adjustments but I seldom see any serious scientifically rigorous challenge that addresses the reasons and methods that scientists give for making the adjustments.

Yep!

But doing science isn't free.

You're not going to get funding for that study from a government agency, or from a family trust managed by "progressive" administrators (regardless of the political position of the rich dead guy who established it).

If you take funding from, say, an oil company, or from a family trust started by a conservative that is somehow still managed by conservatives, any results not agreeing with the Global Heat Death scenario will be flamed as comparable to tobacco company sponsored lung cancer research - and can go whistle for a journal to publish them. (Isn't it amazing how research that DOES agree doesn't seem to have these problems, no matter how much the data has been "adjusted"?)

Other funding sources have similar issues.

So do you have any suggestions on where researchers can get funding for that study (and for all their future work in the field after it's done, if it doesn't agree with the dominant paradigm?)

Perhaps you have a few million to spare?

The National Sheep Association focuses more on the "penetration testing" side of security, if you know what I mean.

Yeah. I get enough disposable shit from the world every fall, when the trees dump all their leaves in my yard. And during spring and summer when after I cut it to an acceptable length, that Falk grad just comes back.

I've tried piling the leaves and grass up, along with things like the leftovers from my food and all the paper products I use, and it magically turns into dirt after a few months. I think it is the compost fairies and their workers, all those big, red works they send to sort thru the pile.

You're right. All my packaging and stuff should be shit that never goes away. They need to make like titanium paper or something that lasts forever. Fuck this disposable shit, I get enough of that from the world itself.

For the record, there actually was never a civil war where one side fought for the right to own white people under the banner of a "black power" flag. Also, there is not to this day (nor was there ever) a state that still flies that flag of white oppression.

For the record. the Civil War was not about one side fighting for the right to own black people under the banner of a "white power" flag, either.

The slavery issue was used in recruiting, convincing normally anti-war religious factions to drop their opposition (or even support it) under the "just war" doctrine, and eventually as a tactic near the end of the war to try to promote a slave revolt in the Confederacy. But the original fight (like the American Revolution, the "occupy" movement, and the RIAA/MPAA inspired draconian copyright regime) was about a crony capitalists / government axis using tariffs and laws to keep a large segment of the population as captive customers for overpriced monopoly products, suppressing both their trade with suppliers in other countries and their ability to make their own, lower-priced, replacement products.

It was the north's "1%" against the south-as-ghetto.

(Note that I say this as a descendant of a number of people who fought on the Union side.)

Unfortunately, the actual history of the conflict has been largely suppressed. IMHO the current anti-confederate-battle-flag move is both an attempt to finish off the suppression of the history of the conflict and to pre-emptively propagandize against any move by southern border states to take their own measures against what they perceive as a massive invasion across the southern border.

"Those who don't study history are doomed to repeat it." applies here - even if the history isn't studied because books about it are suppressed (e.g. removed from book stores and libraries because they contain the "evil racist flag").