From owner-freebsd-current Fri Nov 6 12:39:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28536 for freebsd-current-outgoing; Fri, 6 Nov 1998 12:39:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28528 for ; Fri, 6 Nov 1998 12:39:55 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id PAA01859; Fri, 6 Nov 1998 15:39:24 -0500 (EST) (envelope-from wollman) Date: Fri, 6 Nov 1998 15:39:24 -0500 (EST) From: Garrett Wollman Message-Id: <199811062039.PAA01859@khavrinen.lcs.mit.edu> To: Doug Rabson Cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: nfs.ko panics on unloading In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > code). Unfortunately the vfs system itself doesn't support unloading yet > (a project for someone there). It certainly did before! NFS never did, no, because there was no way to undefine a syscall, but when I first implemented VFS LKMs, you definitely could unload them (provided that the reference count was zero). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message