I wish I had mod points... I'd mod you up.

You're supposing that "Sony" is a single massive thing -- it's not. It's a conglomerate with many separate units that share relatively little other than a name and some discounts at the Sony Store.

Proof: The hackers have done nothing outside of Sony Pictures. If there'd been interoperability in the layer that they got into, we'd be seeing data from other "Sony"s out there as well.

SOE/SMSS/SNEI learned a lot after what happened in 2011. But a movie studio that deals mainly with corporate accounting to pay actors and production companies, and the occasional internal creative discussion, has a far different calculus to make on what to secure how than an Online Game company, or the one handling end-user billing (read: PCI) data for a storefront (PSN).

You're going to see a giant top down review come out of this, of course, but implementation will probably still be handled by individual corporate units to some extent.

Sony wasn't attacked because they were vulnerable or had particularly lax security, they were attacked for political reasons by a foreign power. I guarantee you that if Viacom has been producing The Interview they would have had a similar attack against them and would probably have fared little better.

One can imagine all sorts of objections to this ("I take too long", "I like staring at onions, but I don't like eating them", etc...), however a self-reported 98% success rate -- or at least, 98% of the time they end up with a pizza with their preferred ingredients and/or that they end up really liking -- would explain why Pizza Hut decided to roll ahead with this -- seemingly weirdly ahead of its time -- tech right away.

98% approval suggests that browsing an appetite are more firmly linked. If the numbers hold up outside of the focus groups and small study areas, I'd expect this technology to spread far and wide. Carls Jr. (a/k/a Hardee's) and Jack in the Box already use the kiosks in several locations here in San Diego; a camera and tracker wouldn't be that much of a step and could provide a quite different experience.

Eventually, we just keep rediscovering old concepts. Store-and-forward is basically Zone Mail Hour, and the first time I read about the Deep Space network concepts, all I could think of was interplanetary FidoNet, or WWIVnet.

This is one of the keys, and why the Lennart-hate is slightly more justified than the usual OSS spats.

Actively pushing to deprecate and then FORCE TO BE REMOVED initscripts from the Fedora RPMs was a way, similar to the integration of udev and GNOME, of forcing adoption and making migration back to other init systems difficult. This is classic embrace-and-extend, anti-competitive behavior except instead of Microsoft leveraging its weight, it's a developer making a power play.

As for how and why Fedora agreed to this... Well, there are a couple of different things at play. To some extent, it's felt like for a few years now the developers in the community have been pushing things and the sysadmins in the community have been busy doing their jobs or otherwise not paying attention. Suddenly Fedora is all about people running on their laptops and their little docker VMs with very little thought to the poor schlub who's dealing with a half-broken system at 3am in the morning. I can't say I blame Fedora specifically -- communities go awry all sorts of ways -- but I do wish RedHat had and has been taking administrator feedback into account with RHEL7.

Suffice to say, there's a lot of concern out there.

Please, please, PLEASE can the folks who are setting this up call it "Skynet"? Thanks.

Here, let me Google that for you

Also, from 2008 Davos:

Just how crazy is Al Gore? That was the question that popped, once again, into my brain as I read a January 24 Agence France Press news story out of the Davos meeting of business and political elite. Gore asserted that, “the North Pole ice caps may disappear entirely during summer months within five years”

I was instantly reminded of the story that ran in The New York Times in August 2000 claiming that the Pole was free of ice for the first time in 50 million years. It wasn’t, of course, because people who have actually been to the Arctic quickly noted that, in the summer, some ice actually does melt there. The Times retracted it three weeks later.

This kind of apocalyptic nonsense has been ratcheting upward ever since the new century began and my theory is that lunatics like Al Gore know that they are running out of time when it comes to imposing draconian restrictions on the use of every form of energy known to mankind. This is the purpose of the global warming hoax.

Given that developers are the new kingmakers, Red Hat needs to get out in front of the developer freight train if it wants to remain relevant for the next 20 years, much less the next two.

It's very hard to avoid a snarky response, but I'll try.

* Developers are not kingmakers
* Developers are not system administrators
* Developers don't understand operations
* Developers often don't understand scale engineering unless they can abstract it away by not thinking too hard about anything
* Red Hat Enterprise Linux (and its derivatives) are not intended to be shiny new, but to be reliable
* Use Fedora if you want bleeding edge, or re-package things yourself. RPMs aren't hard.

This. Actually, in RHEL/CentOS, you can simply run /etc/rc every minute via cron and it'll sync what's running with what's supposed to be, assuming things have been /sbin/service stopped. (And if they haven't been cleanly stopped, you need a specialized tool that understands how to *TEST* the service rather than rely on subsys.)

You can see this in Development vs Operations, Bay Area Startup Hipster Programmers vs System Administrators Who Have To Carry The Pager, Big Data vs Simpler Analysis, and a lot of other places in the industry right now....

There's an influx of talent that doesn't seem to understand the fundamentals of system architecture, or assumes they have all the answers and can/should hard-code them into the design, preventing "the Unix Philosophy" from being applied by the operator who's trying to deal with the crisis at 3 in the morning. "whatcouldpossiblygowrong", ergo I shall design this in C, and if you need more flexibility than I'm offering then You're Doing It Wrong.

What they don't understand is that they don't have all the answers... Nobody does. The only solution is to leave as much flexibility available as far down the stack as possible to allow the folks who have to deal with this (eg, system administrators) the ability to do their jobs. Replacing shell scripts with C code and the unix toolkit with monolithic binary blobs does not help the situation.

systemd does a few things right (cgroup management, for one), and promotes the state of the art in a few areas that probably only could be dealt with at the PID1 level... Also, as the original article admits, there's nothing inherently wrong with working to speed up boot times across the board. All of these things are irrelevant and outweighed by enforcing declarative styles on system configuration, and the sheer philosophical hazard of taking all these disparate functions and putting them into a program.

It makes absolute sense for Android, and perhaps an embedded system that just needs systemd and busybox. For a regular Linux userland, it takes us in the wrong direction.

Actually, you'd probably be committing a crime by not reporting there too... In both cases, if it could be proven you were aware of it. What you're talking about is the different levels of moral responsibility between the two cases.

To answer the OP, as someone who's had root at large positions... Assuming you are not intentionally spying on something or doing something at the behest of a security directory, legal, or other internal affairs-ish agency (which probably doesn't exist at your smaller company), you should treat everything as if you were a cop and you didn't have a warrant. You're not going on a fishing expedition, but if something is "in plain view", it is not inappropriate to use common sense and reason to consider that information now available to you and make choices accordingly. If that means calling your CFO/Legal that's one thing, if it's police that's something else.

Overall, it's hard to go wrong with the time-tested advice sudo lectures you with, specifically #1/#3:

        We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things:

        #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.

It's rather ironic that seamless integration with the OS is much less of a privacy issue than seamless integration with remote servers nowadays....

You're asking what he's scared of on Slashdot? Maybe his real name is RMS...

I think you're confusing generic Disk Repair with rebuilding the Desktop File...

Unless your drives were seriously damaged (floppies thrown in a backpack were always a bad idea no matter where you were), missing icons and whatnot were at the disk catalog level (used by Finder), not the HFS level. Command-Option on disk insert would fix it for me.

In the event of a power outage or something similar, it was always advisable to run Disk First Aid (and later versions System 7.5+ or Mac OS 8.1 maybe?) would run it automatically for you in the event of an unsafe shutdown, but that's just morally equivalent to running an fsck.

Not so weird. There may be plenty of sociological reasons one could consider for making this gender (or sex) specific that are probably pretty valid. (Men and women have dramatically different ways of understanding communication, and this was not unknown in the 1950s.)

But if the rest of us are forced to consider Turing's homosexuality as a person indivisible from his work as a visionary (OMG he was a thinker, and he was gay!), it's only fair to consider that trait in the analysis of the work he did...