Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:5309 comp.os.386bsd.misc:1088 Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!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: kernel names Message-ID: <michaelv.748757186@ponderous.cc.iastate.edu> Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA References: <1993Sep21.194457.10899@fcom.cc.utah.edu> <27pe7k$4vq@germany.eu.net> <27pqqj$ibk@pdq.coe.montana.edu> Date: Thu, 23 Sep 1993 04:06:26 GMT Lines: 31 In <27pqqj$ibk@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: >In article <27pe7k$4vq@germany.eu.net>, >Bernard Steiner <bs@Germany.EU.net> wrote: >>Comment: I do not see any sophisticated reason (apart from some stupid "we're >>being different) for the kernel (and that goes for all derivates of 386bsd, >>*including* 386bsd) to have any other name than /vmunix. > ^^^^ >Yeah right, I want to get sued for using that 4-letter word. >For now, I think 386bsd is the safest thing, but personally I'd like >something as generic as /kernel, since it's blatantly obvious, and >no-one can sue you for using that name. :-) If you're so concerned about being able to access your kernel as /vmunix, you can try this neato trick that modern unices enable us to do! ln -s /netbsd /vmunix or ln -s /386bsd /vmunix Knock yourself out... -- ------------------------------------------------------------------------------ Michael L. VanLoon Project Vincent Systems Staff michaelv@iastate.edu Iowa State University Computation Center ------------------------------------------------------------------------------