* Gregory Nowak <greg at romuald.net.eu.org> wrote: > On Thu, Apr 09, 2009 at 12:58:25AM +0200, Michael Prokop wrote: >> My question is: do I have to take care of port/quiet/ser/start as >> well on my own? If so: what's the most elegant way to support that? > You'll need to provide the ability for relevant parameters to be > passed to appropriate modules, if the user supplies them at boot. You > may want to look at the syntax we use in systemrescuecd to do this: > http://www.sysresccd.org/Speakup-info#Booting_with_Speakup_in_SystemRescueCD_1.1.0_and_later > and the section after that one might be of use as well. The way we do > this is to look at /proc/cmdline, and start parsing out the options, > starting with "speakup=". If the quite option is passed, we invoke > speakup_main with quiet=1. For "synth=", we just invoke that > particular module, (I.E. synth=bns invokes speakup_bns, synth=dtlk, > invokes speakup_dtlk, and so on). As for the other options, we simply > pass them to the particular synthesizer module, expecting that the > user will know which options a particular synth module takes, > (I.E. that speakup_bns takes ser=, but that speakup_dtlk takes > port=). Hth. I was hoping to get around the /proc/cmdline parsing, but I think I'll use the same approach as in systemrescuecd. Thanks! regards, -mika- -- ,'"`. http://michael-prokop.at/ ( grml.org -? Linux Live-CD for texttool-users and sysadmins `._,' http://grml.org/
