Message-ID: <696bf905@news.ausics.net> From: not@telling.you.invalid (Computer Nerd Kev) Subject: Re: "7 deprecated Linux commands you need to stop using - and what to use instead" Newsgroups: comp.os.linux.misc References: <10k93b3$9rp0$1@dont-email.me> <10kackp$3nav$1@paganini.bofh.team> <696961d0@news.ausics.net> <10kdc0i$1h5vb$1@news1.tnib.de> <696ad9ca@news.ausics.net> <10kfj4a$1npde$1@news1.tnib.de> User-Agent: tin/2.6.5-20251224 ("Glenury") (Linux/2.4.31 (i586)) NNTP-Posting-Host: news.ausics.net Date: 18 Jan 2026 07:03:01 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 27 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.misc:81252 Marc Haber wrote: > not@telling.you.invalid (Computer Nerd Kev) wrote: >>Marc Haber wrote: >>> ifconfig is common, but its parameters are different everywhere and >>> its output as well. >> >>Like most common UNIX commands are between different UNIX-type OSs. >> >>> Just having the same command name doesn't constitute an acceptable >>> interface. >> >>They work similarly and give you a start with what to look for. >>I've being playing with a 1990s UNIX-type OS lately and the >>ifconfig differences weren't a problem at all. Plus I at least >>know the command name so I can check the man page and see the >>differences, without starting from basics and needing to learn >>a completely different set of command names. Surely the advantage >>is obvious? > > So you would be fine with an ifconfig alias that maps to ip addr? That would still make the documentation hard to find (if you don't know to check if it's an alias anyway). -- __ __ #_ < |\| |< _#