From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: doc getsockopt, setsockopt
Date: Sat, 01 Oct 2005 09:06:56 +1000 [thread overview]
Message-ID: <87k6gyi29b.fsf@zip.com.au> (raw)
In-Reply-To: <rmiirwi35v0.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "30 Sep 2005 11:58:11 -0400")
Greg Troxel <gdt@ir.bbn.com> writes:
>
> NetBSD does not define SOL_IP. SOL_SOCKET is 0xffff. So from the
> NetBSD point of view, the right thing to do is define
> IPPROTO_{IP,UDP,TCP} as (constant) variables.
The posix spec at
http://www.opengroup.org/onlinepubs/007904975/functions/getsockopt.html
gives IPPROTO_TCP as an example, so yep, I'll remove the SOL bits in
favour of IPPROTO.
I'd noticed in the past the gnu/linux "man 5 protocols" says to use
/etc/protocols instead of numbers like IPPROTO, but what posix says
must trump that.
> NetBSD's Linux compatibility code indicates that SOL_IP is 0, but has
> a comment that these values can vary by architecture
That should be ok, we don't care about the actual values as long as
the constants are right.
> It would be interesting to hear what variables the Linux kernel
> actually compares to - IPPROTO_IP or SOL_IP.
Oh, well, there should be a better spec for the programming interface
than digging around the sources :-).
> 'man 7 ip' is Linux specific (it's ip(4) on BSD). Perhaps "Consult
> operating system documentation for these calls".
Thanks, I'll put "man ip" (there should be only one).
> MULTIADDR is the multicast group to be joined or left, and
> INTERFACEADDR is an IP adddress by which an interface will be found to
> perform the join/leave operation. INTERFACEADDR may be INADDR_ANY in
> which case the default interface will be used. These values are simply
> passed to the underlying system call, so extensions on some systems to
> specify interface by ifindex may be available.
Sounds fair.
> Or skip the last sentence, or the second half of it. People who
> understand specifying interfaces by ifindex will hopefully realize the
> portability issues of that.
Do you need to know about host vs network byte order to get it
through? That would be something to note.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-09-30 23:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 21:31 doc getsockopt, setsockopt Kevin Ryde
2005-09-30 15:58 ` Greg Troxel
2005-09-30 23:06 ` Kevin Ryde [this message]
2005-10-02 23:09 ` Greg Troxel
2005-10-03 1:10 ` Kevin Ryde
2005-10-03 23:46 ` Greg Troxel
2005-10-11 22:54 ` Kevin Ryde
2005-10-12 14:30 ` Greg Troxel
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k6gyi29b.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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.
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).