Linux distros (was Re: RH9 disks on the net.)

[Doug Sutherland]

Luke,

 > I then posited, that if such a parameter existed, it should
 > be made possible, during a kernel compile, to change that
 > defaulting to off behavior

With the speakup patches applied, when I run make menuconfig,
I get an option to enter a text string for default synthesizer.
The default value is "none". Perhaps that would do what you
are suggesting?

What it does it give you these options:
- speakup in the kernel (yes/no)
- include which synthesizers
   (you can tick off as many as you want (yes/no)
- then enter the default synth (string value)

The default synth is already "none" by default. In my case
I am changing that to usrdev, which is the software synth
mods for use with festival.

 > such that a "speakup=on" would not be necessary, if the
 > person compiling the kernel *wanted* speakup to be on all
 > of the time, unless they did the converse of the above,
 > and specified a "speakup=off" boot parameter (such as
 > might be necessary, if another family member was booting
 > the system, and didn't want speech).

Hmmm ... looking at slackware's speakup.i kernel config,
the default synthesizer CONFIG_SPEAKUP_DEFAULT is set to
none ...

Are you sure that it's not already set up to do what you
want? I am about to try compiling this with this value,
the default synth, set to usrdev, in the kernel config.
I think that means this is an always on speakup that
talks to the middleware that connects to festival.

If I leave it as "none" then I would need a boot time
parameter I assume, but I'm setting in now before
compiling the kernel.

What I want is lilo option for speakup or not ... but
I will have two different kernels ... maybe that's not
the ideal way ... I will experiment with this ...

  -- Doug




>Yes, this latter is a separate issue, but it entered the discussion as
>explained, and is thus a part of it, so long as anyone cares to talk to me
>about it.:)
>
>Luke
>
>
>On Thu, 10 Apr 2003, Doug Sutherland wrote:
>
> > Luke,
> >
> >  > We're talking about the official distribution, not your own
> >  > patched copy of the official distribution of the kernel.
> >
> > What's the difference? Presumably if speakup was added to the
> > official, it would do what I am looking at: it adds a new
> > option in console drivers for speakup, and allows you to
> > select synthesizers. Why should it be any different if it was
> > in the official source?
> >
> > Are you talking about a kernel parameter to tell it to use
> > speakup or not? If so, I think that is a separate issue.
> > This is the build of the kernel.
> >
> >    -- Doug
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>_______________________________________________
>Speakup mailing list
>Speakup at braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup