From owner-freebsd-current Thu May 2 13:17:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 4547637B96B for ; Thu, 2 May 2002 13:14:36 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1920) id 0D2FFAE1D1; Thu, 2 May 2002 13:14:15 -0700 (PDT) Date: Thu, 2 May 2002 13:14:15 -0700 From: Maxime Henrion To: current@FreeBSD.org Subject: HEADS UP: mount_std(8) consumers conversion to nmount Message-ID: <20020502201415.GH63621@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am going to commit patches that convert all the mount_std consumers to the nmount framework; namely devfs, fdescfs, linprocfs and procfs. This results in an ABI breakage, so you need to update your mount_std(8) utility. I have changed mount_std(8) to try a mount() call first, and then a nmount() call in revision 1.13 of mount_std.c. If you rebuilt it since (this commit was done the 7th of April), you're safe. If you didn't, you will not be able to mount these filesystems anymore. Please note that even if you updated it, you will get some warnings from the kernel since it tries mount() before nmount(). Once these commits are done, I'll change the order of the calls to get rid of these warnings. I will still keep the mount() call for some time, in the case there are external filesystems using mount_std. Thanks for your attention, Maxime Henrion To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message