On Thu, Dec 29, 2016 at 11:09:35PM +0000, Wookey wrote: > Yeah I think that mess is why I've never felt any need to move away > from ifconfig. I ran ip something a few times, went 'huh?' at the cryptic > output and stayed with the rather more civilised /sbin/ifconfig. > > So it seem that the output does actually label things, but the things > and labels look exactly the same. Would some colons really have hurt > too much? > > i.e. mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 > is really > mtu: 1500 qdisc: mq state: UP mode: DEFAULT group: default qlen: 1000 > > Anyone think the latter is a tad clearer? I still don't know what a > qdisc is or a default group, but it's a lot easier to find things I do > recognise. Before this discussion I just saw it as a mysterious jumble > of 10 things (after a set of things in CAPITALS that were somewhat > mysterious too (what's a LOWER_UP, I wonder) - who knows what it might > mean.
Do you really think that
wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.** netmask 255.255.255.0 broadcast 192.168.**
inet6 fe80::** prefixlen 64 scopeid 0x20<link>
ether e4:**:ca txqueuelen 1000 (Ethernet)
RX packets 66323088 bytes 90518262611 (84.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18425793 bytes 2920636610 (2.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
is clearer than
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether e4:***:ca brd ff:ff:ff:ff:ff:ff
inet 192.168**/24 brd 192.168.** scope global dynamic wlp3s0
valid_lft 70216sec preferred_lft 70216sec
inet6 fe80:**/64 scope link
valid_lft forever preferred_lft forever
?
To me they are the same. Note that ifconfig too has cryptic uppercase jumble
and cryptic lowercase jumble and doesn't have any separators between field
names and values.
--
WBR, wRAR
signature.asc
Description: PGP signature
