Date: Sun, 5 Aug 2001 12:25:54 -0700 From: Jim Mock <mij@soupnazi.org> To: John Murphy <jfm@blueyonder.co.uk> Cc: doc@freebsd.org Subject: Re: Minor changes for Handbook Chapter 9 Message-ID: <20010805122554.B92283@cartman.geekhouse.net> In-Reply-To: <ashqmtks9legvh8d91o8qj0bo84gmqjbnh@4ax.com> References: <ashqmtks9legvh8d91o8qj0bo84gmqjbnh@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 05 Aug 2001 at 14:39:27 +0100, John Murphy wrote: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html > > 9.4 The Configuration File > Last sentence in the paragraph below the list of i386 cpu types: > If you are unsure which type your CPU use, > of your CPU type, > > Near the end: > pseudo-device tun # Packet tunnel. > > This is used by the userland PPP software. The number after tun specifies > |A| > ... > > pseudo-device pty # Pseudo-ttys (telnet etc) > > This is a ``pseudo-terminal'' or simulated login port. It is used by > incoming telnet and rlogin sessions, xterm, and some other applications > such as emacs. The number indicates the number of ptys to create. > |A| ^ after pty > ... > > pseudo-device bpf # Berkeley packet filter > > This is the Berkeley Packet Filter. This pseudo-device allows network > interfaces to be placed in promiscuous mode, capturing every packet on > a broadcast network (e.g., an Ethernet). These packets can be captured > to disk and or examined with the tcpdump(1) program. > > Perhaps add a note here: > Note: The bpf pseudo-device is also used by the dhclient(8) program > to obtain the IP address of the default-router etc. Leave it > uncommented if you connect to a network using DHCP. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-trouble.html > 9.6 If Something Goes Wrong > > First Note: > The proper command to ``unlock'' the kernel file that make installs > (in order to move another kernel back permanently) is: > > # chflags noschg /kernel > > An addition perhaps: > If you find you can't do this, you are probably running at a securelevel(8) > greater than zero. Edit the kern_securelevel entry in /etc/rc.conf to > kern_securelevel="-1" and reboot. Remember to change it back when you're > happy with your new kernel. Thanks again. I just committed this stuff. - jim -- - jim mock <mij@soupnazi.org> tech writer | iXsystems, Inc. - - http://soupnazi.org/ work: jim@ixsystems.net | jim@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010805122554.B92283>