From owner-freebsd-questions Sat Feb 6 15:54:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08511 for freebsd-questions-outgoing; Sat, 6 Feb 1999 15:54:35 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08500 for ; Sat, 6 Feb 1999 15:54:26 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id AAA85914; Sun, 7 Feb 1999 00:54:21 +0100 (CET) (envelope-from des) To: "John Barbee" Cc: Subject: Re: Sharity and NFS References: <000201be5214$0bbf9100$0700a8c0@farpoint> From: Dag-Erling Smorgrav Date: 07 Feb 1999 00:54:21 +0100 In-Reply-To: "John Barbee"'s message of "Sat, 6 Feb 1999 13:02:46 -0800" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John Barbee" writes: > All that happened, based on the logs, was that there was a couple of > restarts. The kernel config file's date is November 7th. The kernel's date > was November 7th. Sharity's programmer says that I must've had NFS support > otherwise it would not have worked. Is there anyway, with my kernel config > above that limited NFS support was included that could explain how Sharity > worked and then all of the sudden stopped working? kldload nfs DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message