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

 



Forgot your password?
typodupeerror

Comment Where's this going to end up? (Score 1) 421

So was his offence the mention of a firearm, or the mention of its employment in ending a fantasy creature's life? If he said he shot a raccoon, would he have also been expelled?

The US has been glorifying scenes of extreme violence for years on TV or in the movies. And yet, if a child were to mention they watched anything like that, and, god forbid, write a synopsis on it, they'd be looking at expulsion/sternly-worded letters too? Really, what kind of children are being raised there these days? Where everything is an offence of some kind, where to feel mildly insulted is a level of indignance akin to to smacking your mother in the face elsewhere in the world.

In a couple of decades, these mis-educated, skin-as-thick-as-paper children are going to be the ones running a country possessing the most powerful military on earth.

Comment Re:Disappearing $3 Billion (Score 2) 51

It probably won't be around in 5 years or so.

The userbase is predominantly teenagers who'll be very different people in a couple years, and the slightly older crowd who'll have moved onwards as well.

I see two issues:
1) Functionally, it's simple to replicate, and
2) The ephemeral nature of the pictures were what gave it traction in the first place. This is now under serious (20 years of) scrutiny.

There will likely remain a market for the functionality it offers, but the teen demographic will probably not be revitalised given its current situation.

Let's not mock the founder(s) for turning down the $3 billion though, this is a good lesson learned and hey, they're still young.

Comment In my experience... (Score 1) 294

.. as the admin for a couple of hundred Windows servers, an efficient CAB is your friend. As another said, they have your back, and that of the business (and by extension, the poor guy who is up at 4am fixing any issues introduced). That said, I've also worked with companies and CABs that know how everything is written in the ITIL handbook, but with no clue of how to put it into (an efficient) practice. It sounds like your CAB just wants the paperwork done - did you bring on consultants recently? - and think/hope it will mitigate the risks involved with patching. Change request for patching on a development environment? Routine change. Keep up with the news for any issues from this month's patches. You patch dev, or your pre-prod environment or whatever you have, monitor for a few days and if all is good you apply the same patches to your production machines. This is enough risk mitigation for most, and it gets the job done at the end of the day. Make up a nice RACI chart (Responsible, Accountable, Consulted, Informed) for the whole process - you are probably R/A for successful patching, but, the CAB will provide the approval for you to go ahead. They won't allow you to do it if there's a big release, or some on-going issues. Then you only need to know how to push the patches and have a good engineer to fix anything that might occur on the night, and the accountability trail takes care of any finger-pointing and addresses any gaps in the process you might have noticed. Start slow, start small. Work your way up in volume as the becomes more like a routine change.

Submission + - System Administrator vs Change Advisory Board 1

thundergeek writes: I am the sole sysadmin for nearly 50 servers (win/linux) across several contracts. Now a Change Advisory Board (CAB) is wanting to manage every patch that will be installed on the OS and approve/disapprove for testing on the development network. Once tested and verified, all changes will then need to be approved for production.

Windows servers aren't always the best for informing admin exactly what is being "patched" on the OS, and the frequency of updates will make my efficiency take a nose dive. Now I'll have to track each KB, RHSA, directives and any other 3rd party updates, submit a lengthy report outlining each patch being applied, and then sit back and wait for approval.

What should I use/do to track what I will be installing? Is there already a product out there that will make my life a little less stressful on the admin side? Does anyone else have to go toe-to-toe with a CAB? How do you handle your patch approval process?

Slashdot Top Deals

The first version always gets thrown away.

Working...