From: Alex Plotnick <shrike@netaxs.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Patch for network-interface-{list,info}
Date: Tue, 18 Nov 2003 00:49:40 -0500 [thread overview]
Message-ID: <46933.699414558$1069134801@news.gmane.org> (raw)
In-Reply-To: <m3k75zyyij.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "17 Nov 2003 13:23:32 +0100")
storm@cua.dk (Kim F. Storm) writes:
> It's definitely a cleaner interface, yes, and maybe it is as widely
> available as SIOCGIFCONF these days...?
I agree that it's much cleaner. As far as I know, the free BSDs all have
it, and it's in glibc on GNU/Linux. Irix doesn't have it; I don't know
about Solaris.
> But in any case, since network-interface-list is a new addition in CVS
> emacs, I think it would be alright for us to restrict its availability
> to those systems which do support getifaddrs.
This seems reasonable to me. If anyone knows of a good reason why this is
not an acceptable course of action, please let me know.
> How does getifaddrs return the hw address? In ifaddr->ifa_data ?
> Is that portable? If not, maybe it could use SIOCGIFHWADDR as
> a fallback.
getifaddrs() actually returns *two* entries for each interface: one
describes the layer-3 address, and the other the link-layer address. Which
one is which is determined by examining the sa_family of the given sockaddr
(ifa_addr). On BSD, this sockaddr is actually a struct sockaddr_dl and has
family AF_LINK, whereas on GNU/Linux it's an AF_PACKET and is described by
a struct sockaddr_ll. There's no need to muck around with the raw ifa_data
field.
> If you want to modify network-interface-list and -info according to
> the suggestions above, I would appreciate it.
I'll send a patch in the next day or two.
> Are you interested in signing papers for your changes?
This is no problem. If the relevant party contacts me privately via email,
I'll be happy to provide a mailing address for whatever paperwork is
necessary.
Thanks,
Alex Plotnick
next prev parent reply other threads:[~2003-11-18 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ad6w2hm6.fsf@Dora.local.>
2003-11-17 12:23 ` Patch for network-interface-{list,info} Kim F. Storm
2003-11-18 5:49 ` Alex Plotnick [this message]
[not found] ` <8765hi2pl7.fsf@Dora.local.>
2003-11-18 9:46 ` Kim F. Storm
2003-11-16 20:17 Alex Plotnick
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='46933.699414558$1069134801@news.gmane.org' \
--to=shrike@netaxs.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).