Groups | Search | Server Info | Login | Register


Groups > comp.os.linux.networking > #8497

Re: ifconfig

From Richard Kettlewell <invalid@invalid.invalid>
Newsgroups comp.os.linux.networking
Subject Re: ifconfig
Date 2024-09-25 09:18 +0100
Organization terraraq NNTP server
Message-ID <wwvfrpojgdt.fsf@LkoBDZeT.terraraq.uk> (permalink)
References (1 earlier) <vc9t49$2vdno$4@dont-email.me> <vcah85$34j1e$4@dont-email.me> <vct60m$lcd$1@tncsrv09.home.tnetconsulting.net> <wwvv7ylcxvw.fsf@LkoBDZeT.terraraq.uk> <vcvvov$3qr$1@tncsrv09.home.tnetconsulting.net>

Show all headers | View raw


Grant Taylor <gtaylor@tnetconsulting.net> writes:
> On 9/24/24 02:29, Richard Kettlewell wrote:
>> I’m not sure how that would differ from the ifconfig that exists now.
>
> I read somewhere that the way that ifconfig / route / et al. work
> interfacing with the kernel differently

Yes, ifconfig uses ioctl, ip uses a netlink socket.

> and that these different methods are deprecated and will eventually be
> removed.

That hasn’t happened yet and in any case is an implementation detail; if
anyone cared to keep ifconfig &c going after that point, they could be
modified to use netlink instead.

(Linux has a fairly strong tradition against breaking the user-facing
API, but I don’t know if an exception exists in this case.)

>> AFAIK it still works as well as it always did[1], it just can’t
>> manage some of the more modern stuff.
>
> It has more to do with the back end in kernel space than it does the
> front end in user space.

I’ve no idea what this is supposed to mean. If you want it to provide
basic functionality in a backward compatible way it doesn’t matter what
kernel API it uses. At any rate, I think it does do that.

-- 
https://www.greenend.org.uk/rjk/

Back to comp.os.linux.networking | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

ifconfig faeychild <faeychild@nomail.afraid.org> - 2024-09-16 15:37 +1000
  Re: ifconfig Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2024-09-16 05:46 +0000
    Re: ifconfig faeychild <faeychild@nomail.afraid.org> - 2024-09-17 07:26 +1000
    Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-16 23:57 +0000
      Re: ifconfig Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2024-10-04 15:26 +0000
      Re: ifconfig Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2024-10-04 16:25 +0000
        Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-04 20:01 +0000
          Re: ifconfig Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2024-10-08 15:18 +0000
            Re: ifconfig faeychild <faeychild@nomail.afraid.org> - 2024-10-10 08:11 +1100
              Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-10 00:01 +0000
  Re: ifconfig Marco Moock <mm+usenet-es@dorfdsl.de> - 2024-09-16 20:24 +0200
    Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-17 00:07 +0000
      Re: ifconfig Grant Taylor <gtaylor@tnetconsulting.net> - 2024-09-23 20:52 -0500
        Re: ifconfig Richard Kettlewell <invalid@invalid.invalid> - 2024-09-24 08:29 +0100
          Re: ifconfig Grant Taylor <gtaylor@tnetconsulting.net> - 2024-09-24 22:24 -0500
            Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-25 06:45 +0000
            Re: ifconfig Richard Kettlewell <invalid@invalid.invalid> - 2024-09-25 09:18 +0100
        Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-24 21:00 +0000
          Re: ifconfig "Carlos E.R." <robin_listas@es.invalid> - 2024-09-25 07:22 +0200
  Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-17 00:02 +0000
  Re: ifconfig not@telling.you.invalid (Computer Nerd Kev) - 2024-09-18 07:46 +1000
  Re: ifconfig Antti Talsta <atalsta@nothingtosee.org> - 2024-09-23 16:46 +0000

csiph-web