Return to BSD News archive
Xref: sserve comp.os.386bsd.development:550 comp.os.386bsd.misc:229 comp.os.386bsd.questions:1959 Newsgroups: comp.os.386bsd.development,comp.os.386bsd.misc,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!wupost!csus.edu!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: Leadership Message-ID: <hastyC5z10p.Buo@netcom.com> Keywords: netbsd, 386bsd and beyond Organization: Netcom Online Communications Services (408-241-9760 login: guest) References: <C5yH0F.Hn6@ns1.nodak.edu> Date: Sat, 24 Apr 1993 04:41:13 GMT Lines: 20 What is interesting is that the Unix culture keeps getting fragmented and diluted after so many years. Oh, well... When I started hacking on 386bsd a year ago, I read DDJ's articles on 386BSD for quidelines on what to do. For instance, we had a problem with processes heavily compute bound either freezing the system or rendering timesharing useless. By reading, Bill & Lynne's articles I was able to create a simple patch to correct the problem. Another example, was kern_execve.c, we had a lot of problems with it in the beginning and several of us found an article with an updated kern_execve.c ( I happily downloaded it to my system). There was an article on loadable drivers for 386bsd... Hope this helps, Amancio -- This message brought to you by the letters X and S and the number 3 Amancio Hasty | Home: (415) 495-3046 | ftp-site depository of all my work: e-mail hasty@netcom.com | sunvis.rtpnc.epa.gov:/pub/386bsd/incoming