From owner-freebsd-arch Mon Jul 29 7:59:35 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 802B037B400 for ; Mon, 29 Jul 2002 07:59:32 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 551A543E3B for ; Mon, 29 Jul 2002 07:59:32 -0700 (PDT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id 2C83EAE27E; Mon, 29 Jul 2002 07:59:32 -0700 (PDT) Date: Mon, 29 Jul 2002 07:59:32 -0700 From: Maxime Henrion To: freebsd-arch@FreeBSD.org Subject: lsvfs(1) removal ? Message-ID: <20020729145932.GP42325@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-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I have been doing some work in my perforce mux_nmount branch on struct vfsconf. I had to create a struct xvfsconf for userland because the consequences of an ABI breakage for struct vfsconf are really horrible (in short, none of the mount(8) utilities would work). I've also redesigned the way it is exported to userland (vfs_sysctl() was just a huge pile of crap) and converted the userland utilities to use the new API. I was about to convert lsvfs(1) too but after having thought about it, I'd rather remove it entirely. It doesn't seem to serve any useful purpose except being able to tell which filesystem the running kernel supports, which can be as easily done with kldstat -v. So I intend to remove lsvfs(1) unless someone has sensible objections. Maxime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message