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


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - Do You Fear the Singularity?-> 1

Submitted by StonyCreekBare
StonyCreekBare (540804) writes "Chromosome Quest, a lighthearted, fun, fantasy romp, with Castles, Dinosaurs, cat-people and many other classic Science Fiction staples, presents an only slightly tongue-in-cheek look at the very real and serious risks inherent in trusting entirely too much in intelligent machines. Chromosome Quest releases February 15 at eBook merchants everywhere. A short two-minute video introduction to the novel awaits your YouTube viewing! http://youtu.be/IZlGvgKZh1s"
Link to Original Source

Comment: Re:My opinion on the matter. (Score 1) 826

by bferrell (#47752177) Attached to: Choose Your Side On the Linux Divide

and to piggy back, I just had systemd go wonky on my system... Seems it decided not to talk to dbus. dbus was actually running. I couldn't login, issue a reboot command, start or stop processes. As I'm working remotely, I was kind of hosed. I kill'd -9 dbus, and that seems to have caused the system to reboot. I'm not sure though... there was no logging to investigate before OR after.

As has been mentioned, the idea of systemd seems like something to be looked at. Having poorly tested coded rammed into a critical part of systems is a very poor idea. The often espoused idea that if it's not rammed in it will never be sufficiently tested. That to me speaks of monumental arrogance and impatience at a minimum.

Comment: Network best practices may say this... (Score 2) 348

"A firewall is a MUST".... However

1.) If you are a contractor (or an employee for that matter), and you're explicitly told not to do something, document your concerns, in writing and either do what they tell you or quit. This covers your butt when thing blow up. Note I said, when, not if. You don't get to dictate the business objectives in either case (contractor or employee).

2.) The networks/firewalls are only one part of the picture. I've noted other posts asking questions concerning the surrounding environment. These are good, even if they don't address point (1.) If a "best practice" for an element in the environment breaks the environment, then the "best practice" is invalid and MAY be ignored. It may also be that the app in question is brain dead, but that's a whole 'nother topic.

I've seen way too many "best practices" that do not account for the specific environment and even more "checklist" jockeys who can't figure out how to make things work without them. Learn to do more than to follow a flowchart/checklist.

"Be *excellent* to each other." -- Bill, or Ted, in Bill and Ted's Excellent Adventure