As for the efficiency issue of netlink vs./proc, that has nothing whatsoever to do with the user interface. The implementation of the traditional tools could change and nobody would notice or care.
The problem of scripts parsing command output is a moot point too. Ok, so I have a script that parses the output of ifconfig. If the output has to change, there can either be a new tool or ifconfig itself changes. Either way, my script has to be changed. But slightly changing an existing tool will be far les
As has been the case since about 1996. You had time to learn.
That aside, net-tools is still installable in every distribution that no longer installs it by default.
The road to ruin is always in good repair, and the travellers pay the
expense of it.
-- Josh Billings
Poor reasoning (Score:0)
As for the efficiency issue of netlink vs. /proc, that has nothing whatsoever to do with the user interface. The implementation of the traditional tools could change and nobody would notice or care.
The problem of scripts parsing command output is a moot point too. Ok, so I have a script that parses the output of ifconfig. If the output has to change, there can either be a new tool or ifconfig itself changes. Either way, my script has to be changed. But slightly changing an existing tool will be far les
Re:Poor reasoning (Score:3)
Yes. I mean it would be mathematically impossible to introduce a new tool and leave the old one there too.
Re: (Score:2)
That aside, net-tools is still installable in every distribution that no longer installs it by default.