From owner-freebsd-audit Fri Feb 2 9:44:41 2001 Delivered-To: freebsd-audit@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4338D37B69F; Fri, 2 Feb 2001 09:44:23 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f12HiL945711; Fri, 2 Feb 2001 10:44:22 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102021744.f12HiL945711@harmony.village.org> To: Robert Watson Subject: Re: patch to remove setgid kmem from top Cc: Peter Pentchev , Thomas Moestl , freebsd-audit@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Feb 2001 12:21:08 EST." References: Date: Fri, 02 Feb 2001 10:44:21 -0700 From: Warner Losh Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Robert Watson writes: : As tools are migrated to using sysctl() for information retrieval, : allowing the setgid kmem bit to be removed, we've found resistance if the : tools then lose the ability to be used on dumps for post-mortem. Maybe we need to "support" an interface that is like sysctl, but that can get information out of vmcore.1 instead of the kernel. It would have to know the guts of how sysctl is implemented and it couldn't support "function call" sysctls. Then again, maybe I misunderstand how certain sysctls work, or don't realize that there are too many "function call" sysctls out there. Most of the ones I've ever dealt with were "just set the variable in the code" sorts. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message