public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: Speakup in user space, why or why not?
Date: Sun, 2 Oct 2005 20:03:30 -0400	[thread overview]
Message-ID: <000301c5c7ad$e6908df0$6701a8c0@QUARK> (raw)
In-Reply-To: <20051002235032.GA4642@blackbox>

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



  reply	other threads:[~ UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Sina Bahram
 ` Gregory Nowak
   ` Garrett Klein
     ` Sina Bahram
       ` Janina Sajka
         ` Sina Bahram
           ` Janina Sajka
             ` Kenny Hitt
               ` Sina Bahram [this message]
             ` Lorenzo Taylor
               ` Sina Bahram
                 ` Gene Collins
                   ` Sina Bahram
                     ` Gene Collins
                       ` Sina Bahram
                     ` Scott Howell
                       ` Charles Hallenbeck
                         ` Sina Bahram
                       ` ace
                         ` Sina Bahram
                   ` Sina Bahram
         ` Lorenzo Taylor
           ` Sina Bahram
           ` Luke Yelavich
           ` Jim Grimsby
   ` Sina Bahram

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='000301c5c7ad$e6908df0$6701a8c0@QUARK' \
    --to=sbahram@nc.rr.com \
    --cc=speakup@braille.uwo.ca \
    /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).