On Wed, May 23, 2012 at 2:25 PM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
2012/5/23 Richard Shaw <hobbes1069(a)gmail.com>:
> On Wed, May 23, 2012 at 10:22 AM, Richard Shaw <hobbes1069(a)gmail.com> wrote:
>> I'm attempting to update my ZFS kmod packages and I released that for
>> the akmods package I also need a systemd service file so that it runs
>> early enough, but also so that the SPL kmod is built before the ZFS
>> kmod.
>>
>> kmodtool doesn't give me any way to modify what files are packaged for
>> the akmods package.
>>
>> I guess the simplest solution would be to create an additional package
>> with just the service file and make sure the kmod-spl and kmod-zfs
>> packages require it?
>
> The short answer is, "you don't".
>
> Apparently, when akmods builds the package is automatically installs
> all the packages that are generated other than the debuginfo packages.
> I just created a <kmod-name>-systemd package and now everything's
> happy.
Why it is not easier to consider that akmods built on shutdown or
kernel-devel installation instead to recreate the kernel module
loading process ?
I guess we could ask the same question about why we try to run akmods
on startup at all?
As far as on shutdown goes, I remember reading on a bug report that
building on shutdown may be bad since it will stall the shutdown until
complete. If you have many akmods, that might be a while. If this
isn't as much of a problem than reported, then I could adjust the
systemd service files to run on shutdown instead.
The biggest problem with trying build on kernel update is that the
akmods script in /etc/kernel/postinst.d may not build them in the
right order.
Richard