On Mon, Oct 22, 2018 at 08:45:36AM +0200, Jan Stary wrote: > The wording of ifconfig DIAGNOSTICS can possibly baffle > a non-native speaker (such as me) with > > Messages indicating the specified interface does not exist, > > namely, only after parsing the (non)sentence does one realize > that the diagnostics consists of messages indicating THAT > the interface does not exist etc. > > As the paragraph does not list the messages (surely there are many), > this really boils down to mentioning that ifconfig does indeed have > diagnostic messages. > > I believe nothing would be lost > if this paragraph was deleted. > > Jan >
morning. i think if the text is confusing people, we could look at making it clearer. personally i think it's fine. sometimes you just need to reread a sentence. i don;t think there's anything there overly complicated or obscure. i agree the actual content is not that helpful. that's possibly because enumerating all possible diagnostics would be lengthy and/or impossible. still i think it gives a hint, and is better than nothing. so my opinion is it should stay. if anyone wants to submit diffs to improve it, or course we could look at that. jmc > > Index: ifconfig.8 > =================================================================== > RCS file: /cvs/src/sbin/ifconfig/ifconfig.8,v > retrieving revision 1.319 > diff -u -p -r1.319 ifconfig.8 > --- ifconfig.8 8 Sep 2018 15:21:03 -0000 1.319 > +++ ifconfig.8 22 Oct 2018 06:35:01 -0000 > @@ -1871,10 +1871,6 @@ Create the gif1 network interface: > Put the athn0 wireless interface into monitor mode: > .Pp > .Dl # ifconfig athn0 mediaopt monitor > -.Sh DIAGNOSTICS > -Messages indicating the specified interface does not exist, the > -requested address is unknown, or the user is not privileged and > -tried to alter an interface's configuration. > .Sh SEE ALSO > .Xr netstat 1 , > .Xr ifmedia 4 , >
