slackware and kernel 2.4-24 question

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well if if is your own machine and you usually want Speakup available
all the time, I would go ahead and include the base Speakup statically
in the kernel by choosing 'y' to include it instead of 'm' to make it
moduler.  If you are using hardware speech and include that selection
with 'y' also, you can have Speakup talking at the very beginning of
the boot process and have access to speech clear down to shutdown and
you can track kernel panics if/when they happen.

If it were all moduleer with 'm' kernel config options, you could load
speakup on to an existing system and start it up on the fly without
having to boot the system.  The potential here is say a publicly
available machine in the library running linux.  Just login and pop in
a CD with the Speakup modules available  and run a script and valah,
it's talking!  I may be a bit far fetched here but the idea is speakup
could more likely be included in standard kernel source this way and
have it completely out of the way for those folks who don't need it.

Another situation for modules is in the case of software synths.  On
my box, I have Speakup base and Speakout synth static but sftsyn which
is a software speech option, compiled as a module.  Whenever I want to
use software speech, I can merely echo 'none' to
/proc/speakup/synth_name, load up the stuff needed for Speech
dispatcher and Flite, then echo 'sftsyn' to /proc/speakup/synth_name.
This last step automatically loads  the software synth  module.

Whew!  what a long answer.  I hope it does help give some of the pros
and cons of modules to Speakup.

On Tue, May 18, 2004 at 11:22:58AM -0700, Debee Norling wrote:
> When you compile Speakup as a module, what advantages/disadvantages does
> this give you?

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAql7XWSjv55S0LfERAseOAJ9MBBq4XzghvmIHiGns5lK+rwFKvgCdHg4I
GjRVGQBVTyg6+FO9vaBj+78=
=fOZu
-----END PGP SIGNATURE-----