From owner-freebsd-current Wed Feb 22 14:48:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA07936 for current-outgoing; Wed, 22 Feb 1995 14:48:35 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id OAA07929; Wed, 22 Feb 1995 14:48:32 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Garrett Wollman cc: current@FreeBSD.org Subject: Re: mountd changes In-reply-to: Your message of "Wed, 22 Feb 95 15:35:31 EST." <9502222035.AA08329@halloran-eldar.lcs.mit.edu> Date: Wed, 22 Feb 1995 14:48:31 -0800 Message-ID: <7928.793493311@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > And what on earth is wrong with that? All a `mount' does is cover one > directory vnode with another; it seems rather pointless to have such > restrictions on it. (For that matter, I would like to see the > directory restriction lifted, too.) Sigh.. You can't tell me that this makes sense: $ mount freefall:/a /mnt $ mount freefall:/a /mnt $ mount freefall:/a /mnt $ mount freefall:/a /mnt $ df ... freefall:/a 1668222 569434 1015376 36% /mnt freefall:/a 1668222 569434 1015376 36% /mnt freefall:/a 1668222 569434 1015376 36% /mnt freefall:/a 1668222 569434 1015376 36% /mnt Jordan