Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!yale.edu!yale!gumby!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!acs.ucalgary.ca!cpsc.ucalgary.ca!xenlink!newt.cuc.ab.ca!deraadt From: deraadt@newt.cuc.ab.ca (Theo de Raadt) Subject: 4.4/4.3Reno style SIOCGIFCONF Message-ID: <DERAADT.92Nov18045305@newt.newt.cuc.ab.ca> Sender: news@newt.cuc.ab.ca Nntp-Posting-Host: newt Organization: little lizard city Date: Wed, 18 Nov 1992 11:53:05 GMT Lines: 12 I don't understand fully what is going on with SIOCGIFCONF, at least as it is implimented under 386BSD. I suspect this is the way it is implimented in 4.4. The calls support sockaddr's with sa_len fields. I finally figured out how it works. It differs quite a bit from the old system. I can understand that this is to support multiple address families and interface addresses on one interface. But, what is the AF_LINK entry for? <tdr. -- This space not left unintentionally unblank. deraadt@newt.cuc.ab.ca