From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id AE9AF1EF840; Thu, 9 Oct 2014 09:47:06 -0400 (EDT) Received: from tds-solutions.net (tds-solutions.net [192.99.32.153]) by befuddled.reisers.ca (Postfix) with ESMTP id 5838F1EF83C for ; Thu, 9 Oct 2014 09:47:05 -0400 (EDT) Received: from tds-solutions.net (localhost [127.0.0.1]) by tds-solutions.net (Postfix) with ESMTP id 4E32F3B3D3 for ; Thu, 9 Oct 2014 09:46:57 -0400 (EDT) X-Virus-Scanned: amavisd-new at tds-solutions.net Received: from tds-solutions.net ([127.0.0.1]) by tds-solutions.net (tds-solutions.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id our3nazP4t8W for ; Thu, 9 Oct 2014 09:46:46 -0400 (EDT) Received: from [192.168.1.224] (unknown [69.43.65.27]) (Authenticated sender: sorressean) by tds-solutions.net (Postfix) with ESMTPSA id E353E3B3D2 for ; Thu, 9 Oct 2014 09:46:45 -0400 (EDT) Message-ID: <543691D1.9050000@tysdomain.com> Date: Thu, 09 Oct 2014 09:46:57 -0400 From: "Littlefield, Tyler" Reply-To: tyler@tysdomain.com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "Speakup is a screen review system for Linux." Subject: Re: a little sysadmin story References: <86a956i23h.fsf@vibrator.pk5001z> <20141009125200.GI1044@opera.rednote.net> <86ppe1gyed.fsf@vibrator.pk5001z> In-Reply-To: <86ppe1gyed.fsf@vibrator.pk5001z> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 13:47:06 -0000 This whole story sounds like it needs another couple of bears to make it all interesting. So speakup crashed the kernel. I've had issues, but apart from known bugs I've never seen speakup panic the kernel all the time. Speakup caused a system to crash? Perhaps. People should also backup their work. On 10/9/2014 9:34 AM, Deedra Waters wrote: > Janina, > > speakup was the cause because when bossman came down to hook up a > monitor and look, the panick messages had something to do with speakup. > > As for backing up their work, they were trying to fix their fuck-up to > begin with. The initial problem wasn't with speakup. However when i was > helping them debug it, speakup made the kernel panick and crash. > > Debian i dont think likes people with root access on their box to begin > with, but i think they kind of didn't like speakup in their kernel to > begin with. > > I suspect on the other hand that if speakup was a user-space app, it > wouldn't have mattered to them so much. If a userspace program crashes > it doesn't take down the whole box. When speakup does though, it takes > down the whole box. > > -- Take care, Ty http://tds-solutions.net He that will not reason is a bigot; he that cannot reason is a fool; he that dares not reason is a slave.