From owner-cvs-all  Sun Jan 31 02:00:39 1999
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA05759
          for cvs-all-outgoing; Sun, 31 Jan 1999 02:00:39 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05753;
          Sun, 31 Jan 1999 02:00:28 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA04835;
	Sun, 31 Jan 1999 21:00:23 +1100
Date: Sun, 31 Jan 1999 21:00:23 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901311000.VAA04835@godzilla.zeta.org.au>
To: bde@zeta.org.au, newton@atdot.dotat.org
Subject: Re: cvs commit: src/sys/kern sys_socket.c kern_exit.c kern_resource.c
Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, newton@FreeBSD.ORG
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

> > >  Added comments about non-staticization so it doesn't get un-done next
> > >  time someone goes on a staticization binge.
> > ...
> > This is bogus.  Candidates for staticization are determined by inspecting
> > all system objects and sources for (lack of) cross references using
> > tools/kernxref and/or grep.
>
>KLDs included?

Not currently.  It supports standard LKMs (ones which were installed in
/lkm), but has rotted.  This shouldn't matter because all modules should
be statically compilable and statically compiled into LINT.  It can't
support nonstandard modules of course, since a weird module could want
to reference all functions and objects in the kernel.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message