On Tue, Feb 17, 2004 at 09:33:29PM +0100, sylvain ferriol wrote: [...] > plip needs several modules configuration (plip and partport_pc) > if i just use ethdetect/module_params question, for the 2 modules, > after configuring the first module, cdebconf will take the same for the > second because it has already be seen. > Or it is false > Another point is if i select high property for the second module, > cdebconf will show me the module_params question but with by the > parameters of the first one. > example, i have configured parport_pc: io=0x378 irq=7 > i will have in plip module question plip: io=0x378 irq=7 > but plip can only have parport=X options > so if the user must have a blank field for plip options > > So i have to create different questions using the same template and the > solution is db_register
Absolutely. > >Why is this 'Unknown' > >value a problem? > > because if we want to create a preconfigured d-i for automatic > installation, we will just have to add in questions.dat > Name: ethdetect/module_params/parport_pc > Template: ethdetect/module_params > Value: io=0x378 irq=7 Yes, and where is the problem? I just performed a simple test, and pre-seeding seems to work as expected, so I still do not see why there is a problem with these unknown owners. > >This can be easily fixed within rootskel > > > how do you do that? > create an specific template for all modules?, if think it's ugly > so what is the use of register? No, all I had in mind is to write /usr/bin/debconf-loadtemplate d-i /var/lib/dpkg/info/*.templates in rootskel/src/lib/debian-installer.d/S20templates, and #!/bin/sh exec /usr/share/debconf/frontend -o d-i /usr/bin/main-menu in rootskel/src/sbin/di-main-menu, I believe that all questions will then be owned by d-i. IMO this is only cosmetics, and it needs testing. > >but is this all you want? > > > yes, i think > does 'confmodule -o debian' work ? > because i see that frontend is a link to debconf No, AFAICT the -o flag must be passed to di-main-menu, as written above. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
