Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!sol.ctr.columbia.edu!howland.reston.ans.net!pipex!uunet!satisfied.elf.com!usenet From: *Hobbit* <hobbit@asylum.sf.ca.us> Newsgroups: comp.os.386bsd.bugs Subject: Another weird 950112-SNAP problem Date: 23 Jan 1995 17:18:01 EST Organization: large Lines: 20 Sender: root Approved: God Expires: 1 Apr 95 12:34 Message-ID: <3g1au3$b0f@satisfied.elf.com> NNTP-Posting-Host: asylum.sf.ca.us A kernel built from this distribution seems unable to add a route, default or otherwise, returning with "protocol not supported". A quickish look through the relevant files sees kern/socket.c calling stuff in net/route.c, which under a comment saying "multicast goop, grrr" calls stuff in netinet/mroute.c. This in turn, if MROUTING isn't defined, returns EPROTNOTSUPP. It is likely that I'm doing something wrong here, but I figured I'd ask for a sanity check. Anyone else run into this? One "wrong" thing I might be doing is trying to guess at what to extract from the source-dist to make a "kerndist". I am assuming that pulling out usr/src/sys is "good enough". What about usr/src/include? Any other stuff I might be missing my guess at? Is there a script that pulls out the right things floating around? I don't really want to suck the *entire* src dist across a low-bandwidth link just to build a kernel. Also, various files in FreeBSD-current seem incomplete. net/route.c, for example, is truncated. _H*