Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Comment armchair activism (Score 2) 372

this is one of those stories where if everybody on slashdot who fucking hates big pharma posted links on their facebook/twitter/g+/instawhatever, it could probably boil over to one of those flashpoint social media stories that gets the company to own up to being fuckbags.

it seems that's the only way things change these sure doesn't do shit...

Comment Re: Glad to have it (Score 3, Insightful) 451

It should, but what about externalities. People become more reliant on it and could end up paying even less attention rather than pay fucking attention to the car in front of them. Speculation is moot. Show me trials before it becomes federal law or some ilk like that.

Comment Re: How dare they? (Score 1) 451

Your sarcasm is actually true. It is our right. And you also have the responsibility of paying for poor decisions. This generation would rather hand over the hard choices to somebody else rather than risking the responsibility of making a choice themselves, or for that matter, being afraid of living in a free society where such choice are possible.

Comment Re:i work in enterprise datacenter (Score 1) 150

...small backhaul offices with a couple hundred servers do not a datacenter make. we're arguing semantics at this point but my point still stands for anybody switching petabytes by the hour, i.e. 1k switches at 24-48 10G fiber links switching at 5-10% loading every second.

Comment Re:i work in enterprise datacenter (Score 1) 150

> If a single device brings down your entire data center, you've got design problems and your architect should be fired or retrained.

Please: if your data center has the time, and skill, and is willing to take the service interruptions to make the whole setup properly immune to single points of failure, that's great. But very, very few live business environments have that kind of resource, time, and willingness to enable critical switches with robust failover.

As other posters have mentioned the level of switches discussed by op are not DC switches. SMB switches, sure, but enterprise datacenter, no.

Comment Re:i work in enterprise datacenter (Score 1, Flamebait) 150

blah blah blah

Reality is single device failures bring down large chunks of the net including valuable peers of your "enterprise datacenter"

Of course, sometimes identical cisco models used in redundant tuples also cause outages together after upgrade by common bug that didn't show up in test

so pontificate all you want, you're vulnerable to a lot of bad things

(1) I guarantee if you emailed that explanation to a DC manager you'd be shitcanned. I agree that we are all vulnerable to bad things, but avoidance of a single point of failure device in the DC like op highlights is network ops 101 stuff.

(2) Show me a datacenter that's an all cisco shop. Most are whitebox/greybox now. Welcome to the 21st century. Most "big-data" shops have firmware experts who know their hardware down to the MMU register level and order stuff directly from places like Taiwan with nary a CCIE to be found in corporate ranks.

Comment i work in enterprise datacenter (Score 3, Interesting) 150

If a single device brings down your entire data center, you've got design problems and your architect should be fired or retrained. These days everything is redundant in triplicate at minimum and new devices spin up automatically based on automatic provisioning and chef/puppet type setups. Even if your core router (why would you have just one!?!?!?!) shits the bed and resets to factory defaults with VLAN 1 and basic STP with no routing interfaces configured, if your NOC folks did a good job, a proper MSTP / VRF / TRILL / SDN ( OpenFlow, etc) / etc like setup should route around that shit and QA will have already tested the "core clos spine device reboots to factory defaults" test case at which point you have just another device for a low paid lackey to swap out based on your network monitor going yellow.

If you work in a Fortune 500 datacenter and you can't handle this sort of outage, get the fuck out. You're the reason shit's going downhill. Also if a Cisco 3650 or 3850 bring down your datacenter, see previous negative asshole sentiment or get a new job if your manager is responsible for the confines of such a clusterfuck. No participation trophy for such asshattery.

Submission Ashley Madison Hackers Dump Their Load-> 1

cosm writes: The folks behind the Ashley Madison hack followed through with their threat by posting 9.7G of customer date to the "Dark Web", Reuters reports.

Hackers have followed through on a threat to release online a huge cache of data, including customer information, that was stolen a month ago from cheating spouses website, several tech websites reported on Tuesday.

Link to Original Source

Comment Internet of Things (Score 1) 383

Assuming the "Internet of things" is not just a hollow buzzword, do you see Linux dominating IoT's projected explosive growth, forever entrenching Linux as the #1 choice for embedded eons to come?

PS: To me, IoT just represents embedded stuff that connects to the internet in trendy ways marketers haven't over-saturated yet with hip commercials and cheap-labor produced widgets.. "things" sells better to the unwashed, so meh

Comment Re:Thanks You Dr. Nash (Score 2) 176

Awesome to meet somebody else in the space, it is a fun place to be in. I'm mostly a DevOps guy now (I know --- buzzwords blah blah), but if a tough support call comes in, typically I spend my time in the run-time analysis side explaining "why is this packet being dropped from this queue" or "why did our convergence algorithm pick this path". Say a big data center customer calls and says "such and such is getting dropped on the 40G QSFP links during congestion, please explain your bug". Then that turns into a large discussion about how to configure COS queues properly and some education about xyz configuration spaces with the various protocols, followed by an update to our documentation if it's sparse in that particular implementation scenario or a white paper specific to their topology and common traffic profiles (tier 1 ISPs usually).

The program isn't debugged until the last user is dead.