Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 May 2009 15:05:17 -0500
From:      Scot Hetzel <swhetzel@gmail.com>
To:        QAT@freebsd.org
Cc:        ports@freebsd.org, cvs-ports@freebsd.org, imp@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org
Subject:   Re: cvs commit: ports/net Makefile ports/net/bwi-firmware-kmod  Makefile distinfo pkg-descr pkg-plist
Message-ID:  <790a9fff0905101305l70d7809cl1ca2525729d53daa@mail.gmail.com>
In-Reply-To: <20090510162002.A2CAA8FC4E@release.ixsystems.com>
References:  <200905092141.n49LfomV031060@repoman.freebsd.org> <20090510162002.A2CAA8FC4E@release.ixsystems.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Sun, May 10, 2009 at 11:20 AM,  <QAT@freebsd.org> wrote:
> ================================================================
> ====================<phase 6: make install>====================
> add_pkg
> ===>  Installing for bwi-firmware-kmod-3.130.20
> ===>   Generating temporary packing list
> ===>  Checking if net/bwi-firmware-kmod already installed
> install -o root -g wheel -m 555   bwi_v3_ucode.ko /boot/modules
> kldxref /boot/modules
> ===>   Registering installation for bwi-firmware-kmod-3.130.20
> ================================================================
> ====================<phase 7: make package>====================
> ===>  Building package for bwi-firmware-kmod-3.130.20
> Creating package /tmp/packages/All/bwi-firmware-kmod-3.130.20.tbz
> Registering depends:.
> Creating bzip'd tar ball in '/tmp/packages/All/bwi-firmware-kmod-3.130.20.tbz'
> Deleting bwi-firmware-kmod-3.130.20
> ================================================================
>
> === Checking filesystem state
> list of extra files and directories in / (not present before this port was installed but present after it was deinstalled)
> 33067887        4 -rw-r--r--    1 root             wheel                  88 May 10 16:20 boot/modules/linker.hints
> ================================================================

This shouldn't be flaged as an mtree error.  The reason that
linker.hints was left behind is due to this file is generated by
kldxref.  The port/package runs kldxref during the install of the
firmware module to update the existing or create a linker.hints file,
and when the package is removed, it runs kldxref again to clean up the
linker.hints file to only contain the modules in /boot/modules.  It
has no way to know if it is safe to remove this file.

Should Kernel Modules be running kldxref in /boot/modules?

Should I change the port to have a do-install target that installs the
bwi firmware kernel module so that it doesn't run kldxref during the
install?

Scot


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0905101305l70d7809cl1ca2525729d53daa>