From owner-freebsd-current  Sat Oct  7 12:10:23 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA15501
          for current-outgoing; Sat, 7 Oct 1995 12:10:23 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA15493
          for <current@freebsd.org>; Sat, 7 Oct 1995 12:10:18 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA00629; Sun, 8 Oct 1995 05:07:50 +1000
Date: Sun, 8 Oct 1995 05:07:50 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199510071907.FAA00629@godzilla.zeta.org.au>
To: ache@astral.msk.su, current@freebsd.org
Subject: Re: procfs LKM broken now!
Sender: owner-current@freebsd.org
Precedence: bulk

>It calls _divdi3 function (procfs_vnops.c) and fail to load,
>because can't find it. Also libkern have such function, it seems
>that procfs_vnops.c is only file which call it, so, it isn't
>picked from libkern to kernel.
>Workaround is to add 'options PROCFS' to kernel config file.
>In this case _divdi3 picked from libkern.

This shows that a kernel library shouldn't be used if there are
lkm's.  The whole point of the library is to avoid linking to
unused functions, but lkms might use anything in the library
and this use is not detected when the kernel is linked.

Also, when individual .o's are used instead of a library, the
list of .o's must be bloated to include everything that an lkm
might need.

Bruce