Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!news.dell.com!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.bugs Subject: Re: NetBSD 0.9 kernfs feature & whatis.db generator Date: 16 Sep 1993 12:53:34 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 42 Message-ID: <27a97c$nve@hrd769.brooks.af.mil> References: <89at03uedatl00@amdahl.uts.amdahl.com> <8eWA03X=daw000@amdahl.uts.amdahl.com> NNTP-Posting-Host: hrd769.brooks.af.mil In article <8eWA03X=daw000@amdahl.uts.amdahl.com> agc@uts.amdahl.com (Alistair G. Crooks) writes: >1. NetBSD 0.9 has the new kernfs feature. I'm sure it's nice, but >when I do an "ls -lR /", I soon get into a loop because of kernfs. > >It goes all the way into /kern/root fine, and then seems to recurse >through the directories, so that eventually it's listing >/kern/root/kern/root/kern/root/kern/root/kern/root > >I've not had the patience to let it continue to see how far it will >go, but I assume that this will continue almost ad infinitum. Any >comments? > Before I got the new daily script from the /usr/src/etc directory, I would do one of these every night. Eventually you will run out of memory, swap space, patience, and OS. The end-effect was that it would freak out with some sort of vm_fault() and trash the piece of the file system it touched last. >2. A small shell script to make the whatis.db file (there's a >makewhatis.sed file in the /usr/share/man directory, but I can't find >anything else to do this, and as apropos doesn't work until the >whatis.db file is built...). Go to the usr/share/man directory, and, >as root, execute the shell file that appears after my signature below. > There is a bit in the FAQ about this. You can use make to generate a new whatis.db. See the points in the FAQ before attempting this though, since not all makewhatis.sed's are created equal. >Of course, I'm perfect as well, and never need to use apropos... > Sure. Me too. I just knew this because not knowing it would have been a mistake :-) -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX