Re: [orca-list] [lutz kaiser gmx net: Re: Running brltty at startup with Orca.]
- From: Jason White <jason jasonjgw net>
- To: orca-list gnome org
- Subject: Re: [orca-list] [lutz kaiser gmx net: Re: Running brltty at startup with Orca.]
- Date: Sun, 1 Jun 2008 12:05:18 +1000
On Sat, May 31, 2008 at 10:44:26PM +0200, Fabrizio Marini wrote:
Tell him I opened it, and changed the value of the environment
variable RUN_BRLTTY from noto yes. Now i can regularly have brltty up
and running at startup.
To learn better how these things work, i have one more question. I
looked inside the script /etc/init.d/brltty and found some
instruction i could not understand very well, but i think it should
set to yes that variable if it is set to no. So, why the value of
that variable is unchanged after the script execution at startup?
To be more precise, if you remember, before i edited
/etc/default/brltty, i could regularly start brltty by digiting
#brltty
at the bash prompt, while i could not have it up and running at start up.
Here is how it works. /etc/default/brltty contains the variable assignment. In
/etc/init.d/brltty there will be a line that executes the contents of
/etc/default/brltty in the shell that is running the script. This will change
the value of the variable.
You can do this from the shell prompt as follows:
source /etc/default/brltty
and if you use the echo command or the set command to check the value of the
variable, you will find that it is set to yes.
Another syntax for this is:
. /etc/default/brltty
The setting is in effect only in the shell that executes the variable
assignment. Stated differently, the variable is a shell variable, not an
environment variable.
Later in the initialization script, the value of that variable will be tested,
and if it is set to "yes", brltty will be run.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]