From: Deedra Waters <deedra@the-brannons.com>
To: speakup@linux-speakup.org
Subject: a little sysadmin story
Date: Wed, 08 Oct 2014 16:16:50 -0700 [thread overview]
Message-ID: <86a956i23h.fsf@vibrator.pk5001z> (raw)
i was working at oregon state's open source lab and network admin
thing for a year and a half. Here's one situation. i came across. Not
trying to antagonize anyone at all but here's what happened and this is
one reason why i dislike speakup in the kernel even though it's got a
lot of benifits.....Anyway......
I was working at the lab. Debian was having a problem with one of their
my machines. The machine had crashed so i went to the dmz to kick it and
try and help them figure out their problem. We were happily working on
the box an hour or so later when i hit a speakup bug. The kernel
panicked, and the box crashed. $debiandeveloper lost their changes to
some config files. The end result was the lab lost their access to the
debian machine. I had a similar problem on another client's box. end
result, they flipped had speakup pulled from their kernels and i wasn't
allowed to work on their boxes.
This is an extreme case, but it's also an important point in my concern.
--
Website: http://deedra.the-brannons.com
blog: http://deedra.the-brannons.com/blog
next reply other threads:[~ UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
Deedra Waters [this message]
` Brian Buhrow
` Deedra Waters
` Janina Sajka
` Deedra Waters
` Littlefield, Tyler
` Littlefield, Tyler
` Al Sten-Clanton
` Glenn
` Mike Ray
` Glenn
` Littlefield, Tyler
` Glenn
` Mike Ray
` Glenn
` Tom Fowle
` covici
` Blake Hardin
` Kyle
` Kelly Prescott
` Janina Sajka
` Kelly Prescott
` Janina Sajka
` John G. Heim
` Janina Sajka
` Glenn
` John G. Heim
` Janina Sajka
` Samuel Thibault
` John G. Heim
` covici
` John G. Heim
` Littlefield, Tyler
` John G. Heim
` covici
` speakup in the kernel John G. Heim
` covici
` John G. Heim
` Samuel Thibault
` covici
` Samuel Thibault
` covici
` John G. Heim
` Samuel Thibault
` covici
` a little sysadmin story Janina Sajka
` Janina Sajka
` John G. Heim
` Deedra Waters
` John G. Heim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a956i23h.fsf@vibrator.pk5001z \
--to=deedra@the-brannons.com \
--cc=speakup@linux-speakup.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).