Pressing tab only completes as much of the command as can be automatically completed. In other words, if there is more than one file or directory name that starts with the chars 2.6. tab completion cannot continue until you supply it the disambiguating data. Use: ls -1 to learn what that is. Undoubtedly, you have several installations of a 2.6 kernel. To answer your other question, the mkinitrd command is one command. You can either enter it all at once, without pressing enter, or you can press the back-slash key to continue your command on a new line. But, you must enter one command. Beth Hatch writes: > > > Hello everyone, > > Today, after lots of trial and tribulation, I finally got Linux to speak!!!! > The Dectalk I borrowed works fine and I was able to log in and start > speakup. > > I began making the initrd disk today following the installation how-to > file. I am using kernel 2.6.10 and Fedora core 3. When I go to the > /libs/modules directory and attempt to type in the commands, I am making the > ram disk after installing Speakup, not during the installation, I get error > messages referring to files not found. Unfortunately, I'm not sure what > file or files it was looking for, I did an everything installation, but due > to uncontrollable circumstances my installation of Fedora was not done by me > but by someone installing and patching the kernel for me. So, When I look > at my commands as typed into the command line and of course using the proper > synthesizer key, I see only the 2.6. and no other numbers or letters > designating the rest of the kernel designation when I press the tab key as > directed in the installation how-to. I also see nothing relating to the > Dectalk driver so obviously either I've done something wrong, or something > is missing in the way I've entered the command. Does the entire command > belong on one line, or do you hit enter at any other time before the end of > the command? > > I'm sorry this question is so convoluted, I am following the > installation how-to and I am unsure what I may be doing wrong or why the > initrd isn't working. > > Thanks for any help or suggestions, > > Beth > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Janina Sajka Phone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Chair, Accessibility Workgroup Free Standards Group (FSG) janina at freestandards.org http://a11y.org If Linux can't solve your computing problem, you need a different problem.
