From owner-freebsd-current Tue Feb 23 1:31:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id DF3AE10E88 for ; Tue, 23 Feb 1999 01:31:49 -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 UAA05470; Tue, 23 Feb 1999 20:31:46 +1100 Date: Tue, 23 Feb 1999 20:31:46 +1100 From: Bruce Evans Message-Id: <199902230931.UAA05470@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: Problems with nfsstat and dynamic OID Cc: current@freebsd.org, mike@smith.net.au, romanp@wuppy.rcs.ru Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >I fixed this a while back to use sysctlbyname, as it should have been >> >done. Bruce subsequently backed it out (bad idea, IMO). >> >> You only worked around the previous breakage of vfs sysctls for the >> statically configured case. The dynamically configured case was more >> fundamentally broken (sysctls were not wired at all). Other applications >> that use vfs sysctls, e.g., mountd(8), remained broken in all cases. > >Even then, only NFS' sysctls were 'fixed' to use vfc_typenum as their oid >numbers. Other filesystems with sysctls such as ufs were still 'broken'. Except there weren't any such filesystems at the time. Now that ffs's reallocblks is enabled, there are vfs.ffs.doreallocblks and vfs.ffs.doasyncfree, but these weren't and aren't a problem because ffs can't be an LKM er KLD, and there is no need to access them at the library level. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message