That's awesome Chris. I always thought having software speech in the initrd would be very neat; the equivalent of having a hardware synth at boot more or less. I wasn't sure if there is such a thing as a too big initrd. Your post tells me the answer is no, at least in your case. The second and harder part is figuring out what exactly needs to go in the initrd to get software speech, while not putting in the initrd more than is necessary. Could you please consider doing a brief write-up on the procedure you used? I would find something like that to be a helpful and interesting read, and I'm sure others would as well. Greg On Wed, Oct 08, 2014 at 04:04:16PM -0700, Chris Brannon wrote: > Well, if the Linux console moves into user space, this doesn't have mean the > end of hardware speech. > Perhaps the way forward is through initramfs? As a proof of concept, I > built one that had the Speakup modules, audio libraries, and espeakup. > I had *software* speech running from the initramfs. > It was a bit difficult to build it, because I had to figure out all of > the dependencies and add them. But it worked. > Now, if you're just doing hardware speech, things are going to be much > less complicated, and it should definitely be possible to have it long > before the root partition is mounted, even if the Linux console code > ends up migrating to userspace. > > -- Chris -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-manager@xxxxxx _______________________________________________ Speakup mailing list Speakup@xxxxxxxxxxxxxxxxx http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
