[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#353942: sigh, udev..

On Feb 22, Joey Hess <joeyh@debian.org> wrote:

> > If the problem is only passing parameters from the kernel command line
> > then you can solve this with a script which parses it and writes the
> > parameters to a file in /etc/modprobe.d/.

> Another way to do this might be to tag parameters on the command line
> with the module they apply to. Matthew Wilcox suggests in this bug
> report that libata.atapi_enabled=1 will send that parameter to the
> libata driver if it's compiled in; I wasn't aware of this syntax before.
> Is it documented somewhere (kernel source file is fine ;-) and does it
> work for other module parameters? Seems we could just parse that if so.
Yes, this is what I suggested to do.

> (Hmm, we also currently only write those entered module parameters to
> the installed system's /etc/modutils/, not to its /etc/modprobe.d/,
> wonder if we should change that too..)
If you want to support 2.6 kernels then it would be a good idea, yes.

> Then yes, that might work. I can sort of see how to do a. -- make
> udevsynthesize avoid doing anything with block devices. Doing b.
This was my idea too.

(BTW, are there any news about dh_installudev? Do you need help?)


Attachment: signature.asc
Description: Digital signature

Reply to: