On Wed, 2009-09-30 at 11:57 +1300, Philip Dowie wrote:
If you have tool that works and delivers relevant info, why abandon it just write scripts to do what has already been done? Why reinvent the wheel?
An attitude that would freeze progress. And ifconfig, ip, et al... are reading their information from /proc or /sys anyway. If you want to write solid utilities, or scripts, you don't frog around trying to parse the [variable] output of some utility you just go straight to the source.
Anyhow, I don't want this be a flame war. I only hope 'ifconfig' sticks around for a while. A long while. I asked earlier if ifconfig uses depricated APIs. Nobody knows, or nobody has answered. If it does, then when the depricated APIs are finally actually removed from the kernel, then ifconfig will break.
I don't know about "deprecated" I know what I've been told, and read, but people more knowledgeable than me.
If it doesn't use depricated APIs, then there is nothing to stop you from grabbing the source and compiling it yourself
Somehow that is easier than just using/learning the newer tool?
once it is removed from the distribution. ifconfig (part of net-tools) hasn't been actively developed since 2001, ip (from iproute2) has been available since the 2.4.x series kernels, so I'd suspect that ifconfig does make use of depricated APIs.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org