SUMMARY: how to know what options were built into kernel
Rich Glazier <[email protected]> Mon, 22 Nov 2010 16:33:08 -0800 (PST)
| Newsgroups | gmane.os.tru64.managers |
|---|---|
| Message-ID | <[email protected]> |
Thank you everyone, for your responses. I got a lot of good information, bu= t I =0Anever did effectively find out how to tell if PACKETFILER option is = part of my =0Arunning kernel, other than to run tcpdump and it worked! :)= =A0Oddly, the =0A/dev/pfilt files were never created, but it seems to work.= Some good advice I =0Agot from this was that there is a man page on settin= g up packet filtering, man =0Apacketfilter.=0A=0A=0A=0A----- Original Messa= ge ----=0AFrom: Rich Glazier <[email protected]>=0ATo: tru64-unix-mana= [email protected]=0ASent: Thu, November 18, 2010 1:45:38 PM=0ASubject: how to k= now what options were built into kernel=0A=0AI am trying to see if the PACK= ETFILTER option was built into my running kernel.=A0 =0A=0AUnder /sys/conf = I see several kernel config files.=A0=A0The one that is my HOSTNAME, =0A=0A= does have "options PACKETFILTER", but how can I extrapulate this from =0A/u= sr/sys/HOSTNAME/vmunix (i.e./vmunix) to actually know it's in the kernel?= =0A=0AThanks for the help,=0A=0ARich=0A=0A=0A