Re: Debian kernel packaging: changes forthcoming in kernel-package 11.x

[maximilian attems <max@stro.at>]

heya manoj,

you didn't respond on my point putting the scripts under
/usr/share/kernel. this is a crucial decision.

initramfs-tools has both /etc/initramfs-tools/{hooks,scripts}
that take precendence over packaging files in
/usr/share//initramfs-tools/{hooks,scripts}
that allows very handy local configurabilty.

On Wed, 02 May 2007, Manoj Srivastava wrote:

> On Wed, 2 May 2007 10:11:11 +0200, maximilian attems <max@stro.at> said: 
> 
> > the default one unless other specified.
> 
>         Which generator is the default one? Right now, we have a
>  hard-coded algorithm that decides whether to use one or the other,
>  unless the user overrides it, and I want to move that decision making
>  logic (even if it is configurable) out of the postinst.

that is pretty clear by the logic of the postinst: initramfs-tools
is the default (popcon will tell that too ;) d-i uses it as default too.
afaik no other initramfs generator works on all release archs.

 
> > you don't talk at all in this proposal of /etc/kernel-img.conf do you
> > want to obsolete it?
> 
>         /etc/kernel-img.conf is to configure the action of the kerel
>  image postinst script.  If we move the running of the initrd
>  generators, bootloaders, symlink creators, etc out of the postinst,
>  then /etc/kernel-img.conf has no more say in what gets run.
> 
>         Again, /etc/kernel-img.conf is hard to modify automatically, and
>  I think would make the resulting image installation setup more rigid,
>  since no package really owns that script.

sure, thanks for clarification.
 
>         So, we can use alternatives to have bootloaders and
>  initrd-generators cooperate; so we don't have to have a over-arching
>  configuration. 

nack alternatives is not a scalable tool.
default unless /etc/kernel/initramfs overrides the default
/usr/share/kernel/initramfs
 
best regards

-- 
maks