NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

misc/39327: incoherent socket man pages

>Number:         39327
>Category:       misc
>Synopsis:       incoherent socket man pages
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Aug 09 18:40:00 +0000 2008
>Originator:     Martin S. Weber
>Release:        NetBSD 4.99.69
System: NetBSD 4.99.69 NetBSD 4.99.69 (GENERIC) #2: Mon Jul 
14 16:54:25 CEST 2008 
root@rfhinf038:/fsim/data/netbsd/obj/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
when reading socket(2), it says:
        The protocol specifies a particular protocol to be used with the socket.
        Normally only a single protocol exists to support a particular socket
        type within a given protocol family.  However, it is possible that many
        protocols may exist, in which case a particular protocol must be speci-
        fied in this manner.  The protocol number to use is particular to the
        communication domain in which communication is to take place; see

I.e. there exists one set of protocol parameters per protocol family (or
in other words matching the arguments of socket(2), per "domain").

So you'd expect mention of the protocol family aka domain in protocols(5).
It's there, too -- "the known protocols used in the DARPA Internet." 
(aka PF_INET) So let's have a look at /etc/protocols ...

First it starts babbling about IPV6 (which isn't PF_INET aka DARPA Internet),
then it continues to describe some protocols that are clearly IPv6.

These aren't for PF_INET, but for PF_INET6 ? From their comments and names,
I'd guess the latter. From them being in /etc/protocols, it *must* be PF_INET
as protocols(5) refers to the protocols as "DARPA Internet" (aka PF_INET)

        man 2 socket , read
        man 5 protocols , read 
        view /etc/protocols , read
        Change protocols(5) to not talk about "DARPA Internet" protocols or add
        a field in /etc/protocols to tell for which protocol family (aka domain
        in socket(2)) the protocol really is.


Home | Main Index | Thread Index | Old Index