From owner-cvs-sys Fri Mar 17 20:16:34 1995 Return-Path: cvs-sys-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA10808 for cvs-sys-outgoing; Fri, 17 Mar 1995 20:16:34 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA10802; Fri, 17 Mar 1995 20:16:29 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id UAA20285; Fri, 17 Mar 1995 20:16:04 -0800 From: "Rodney W. Grimes" Message-Id: <199503180416.UAA20285@gndrsh.aac.dev.com> Subject: Re: cvs commit: src/sys/libkern locc.c random.c scanc.c skpc.c libkern.h To: davidg@Root.COM Date: Fri, 17 Mar 1995 20:16:04 -0800 (PST) Cc: CVS-commiters@freefall.cdrom.com, cvs-sys@freefall.cdrom.com In-Reply-To: <199503180406.UAA00419@corbin.Root.COM> from "David Greenman" at Mar 17, 95 08:06:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1710 Sender: cvs-sys-owner@freebsd.org Precedence: bulk > > >> NOT! IMNSHO, copying files out of libc for the kernel is extremely evil. > > > >That was what Berkeley intended when they did this, if you have doubts go > >read /usr/src/lib/libc/Makefile, targets libkern:, libkern.gen, and > >libkern.${MACHINE}... the one of real interest here is: > > Did I say I had any doubt? No, I'm quite aware of this. I just happen not > to agree with it. I was *shocked* when I first heard about it last year, and > I remain incredulous. > It's bad enough that we have a libkern in the first place, and it's a lot > worse that it has all of these contortions. I personally prefer to know > exactly what is going to be in the kernel and find it more than a little > obnoxious to have an unknown set of .o's included out of libkern.a, and quite > evil for the sources to come out of libc. I'm willing to live with the pot-luck > .o's, but I'm not willing to live with them coming from libc. Above I was just stating and pointed to what Berkeley had intended to be done with respect to libkern, I am in no way agreeing that what they did was a good idea. You should know from the very early days of the 4.4 migration of FreeBSD that I am in total agreement with you on this issue, I think we both got pretty sick when we looked at it. I think we should just stop building libkern, and for machines that need routines from there add them to sys/i386/files.i386. For people doing a new port it is nice to have these generic C functions around, but other than that I see libkern.a as an evil thing to have done. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD