| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Linux has SHUT_RD and SHUT_WR reversed in the ``how'' argument. Presumably | 1998-04-25 | 1 | -1/+9 | ||
| | | | | | | they will fix this sometime, after which this change should be backed out. Pointed out by tchrist@perl.com | |||||
| * | recover from lint changes elsewhere, not completely tested | 1998-02-10 | 1 | -4/+4 | ||
| | | ||||||
| * | emulate linux connect() braindamage even better -- only do so on async | 1998-02-07 | 1 | -1/+9 | ||
| | | | | | sockets; pb@fasterix.freenix.org | |||||
| * | support IP_HDRINCL | 1997-12-14 | 1 | -1/+3 | ||
| | | ||||||
| * | add GIFMETRIC and GIFMTU | 1997-12-10 | 1 | -1/+7 | ||
| | | ||||||
| * | emulate linux SIOCGIFHWADDR; stolen from freebsd; not tested yet | 1997-12-10 | 1 | -1/+30 | ||
| | | ||||||
| * | oh, connect() semantics are EVEN WORSE | 1997-11-27 | 1 | -4/+2 | ||
| | | ||||||
| * | If using async connect(), after select for writeable, if getpeername() | 1997-11-26 | 1 | -2/+32 | ||
| | | | | | | | | | | indicates connection failure, you can use getsockopt(SOL_SOCKET, SO_ERROR, ...) to find the error. But the linux people I guess didn't know about this, and changed connect() so that a 2nd connect() call on a failed socket returns the error directly. Fake this demented non-standard behaviour which Linux users are now starting to code to. Talk about dilution of the API... | |||||
| * | indent | 1997-11-26 | 1 | -29/+29 | ||
| | | ||||||
| * | Good fixes and changes from latest Net. | 1996-04-17 | 1 | -1/+32 | ||
| | | ||||||
| * | From NetBSD: | 1996-03-08 | 1 | -1/+51 | ||
| | | | | | linux compatibility changes. | |||||
| * | initial import of NetBSD tree | 1995-10-18 | 1 | -0/+704 | ||
