From owner-freebsd-bugs Tue Aug 22 8:20: 8 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 0FBA137B422 for ; Tue, 22 Aug 2000 08:20:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA09825; Tue, 22 Aug 2000 08:20:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 22 Aug 2000 08:20:04 -0700 (PDT) Message-Id: <200008221520.IAA09825@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/20710: mount output is to long, and "mount -v" is useless. Reply-To: Sheldon Hearn 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: Sheldon Hearn To: Bruce Evans Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/20710: mount output is to long, and "mount -v" is useless. Date: Tue, 22 Aug 2000 17:17:19 +0200 On Sat, 19 Aug 2000 12:40:03 MST, Bruce Evans wrote: > > 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). > > > 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. Hi Bruce, Could you suggest how we should go forward with this? Your comments make it sound like you'd change _something_ about the status quo. Would you perhaps limit the printing of read and write information to verbose (-v) mode? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message