From owner-freebsd-current Mon Aug 16 22:45:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7312E155BE for ; Mon, 16 Aug 1999 22:45:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id HAA23241; Tue, 17 Aug 1999 07:43:20 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Andrzej Bialecki , current@FreeBSD.ORG Subject: Re: Q: Extending the sysctl MIB for Linuxulator variables In-reply-to: Your message of "Mon, 16 Aug 1999 15:17:54 PDT." <199908162217.PAA01159@dingo.cdrom.com> Date: Tue, 17 Aug 1999 07:43:20 +0200 Message-ID: <23239.934868600@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908162217.PAA01159@dingo.cdrom.com>, Mike Smith writes: >> I think that is too obscure considering the exposure this will get. > >What "exposure"? It's a backend to a tuning interface for our ABI >compatibility... We will be judged on how well we run linux more than many other sane factors in the future. >>From the perspective of an integrated namespace, we've already made the >wrong moves insofar as vm.* should be kern.vm.*, vfs.* should be >kern.vfs.*, etc. Either the entire kernel namespace should have a >presumed leading kern. (and the existing kern.* nodes need to move) or >we should relocate stuff to reflect a more ubuquitous naming >arrangement. You know, all your argument here supports is that the "kern" toplevel tree is a mistake :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message