From owner-freebsd-current  Mon May 25 09:03:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA11451
          for freebsd-current-outgoing; Mon, 25 May 1998 09:03:48 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA11443
          for <current@freebsd.org>; Mon, 25 May 1998 09:03:45 -0700 (PDT)
          (envelope-from imp@village.org)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0ydziy-00021C-00; Mon, 25 May 1998 10:03:44 -0600
Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA20388 for <current@freebsd.org>; Mon, 25 May 1998 10:03:04 -0600 (MDT)
Message-Id: <199805251603.KAA20388@harmony.village.org>
To: current@FreeBSD.ORG
Subject: boot message
Date: Mon, 25 May 1998 10:03:04 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Should I worry about:

struct nfsmount bloated (> 512bytes)
Try reducing NFS_MUIDHASHSIZ

when I boot a new kernel?

Warner

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message