Yeah, I don't know how else you control side-fumbling.

it's not a turbo-encabulator.I've been wanting one of those for a long time.

We use CentOS AND RHEL. On a few mission critical servers running non-FOSS apps certified to run on RHEL, we use RHEL. We want to know that in event of a major problem (especially if I was gone for some reason) we can call the app vendor or RH and be reasonably confident the problem will get fixed. We've never needed to do that, but over the past decade it has remained far cheaper to pay RH than run the same app on Windows servers. We aren't talking about talking about tens of thousands of dollars to be able to run RH and get updates. If you want the ability to call Red Hat for support on a case-by-case bases, you can get an annual RHEL license for as low as $349 (academic pricing is more like $60/yr!). $799/year gets a 1-hour response for critical issues. But it is up to your boss to decide what level of support, if any, he wants to go with. For many of our other servers we use CentOS. Some can be down with little affect on the organization. Others are just running basic LAMP and FOSS apps where certification isn't an option or isn't required for support. Frankly there is no benefit to us to use RHEL on these servers as we are able to fully support the OS and recover from even severe problems. If you don't have any need for Red Hat's services, software/hardware certifications, or anything else that adds value to RHEL, then by all means stick to CentOS. If you are worried RHEL (and therefore CentOS) will go away if you don't support RHEL, insist that your boss buy a contract (and don't complain when you are looking for your new job.) It is all insurance. As others have said, the real question is how much will downtime cost you? Will RHEL reduce the chance of downtime? Will it shorten the amount of time until recovery? Will it show enough "due diligence" to your boss's bosses to keep both of you employed after a disaster? If you are really worried, fire off a memo to your boss with your concerns and then accept whatever he decides. (But keep a copy as CYA for yourself in case you turn out to be correct.)

If I can assay a guess, being a Deb user, I would say that that was probably for a version based on 1.6, or even God forbid, 1.7. 1.8 brought things along nicely, and 1.9 is very solid. It's like all php based apps, though: there are probably ways into it. Php-based apps on Debian do tend to be older, and so I almost always have to install and maintain them out of the main debian process.

What are you doing about staff development for the changes in Moodle 2? I support a number of districts, and that's my biggest concern. We've got teachers comfortable using it finally, and training on the new file management system alone is going to be a pain...

Years ago, I was a military brat there. One day, everybody spent all day waiting for the MX missile test launch. It was going to happen just after 7. Everybody knew this, even though it was a highly 'secret' event. (They also used to send the MP's around telling everybody to go indoors when there were other 'secret' launches.)7
It wasn't like the Soviets hadn't been informed there was a launch, anyway.

Speaking of, the runway wasn't *built* for the shuttle, it was extended. They used it to land c-5a's and such before.

A fan of malignant and malicious neglect, from my experience.

It's also poke sallet and salit. It's still pronounced as salad is normally. My grandma spelled it sallet, but said it as salad, so I went for conventional orthography.

And abandoned fields across the American south became the new gold fields of the Yukon.

That stuff pops up everywhere, and grows like you wouldn't believe. I can't imagine how well it would do if you fertilized.

And of course, you can use the leaves for poke salad. With a lot of boiling...

Well, he did have another job function that I know of, but they didn't mention it in the article.

Always fun when you see your place of employment in a newspaper article.

I don't recall there being the mouth shield before. It might have been there. It probably was, and I just wasn't thinking of applications for cubicle-worker dictation then.

Regardless, you couldn't hear her speaking into it, and she was definitely recording events. When the judge would ask if anybody knew the defendant, and none of the jurors responded, she was entering that fact; or at least, you could see that she was saying something.

This was a city-level court in Georgia, dealing with low-level criminal and civil cases.

I have no idea if they're transcribing as you say; you're probably right. I do know that a) they were recording with a pc there and b) she was using the mouth-hood to record when people nodded, etc. They have this big ol' MOTU firewire box to take input from all the microphones. I didn't actually get a chance to see the software.

10 years ago, they used digital tape in this same courtroom. 20 years ago, they had a steno machine.

I went to jury duty the other day, and the steno reporter... wasn't really using a steno machine. She was annotating the taping by speaking the non-verbal events into a little mouth-shield thingie.
So verbal dictation is possible- you'll just like more of a geek.

User education. It won't go away, you always need to do it, and for most users, you have to do it multiple times. Proximity systems may help, but...

For the record, on a winders machine, window-L. Two keystrokes, you're done. Well, mostly, but that'll keep most people out.

Well, yeah. But it's still got to take a lot of infrastructure that really sounds beyond their capabilities. Let's say:
16 tb drives, 1 eb= 62,500 drives.
Let's say 2 weeks of storage; 875,000.
Let's say 200 per. Let's say $100 extra per for the racks, cases, controllers.
$262,000,000 just for the storage.

I dunno, 1.5billion euros, with first usage in 2013 and full capabilities and usage in 2022; maybe they'll make it with that budget if they speak to somebody who already does lots of computation and storage, say: the Big G.