From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from uni04mr.unity.ncsu.edu ([152.1.1.167]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1EMDo3-00049f-00 for ; Sun, 02 Oct 2005 20:03:47 -0400 Received: from QUARK (cpe-069-134-173-071.nc.res.rr.com [69.134.173.71]) (authenticated bits=0) by uni04mr.unity.ncsu.edu (8.13.4/8.13.4/N.20050816.01) with ESMTP id j9303Y4F024095 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 2 Oct 2005 20:03:39 -0400 (EDT) From: "Sina Bahram" To: "'Speakup is a screen review system for Linux.'" Date: Sun, 2 Oct 2005 20:03:30 -0400 Message-ID: <000301c5c7ad$e6908df0$6701a8c0@QUARK> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 In-reply-to: <20051002235032.GA4642@blackbox> Thread-Index: AcXHq8/TPSu4qnfUTnyG/rpCmaBi4QAATMJg X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.2, Antispam-Data: 2005.10.2.31 X-Spam-Status: No, Hits=7% X-Spam-Level: IIIIIII Subject: RE: Speakup in user space, why or why not? X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 00:03:48 -0000 Correct Basically ... Having your selected process start up with different terminals is not an issue because all processes have init as their parent, if and when their parent dies. All one has to do is fork, have the child continue on and the parent exit. Hence a daemon ... Well, there is actually a little bit more to a daemon, as they should fork twice and exec to avoid having a controlling terminal, but ... Same concept Take care, Sina -----Original Message----- From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Kenny Hitt Sent: Sunday, October 02, 2005 7:51 PM To: Speakup is a screen review system for Linux. Subject: Re: Speakup in user space, why or why not? Hi. I have brltty in all consoles also. It starts up with an init script before login, so there is only one process running. Kenny On Sun, Oct 02, 2005 at 04:23:54PM -0400, Janina Sajka wrote: > Well, I would expect the canonical answer to come from Kirk himself, > but I would expect it's more than just the boot up messages. There's > also the issue of ubiquitous availability, and persistence. > > In other words, you get Speakup across any and all consoles that you > might open. In my case that's 24 consoles (or 23 on the machines where > I also have a GUI Desktop). Try that from user space. I don't think it > could be done. > > Then there's persistence--meaning that your access continues to > function in the face of whatever might happen to an application you're running. > Not only kernel panics will talk, but any application gone awry can > often, nay usually, be brought under control from a second console. > > Sina Bahram writes: > > Hi Janina, > > > > The point is one of personal curiocity, questions about software > > engineering, and just general interest in why. > > > > I really would like to know if something like this is possible, and > > if the only reason for having it in the kernel is for boot messages. > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup _______________________________________________ Speakup mailing list Speakup@braille.uwo.ca http://speech.braille.uwo.ca/mailman/listinfo/speakup