Date: Wed, 19 Jul 100 01:56:16 +0200 (CEST) From: Renaud Waldura <renaud@guppy.evolunet.com> To: ras@e-gerbil.net (Richard A. Steenbergen) Cc: gcorcoran@lucent.com, mph@astro.caltech.edu, freebsd-net@FreeBSD.ORG Subject: Re: "ifconfig" == "ifconfig -a" Message-ID: <200007182356.BAA14966@guppy.evolunet.com> In-Reply-To: <Pine.BSF.4.21.0007181924180.95155-100000@overlord.e-gerbil.net> from "Richard A. Steenbergen" at "Jul 18, 0 07:26:03 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, 18 Jul 2000, Gary T. Corcoran wrote: > > > Hmmm.... what about having "route" with no parameters just > > give a helpful message, something like "To see the current > > routing table, use the netstat(1) command.". ?? > > If nothing else, it is in no way intuitive that "route" says nothing about > how to view the current routing table. This is one of the most common new > FreeBSD user questions I hear. At a minimium, something should be hinted > at in the man page. And in an ideal world, the "route" command should do what its name suggests: deal with routes, and that includes printing them IMHO. I hate code/functionnality duplication as much as the next guy, but having to call a command totally unrelated to "route" to display the routing table (ie. netstat) has always struck me as a gratuitous twist. I cast my vote for a "route print". -- -- Renaud Waldura <renaud@waldura.org> -- 610 Clipper St. Suite 19 -- San Francisco CA 94114 -- USA -- phone +1 415 642-5364 -- fax +1 415 642-5364 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007182356.BAA14966>