From owner-freebsd-bugs Sat Aug 19 14:40: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 07A8D37B424 for ; Sat, 19 Aug 2000 14:40:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA47497; Sat, 19 Aug 2000 14:40:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sat, 19 Aug 2000 14:40:04 -0700 (PDT) Message-Id: <200008192140.OAA47497@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mike Meyer Subject: Re: bin/20710: mount output is to long, and "mount -v" is useless. Reply-To: Mike Meyer Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/20710; it has been noted by GNATS. From: Mike Meyer To: Bruce Evans Cc: mwm@mired.org, FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/20710: mount output is to long, and "mount -v" is useless. Date: Sat, 19 Aug 2000 16:34:56 -0500 (CDT) Bruce Evans writes: > On 18 Aug 2000 mwm@mired.org wrote: > > >Description: > > > > The "mount" command to get a list of mounted file systems now > > outputs lots of information, making the critical stuff - the > > actual mount points - hard to find. > The stuff about reads and writes takes too much space and doesn't really > belong in mount(8). That's a reasonable way to look at things. I thought about patching it so that the options showed up without the -v, then decided not to. But where should you get that information from? > > Also, the command "mount -v" and the command "mount" do the > > exact same thing. This seems like such a waste. > This is because mount with no args essentially applies -v. -v only makes > a difference for mounting a single filesystem. Um - not after you apply the patch I sent. That's was the point of using -v - it wasn't doing anything in that situation anyway.