From: Barry Pollock <barryp@mail.hurontel.on.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Initrd Help
Date: Sun, 23 Nov 2003 11:53:35 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.58.0311231148150.19354@box> (raw)
In-Reply-To: <20031123163221.GA191@lnx3.holmesgrown.com>
Does your slack ware disk allow you to preload modules from disk
If so, you can do it that way?
Each system has a different way of finding its modules on the floppy.
You hav to figure out that location and place the module in exactly that
location on the floppy.
Then the system can find the module and you can have speech after the
first question.
Barry
On Sun, 23 Nov 2003, Steve Holmes wrote:
> I've been dabbling around a bit with the idea of using initrd to load
> the speakup modules. So far, I've read /usr/src/linux/Documentation
> more than once and looked at an actual initrd image from slackware
> 9.1. But I'm a bit confused. I'm guessing initrd needs to contain a
> completely bootable system within its file system? What about the
> additional modules I want to load such as Speakup? Do I have to copy
> those modules out of the normal place and copy them into initrd? What
> documentation I've read so far doesn't really offer me any small
> examples I can use for my purposes. The slackware one is interesting
> but sure seems like over kill to merely load some extra modules at
> early boot time. Am I possibly going about this the wrong way?
>
> Right now, I have Speakup loading in my rc.modules file and that isn't
> bad for now but That doesn't give me the option to change synthesizers
> from one boot to the next either.
>
> Anyone have any ideas out there?
> Thanks.
> --
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Steve Holmes
` Barry Pollock [this message]
` Steve Holmes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0311231148150.19354@box \
--to=barryp@mail.hurontel.on.ca \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).