<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Christopher Stone wrote:
<blockquote
cite="midd9c612bf0903291042m4d929320w23d666f65666b0a6@mail.gmail.com"
type="cite">
<pre wrap="">On Sun, Mar 29, 2009 at 10:01 AM, Matthew Garrett <a class="moz-txt-link-rfc2396E" href="mailto:mjg@redhat.com"><mjg@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Everyone involved agreed that not having a
keystroke that caused immediate data loss was a sensible idea.
</pre>
</blockquote>
<pre wrap=""><!---->
Ha! Imagine if these same people were in charge of bash. We would
have to remove the rm command because someone could accidentally type
rm. Imagine if someone accidentally typed rm -fr / as root!!! That
could be disastrous! !
</pre>
</blockquote>
<tt>Kudos.<br>
<br>
What many people don't realize is that now instead of when a user sees
that their mouse and keyboard are locked up they can just hit the
Gtrl-Alt-Backspace like they've done for years and kill their X server
and be back at a login prompt, now they're going to call the help
desk. And it going to go like this:<br>
<br>
Help Desk> Good morning, Help Desk. How can I help you?<br>
User>My keyboard and mouse are behaving weird. I checked the cables
and their plugged in ok.<br>
Help Desk> Sounds like your X server is messed up. Did you try
killing your X server?<br>
User> Yes, I pressed Ctrl-Alt-Backspace but norhing happened.<br>
Help Desk> What OS is loaded on your workstation?<br>
User> I'm not sure. They loaded a new one last week.<br>
Help Desk> Ok, let me open a System Administration ticket for you.
They'll call you back in about 10 minutes.<br>
User> Ok, thanks.<br>
<br>
Ring<br>
User> Hello.<br>
SysAdmin> Hi, I see your having a problem with your workstation.<br>
User> Yes, my keyboard and mouse aren't responding now. They just
kept getting slower and slower.<br>
SysAdmin> Ok, it sounds like something has happened to your X server
or you have some runaway process. Let me check something.<br>
User> Ok.<br>
SysAdmin> Ok, I can see that your X server is pegged at 98.3
percent of cpu. So have you tried killing your X server yet?<br>
User> Yes, I tried Ctrl-Alt-Backspace but it didn't do anything.<br>
SysAdmin> Ok, I can kill your X server from here. Would you like
me to do that?<br>
User> Yes, please.<br>
SysAdmin> Ok, I killed your X server. What do you see?<br>
User> It went back to the login prompt.<br>
SysAdmin> Good, you should be able to just log back in now.<br>
User> Yes, I'm in. Thanks a lot.<br>
SysAdmin> Your welcome. Is there anything else I can do for you?<br>
User> No, I'm fine now.<br>
SysAdmin> Ok, well have a good day. I'll close this ticket.<br>
User> Yes, go ahead. And thanks again.<br>
SysAdmin> No problem. If you have any more problems just call the
Help Desk. Bye now.<br>
User> Ok, Bye.<br>
<br>
And that's what we're going to start seeing instead of users being able
to manage the situation themselves.<br>
<br>
Regards,<br>
Gerry<br>
<br>
<br>
</tt>
</body>
</html>