From owner-freebsd-current Sat May 16 04:39:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02902 for freebsd-current-outgoing; Sat, 16 May 1998 04:39:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02876; Sat, 16 May 1998 04:39:17 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id TAA02040; Sat, 16 May 1998 19:39:07 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805161139.TAA02040@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG, kkennawa@physics.adelaide.edu.au Subject: Re: libc corruption In-reply-to: Your message of "Sat, 16 May 1998 19:40:10 +1000." <199805160940.TAA11548@godzilla.zeta.org.au> Date: Sat, 16 May 1998 19:39:06 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >To make it a little easier, perhaps have libc's syscall tables explicitly > >generated from the kernel sources and committed. That should make it > >a no-brainer to keep them in sync and yet will stop accidental leakage > >from the kernel into libc. > > Better yet, generate the tables explicity and don't commit them anywhere. > That should make it a no-brainer to keep them in sync and stop accidental > blockage of the flow from the kernel into libc :-). This is the present situation and it's not working very well. Generating vnode_if.[ch] is another annoyance that I'd like to see eradicated. > Bruce -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message