1 |
Greetings All |
2 |
|
3 |
Hubbs, great work getting modules up outside the tree. |
4 |
Unfortunately this poses an additional problem for users |
5 |
of the sftsyn module. Getting everything set up has lways been a bit |
6 |
rough, but now all the daemons don't go either. |
7 |
|
8 |
As in, the old process used to be: |
9 |
Build speakup into kernel,build sftsyn module |
10 |
add speech-dispatcher, speechd-up to default runlevel |
11 |
reboot |
12 |
|
13 |
This would then pull in festival, espeak, and whatever to get |
14 |
speech-dispatcher up and going, make the dev nodes and whatever, |
15 |
and then you could use it.This is the way it is on |
16 |
gentoo-sources-2.6.20-r10, which I have been using. |
17 |
|
18 |
I am unclear how to make a parallel to all these steps in the new setup. |
19 |
|
20 |
The speakup is now only a module |
21 |
The synth is still a module. This module is built as speakup_soft |
22 |
Both these can be modprobed to get the dev nodes. |
23 |
|
24 |
I'm unsure how to make this permanant because of the new usage around |
25 |
boot-up modules. There is a lot around this in the migration guide to |
26 |
OpenRC, from the old baselayout-2, but now I'm not sure where to put the |
27 |
modules I need, obviously speakup, speakup_soft are the ones but where |
28 |
do I need to put these? |
29 |
|
30 |
Also of course the fact that speechd-up expects speakup to not be built |
31 |
as a module means that the 'support' of sftsyn appears to be something |
32 |
which once compiled cannot be started. I'm sorry to sound negative here |
33 |
but, this is a brilliant system, am I missing something here. |
34 |
|
35 |
Many thanks |
36 |
|
37 |
sonofthejedi |