mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Proposed roadmap to 1.0
Date: Wed, 24 Jul 2013 12:04:09 -0400	[thread overview]
Message-ID: <20130724160409.GW3249@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130724232942.45f4b7ba@sibserver.ru>

On Wed, Jul 24, 2013 at 11:29:42PM +0800, orc wrote:
> > > getifaddrs() does not returns AF_PACKET like glibc does, so list of
> > > all system interfaces is incomplete (does not shows inactive
> > > interfaces).
> > 
> > Is there a use case you want this for? I remember when we added
> > getifaddrs this was discussed, and I was hesitant to add AF_PACKET
> > because it's using some deprecated version of some structure where the
> > fields are too small to store the values they're supposed to
> > represent. I'd have to look through the mailing list and/or IRC logs
> > to recall the details, though. I'm not entirely opposed to it if
> > there's a serious need, but at the time it seemed like a poorly
> > designed interface.
> 
> I faced problem when I tried to build dhcpcd with musl. I
> dropped dhcpcd then, found simple default.script for udhcpc and forgot
> about any problems.

Do you know what dhcpcd needs it for? If it's just automatic binding
when you don't specify an interface, that's probably a bad idea
anyway... But maybe we should support it.

> > > I attached patch for getaddrinfo() (adopt it if you need it)
> > > and test program.
> > 
> > I think it could be cleaner/simpler but I might just commit it as-is
> > for now and wait to clean it up until the getaddrinfo cleanup/overhaul
> > which was scheduled for this release cycle but will get pushed back to
> > the next.
> 
> Thanks for review. I think I can apply it now on server :)

I didn't really "review" it, but as long as you tested it, it's
probably fine. There are only 3 possible code paths here, not an
infinite family of them, so as long as each of the 3 works for you
it should be fine.

Rich


  reply	other threads:[~2013-07-24 16:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29 23:50 Rich Felker
2013-06-30  2:53 ` Rob Landley
2013-06-30  3:01   ` Rich Felker
2013-06-30  5:20 ` Isaac
2013-06-30  5:34   ` Rich Felker
2013-06-30  6:42     ` Isaac
2013-06-30  7:21       ` Justin Cormack
2013-06-30 12:02         ` Rich Felker
2013-07-04 18:13         ` Rob Landley
2013-07-07 20:25           ` Isaac
2013-07-04 18:10       ` Rob Landley
2013-07-07 20:30         ` Isaac
2013-06-30  9:24     ` Rob Landley
2013-06-30 10:45     ` Szabolcs Nagy
2013-06-30 21:29       ` Luca Barbato
2013-07-05 15:12   ` Rob Landley
2013-06-30  5:49 ` Strake
2013-07-17 16:02 ` Rich Felker
2013-07-24 18:36   ` Rob Landley
2013-07-24 19:47     ` Rich Felker
2013-07-25  7:25       ` Daniel Cegiełka
2013-07-25  7:40         ` Rich Felker
2013-07-27  5:30       ` Rob Landley
2013-07-25 10:29     ` Timo Teras
2013-07-24 14:14 ` orc
2013-07-24 14:42   ` Rich Felker
2013-07-24 15:29     ` orc
2013-07-24 16:04       ` Rich Felker [this message]
2013-07-24 16:25         ` orc
2013-07-24 19:41           ` Rich Felker

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=20130724160409.GW3249@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).