From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id E7F8F1EF7BC; Thu, 9 Oct 2014 12:41:10 -0400 (EDT) Received: from hurricane.the-brannons.com (hurricane.the-brannons.com [64.62.188.119]) by befuddled.reisers.ca (Postfix) with ESMTP id 9DFAE1EF7AF for ; Thu, 9 Oct 2014 12:41:09 -0400 (EDT) Received: from localhost (71-38-154-164.ptld.qwest.net [71.38.154.164]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id D220178B9D for ; Thu, 9 Oct 2014 09:36:27 -0700 (PDT) From: Deedra Waters To: "Speakup is a screen review system for Linux." Cc: Subject: Re: a little sysadmin story References: <86a956i23h.fsf@vibrator.pk5001z> <54368FDC.1010704@math.wisc.edu> Date: Thu, 09 Oct 2014 09:36:09 -0700 In-Reply-To: <54368FDC.1010704@math.wisc.edu> (John G. Heim's message of "Thu, 09 Oct 2014 08:38:36 -0500") Message-ID: <86lhopgpza.fsf@vibrator.pk5001z> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 16:41:11 -0000 "John G. Heim" writes: > How do you know that the kernel panicked because of a speakup bug? I > know that I've often thought that but upon closer inspection, it > turned out that speakup generated error messages but they were really > caused by something else. Because my boss who had a hell of a lot more experience then i do dug into it and found out it was a speakup bug. I know you're convinced that speakup is perfect never has a bug and crashes the kernel so i wont even try and convince you other wise but there were people at that lab with a lot more experience then i and they were access friendly. They took a chance with speakup, i had at least 2 ocations where it crashed and it was a bug that was caused by speakup. This was in 2004 now speakup is a lot more stable, but yes it can and does cause the kernel to panick if you hit major bugs. > > > > > On 10/08/14 18:16, Deedra Waters wrote: >> 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. >> > _______________________________________________ > Speakup mailing list > Speakup@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup -- Website: http://deedra.the-brannons.com blog: http://deedra.the-brannons.com/blog