Re: Building kernel image packages with make-kpkg, custom dependency

[Cliff Flood <cliph@cli.ph>]

On Mon, Feb 15, 2010 at 2:11 AM, Tzafrir Cohen <tzafrir@cohens.org.il> wrote:
> On Fri, Feb 12, 2010 at 02:36:37PM -0500, Cliff Flood wrote:
>> Hi,
>>
>> I'm having some problems with building kernel image packages using `make-kpkg`
>>
>> I'm trying to build a package with a custom dependency and have tried
>> editing the control files generated by make-kpkg but find that these
>> changes don't make it into the produced package.
>>
>> So let me back up and explain what's going on.
>>
>> I need to distribute a custom kernel-img.conf to my systems (to ensure
>> they have "silent_modules" set to "yes" which will allow unattended
>> upgrades of kernels that match the one that is currently installed)
>> and I'm doing this by including kernel-img.conf in one of my parent
>> packages. This first version of this package that included this file I
>> wish to include as a dependency for my distributed kernel image
>> packages.
>
> What file(s) have you tried to edit? When?

I have attempted to add my dependency by editing the files
debian/contol and debian/Control

Both of these files are rewritten when I do a `fakeroot debian/rules
binary` to build the kernel.

>> While I'm on the topic I had another problem I have solved but if
>> there's a better way of doing this I'd like to hear it; On my systems
>> /boot is mounted RO so it must be remounted RW before a kernel can be
>> installed. I've achieved this by patching the "preinst" generated by
>> make-kpkg, is there a better way?
>
> Is it just /boot ? Or some other parts of the file system? What happens
> when you need to insall / upgrade grub?

Just /boot

Manually running something like `update-grub` results in error if
/boot isn't remounted RW first, and this is the step of the kernel
image install process I've had to work around as there doesn't seem to
be any hook for dealing with RO /boot

-- 
Cliff Flood