Well, this is laudable, certainly. But, why suffer? You have better control if you are running the system natively rather than over telnet or some such. Also, the redhat install you're on is quite out of date. I still would recommend you get the Bill Acker iso's and install an up to date linux package. Then, grab an even later kernel and practice. You'll always have the other kernel as a boot option. Yes, that's something else Windows people don't realize--as you boot linux you can choose among many kernels to boot with. To answer some of your other questions: Redhat numbers are iterative and relate to Redhat only. insmod is 'insert module' and you almost certainly have it. If you actually need to see where it lives use the locate command as follows: locate insmod If you really want long file names, have at it. They're most certainly supported in linux. Just remember to put them in quotes if you're using spaces in the file names, as , for example: "My Long File Name.txt" On Thu, 17 May 2001, Rich Caloggero wrote: > Actually, I'd trying to learn as juch about linux as I can, so I'd like to > try and patch and compile the kernel myself. Couple of questions: : we're > running redhat 6.2.1 with kernel 2.2.19. What does the redhat version number > signify? When examining the README in /usr/src/linux and the associated > Changes file in the kernel subdirectory, it mentions a command called > insmod. I don't have it. What is it and where do I get it? > Is there a document I should read to further this process? I think I have a > decent understanding of what I'm doing inprinciple, I just don't know where > things live and their names. Incidentally, what do yu-all do about linux > cryptic commands and speech? I've gotten used to long filenames, and labeled > controls - going back to unpronouncible command names etc is just kind of > painful. > > Thanx in advance. > > Rich > > > ----- Original Message ----- > From: "Janina Sajka" <janina at afb.net> > To: <speakup at braille.uwo.ca> > Sent: 16 May, 2001 5:43 PM > Subject: Re: speakup/install failed > > > Rich: > > If you're able to download the iso images at > ftp://speakup.octothorp.org, you'll be ahead of the game. Bill Acker has > patched speakup into the current Redhat install very nicely. You'll get > a fully accessible install--well except for the first prompt where there > is no speech and you have to indicate your synthesizer. But after that > prompt, the install is accessible and the speech is built in. It's by > far the easiest coarse. I heartily recommend it. > > On Wed, 16 May 2001, Rich Caloggero wrote: > > > I'm trying to install speakup-0.10a on redhat kernel 2.2.19. > > I put the speakup sources under /usr/src and copied the source tree for > > linux-2.2.19 into linux. I entered the speakup source directory at > > /usr/src/speakup-0.10a and typed ./install and got this mess: > > [summary: lots of errors about expected binary operator ] > > ./installPatching version v22 > > Creating .orig files [./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ./install: [: ==: binary operator expected > > ] done. > > Patching files [p./install: ${writeloc//^/\/}: bad substitution > > ] done. > > Copying files [c./install: ${writeloc//^/\/}: bad substitution > > ] done. > > speakup-0.10a# > > > > Help. > > > > Rich > > > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > -- > > Janina Sajka, Director > Technology Research and Development > Governmental Relations Group > American Foundation for the Blind (AFB) > > Email: janina at afb.net Phone: (202) 408-8175 > > Will electronic books surpass print books? Read our white paper, Surpassing > Gutenberg, at http://www.afb.org/ebook.html > > Download a free sample Digital Talking Book edition of Martin Luther King > Jr's inspiring "I Have A Dream" speech at > http://www.afb.org/mlkweb.asp > > Learn how to make accessible software at > http://www.afb.org/technology/accessapp.html > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- Janina Sajka, Director Technology Research and Development Governmental Relations Group American Foundation for the Blind (AFB) Email: janina at afb.net Phone: (202) 408-8175 Will electronic books surpass print books? Read our white paper, Surpassing Gutenberg, at http://www.afb.org/ebook.html Download a free sample Digital Talking Book edition of Martin Luther King Jr's inspiring "I Have A Dream" speech at http://www.afb.org/mlkweb.asp Learn how to make accessible software at http://www.afb.org/technology/accessapp.html
