Udev, USB discovery and debconf frontend
- To: debian-boot@lists.debian.org
- Subject: Udev, USB discovery and debconf frontend
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- Date: Sun, 9 Apr 2006 13:29:10 +0200
- Message-id: <[🔎] 20060409112909.GA4708@bouh.residence.ens-lyon.fr>
- Mail-followup-to: Samuel Thibault <samuel.thibault@ens-lyon.org>, debian-boot@lists.debian.org
- In-reply-to: <20060329215625.GE7158@bouh.residence.ens-lyon.fr>
- References: <20060327220409.GC16373@kitenet.net> <20060327221323.GV5157@bouh.residence.ens-lyon.fr> <20060328194900.GB3480@kitenet.net> <20060328200601.GG4660@bouh.residence.ens-lyon.fr> <20060329151748.GA6046@kitenet.net> <20060329153938.GJ4337@implementation.labri.fr> <20060329165925.GG6453@kitenet.net> <20060329174144.GA4028@bouh.residence.ens-lyon.fr> <20060329182441.GA14542@kitenet.net> <20060329215625.GE7158@bouh.residence.ens-lyon.fr>
Samuel Thibault, le Wed 29 Mar 2006 23:56:25 +0200, a écrit :
> Joey Hess, le Wed 29 Mar 2006 13:24:41 -0500, a écrit :
> > Samuel Thibault wrote:
> > > What are you thinking about? Preseeding? Kernel command line arguments?
> > > These are non-trivial. I actually wonder what non-interactive process
> > > can be trivial enough for dumb-Bob user :)
> >
> > if brltty_device_detected; then
> > debconf_set debconf/frontend whatever
> > brltty params
> > fi
>
> And this can be put in a udev rule, ok, fine.
Hmmm, it doesn't work on real, actually. When running in qemu, USB
devices are properly discovered before the debconf frontend is run. But
on real hardware, this is not the case. Could debian-installer-startup.d
scripts somehow wait for udev to have _completely_ discovered hardware?
(Or is it already the case, and should I then find out why my USB
devices are discovered late?)
Regards,
Samuel
Reply to: