From owner-cvs-all Sun Jan 31 05:56:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01230 for cvs-all-outgoing; Sun, 31 Jan 1999 05:56:25 -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 FAA01204; Sun, 31 Jan 1999 05:56:12 -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 AAA20202; Mon, 1 Feb 1999 00:56:09 +1100 Date: Mon, 1 Feb 1999 00:56:09 +1100 From: Bruce Evans Message-Id: <199901311356.AAA20202@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. > >Ah, well there's the rub (and the crux of Eivind's message to me >which prompted me to comment the unstaticizations). No problem. Just fix kernxref before using it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message