Message-ID: <696ad9ca@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> User-Agent: tin/2.6.5-20251224 ("Glenury") (Linux/2.4.31 (i586)) NNTP-Posting-Host: news.ausics.net Date: 17 Jan 2026 10:37:30 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 38 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.misc:81221 Marc Haber wrote: > not@telling.you.invalid (Computer Nerd Kev) wrote: >>Marco Moock wrote: >>> On 15.01.2026 03:14 rbowman rbowman wrote: >>>> ifconfig works fine for me and I don't have to read the whole damn ip >>>> man page to coax the info out of it. >>> >>> Some distributions do not ship it by default, but moved it to a >>> separate package. >> >>Some Linux distributions still ship with ifconfig and without ip. > > Which one? Tiny Core Linux. >>Plus ifconfig is common between different UNIX-type OSs. It looks >>like there's still no ip command in the BSDs, for example. > > 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? -- __ __ #_ < |\| |< _#