Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!howland.reston.ans.net!vixen.cso.uiuc.edu!newsrelay.iastate.edu!news.iastate.edu!ponderous.cc.iastate.edu!michaelv From: michaelv@iastate.edu (Michael L. VanLoon) Subject: Re: [NetBSD-0.9] config Message-ID: <michaelv.747520602@ponderous.cc.iastate.edu> Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA References: <CD1JrE.Mv9@pilhuhn.sub.org> <1993Sep8.170459.6980@gmd.de> <GLASS.93Sep8121515@sun-lamp.postgres.Berkeley.EDU> Date: Wed, 8 Sep 1993 20:36:42 GMT Lines: 20 In <GLASS.93Sep8121515@sun-lamp.postgres.Berkeley.EDU> glass@postgres.Berkeley.EDU (Adam Glass) writes: [stuff about a new config causing problems deleted] >complains loudly about working config files, as the syntax has changed >somewhat in the new config. Which brings up the topic: what is all that crap in the config file anyway? Just from context, and configuring Ultrix kernels, I can usually glean what most of the things are. However, a lot of little piddley things in the config file are highly OS-dependent. It would be nice if there were a doc somewhere in the conf dir with a short description of all the different device/option/etc. names available for use were, and what they actually pertained to. Am I missing something, or does this not currently exist? -- ------------------------------------------------------------------------------ Michael L. VanLoon Project Vincent Systems Staff michaelv@iastate.edu Iowa State University Computation Center ------------------------------------------------------------------------------