mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: if_nameindex/getifaddrs and dhcpcd issue
Date: Thu, 10 Apr 2014 03:52:30 -0400	[thread overview]
Message-ID: <20140410075230.GN26358@brightrain.aerifal.cx> (raw)
In-Reply-To: <20140410073251.GM21662@example.net>

On Thu, Apr 10, 2014 at 09:40:22AM +0200, u-igbb@aetey.se wrote:
> On Wed, Apr 09, 2014 at 06:20:41PM -0400, Rich Felker wrote:
> > Does if_nameindex "work" (modulo the issues with it) on BSD linux
> > emulation now, and would it fail if we switched to netlink or /proc
> > based? This is not necessarily a show-stopper but it would be nice if
> > we had a workaround, and it's something where we should have input
> > from users running musl binaries on BSD.
> 
> I'm not aware of which of the binaries may be calling if_nameindex. The
> ones which are being used continuously are Samba and Coda servers running
> on FreeBSD (for the sake of ZFS), their current production versions are
> still linked to uclibc.
> 
> Occationally I run "everything" i.e. a whole user environment in the
> form of Linux binaries on NetBSD but it will take some time before this
> happens and I test if_nameindex there.

I think these functions are mainly useful for network-configuration
utilities, not general user-facing apps. But I do want to make things
work for users who want to run a complete userspace of musl-linked
linux binaries on a BSD kernel.

At the moment I'm leaning towards a netlink-based approach despite my
moderate disgust with the netlink API simply because the alternative
(/proc) does not seem as possible as I thought it was; I can't see any
way to get a good parsable list of devices, including unconfigured
devices and aliases/multi-addresses, from /proc. If somebody knows how
and has a proposal for how it could be done, please speak up.

Rich


  reply	other threads:[~2014-04-10  7:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08  9:11 Natanael Copa
2014-04-08 10:07 ` Justin Cormack
2014-04-08 12:25   ` Timo Teras
2014-04-08 14:23     ` Natanael Copa
2014-04-08 15:45     ` Rich Felker
2014-04-08 16:08       ` Timo Teras
2014-04-08 16:19         ` Justin Cormack
2014-04-08 22:41           ` Rich Felker
2014-04-09  7:17             ` u-igbb
2014-04-09 22:20               ` Rich Felker
2014-04-09 22:32                 ` Justin Cormack
2014-04-10  7:40                 ` u-igbb
2014-04-10  7:52                   ` Rich Felker [this message]
2014-04-09 14:02         ` Timo Teras
2014-04-10  0:55           ` Rich Felker
2014-04-09  7:55       ` Natanael Copa
2014-04-08 12:54   ` Szabolcs Nagy
2014-04-08 13:42   ` Rich Felker
2014-04-08 14:16     ` Justin Cormack
2014-04-08 15:38       ` Rich Felker
2014-04-09  7:13         ` Natanael Copa
2014-04-09 22:18           ` Rich Felker
2014-04-08 21:16     ` Natanael Copa
2014-04-08 21:30       ` Justin Cormack
2014-04-08 22:59         ` Rich Felker
2014-04-08 14:27   ` Natanael Copa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140410075230.GN26358@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).