Re: [base pkg] update !GENERIC kernel

From: Ben Woods <woodsb02_at_gmail.com>
Date: Wed, 19 Jul 2017 23:05:32 +0000
On Wed, 19 Jul 2017 at 7:37 pm, Boris Samorodov <bsam_at_passap.ru> wrote:

> Hi All,
>
> I use self-made base packages for an ARM board. The kernel I use
> is IMX6 one. While pkg update I get this:
> ---
> [271/302] Upgrading FreeBSD-kernel-imx6-debug from 12.0.s20170718113533
> to 12.0.s20170719070514...
> [271/302] Extracting FreeBSD-kernel-imx6-debug-12.0.s20170719070514:
> 100%
> kldxref: //boot/kernel: No such file or directory
> pkg: POST-INSTALL script failed
> [272/302] Upgrading FreeBSD-kernel-imx6 from 12.0.s20170718113533 to
> 12.0.s20170719070514...
> [272/302] Extracting FreeBSD-kernel-imx6-12.0.s20170719070514: 100%
>
> kldxref: //boot/kernel: No such file or directory
> pkg: POST-INSTALL script failed
> ---
>
> All is fine except those messages.
>
> There is no /boot/kernel, but there is /boot/kernel.IMX6. The kernel
> is defined at /boot/loader.conf:
> ---
> kernel="kernel.IMX6"
> ---
>
> Seems that for now pkg can't handle non-default kernel. Should I just
> ignore those messages? Or should I run some post-update commands/scripts
> by hand?


I had the same problem on my machine using pkg-base with a non-default
named kernel package.

As a workaround, I created a symlink at /boot/kernel pointing to the
correct kernel directory. This seemed to fix the problem, but required this
manual intervention.

It would be good if this wasn't required, and the kernel package used the
kernel parameter in loader.conf to determine where to run the post-install
script.

Regards,
Ben
-- 

--
From: Benjamin Woods
woodsb02_at_gmail.com
Received on Wed Jul 19 2017 - 21:05:45 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:12 UTC