Date: Sat, 19 Aug 2000 14:40:04 -0700 (PDT) From: Mike Meyer <mwm@mired.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/20710: mount output is to long, and "mount -v" is useless. Message-ID: <200008192140.OAA47497@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/20710; it has been noted by GNATS. From: Mike Meyer <mwm@mired.org> To: Bruce Evans <bde@zeta.org.au> 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. <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008192140.OAA47497>