Gentoo Archives: gentoo-accessibility

From: Whitley CTR Cecil H <WhitleyCH.ctr@××××××××××××××××.mil>
To: "'gentoo-accessibility@l.g.o'" <gentoo-accessibility@l.g.o>
Subject: RE: [gentoo-accessibility] 2004.2
Date: Thu, 05 Aug 2004 12:30:17
Message-Id: 6D3A09C6CAB0D311BA5000902760D022040F2150@chpt0000se01.cherrypoint.usmc.mil
1 Hi deedra,
2 Okay, sorry i should have included complete information in my original
3 query. I have since googled a bit and d/l'ed the tgz from the speakup site
4 and read the readme. The program itself is dtload. It is included in the
5 speakup sources. It is an optional driver for the dectalk pc, and according
6 to the speakup mailing list (may 04) it works with the dectalk pc2 as well,
7 but files have to be replaced which come from DEC (the boards "firmware"
8 files). So, with all that said, I presume I can get there from here with
9 gentoo, i'll just need to use my external dectalk express long enough to
10 compile the additional driver as a module and replace the default files with
11 the equivilents for the pc2.
12
13 So, now with all that said, does 2004.2 have speakup built-in? Is there
14 anything I should watch out for when compiling mmy own kernel? I assume
15 there's still not an ebuild for a kernel with speakup in it, or is there?
16
17 The compile shouldn't be too horrible, after all it will be a minimal system
18 for use as a router/firewall. It's also not my normal system so if I have
19 to leave it in a corner compiling for a few days, that's no big deal (except
20 for thunderstorms, ain't summer great?). I won't want much on it to begin
21 with and I may remove most of that so that if it gets hacked they won't have
22 much to work with. In fact i'll probably use a stripped down busybox for
23 the shell and remove everything from /bin and /sbin that I can and have the
24 system still function. As long as I can mount, I can always put the tools I
25 need on cd since I will have physical access.
26
27 Regards,
28
29 Cecil

Replies

Subject Author
RE: [gentoo-accessibility] 2004.2 Deedra Waters <dmwaters@g.o>