Bug 20710
| Summary: | mount output is to long, and "mount -v" is useless. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | mwm | ||||
| Component: | bin | Assignee: | Sheldon Hearn <sheldonh> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | 5.0-CURRENT | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
mwm
2000-08-18 22:40:01 UTC
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). > 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. Bruce 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 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.
On Tue, 22 Aug 2000, Sheldon Hearn wrote:
> 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?
I wouldn't change more than that. `mount' with no args has shown the
mount options since the beginning of history.
Bruce
Responsible Changed From-To: freebsd-bugs->sheldonh I'll take this one. State Changed From-To: open->feedback Mike, are you happy with rev 1.40 of mount.c ? State Changed From-To: feedback->analyzed Once we're happy that this breaks as little as we think it does in -CURRENT, we can merge it onto RELENG_4. State Changed From-To: analyzed->closed Merged onto RELENG_4 in rev 1.39.2.1. |
