Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:5287 comp.os.386bsd.misc:1084
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate
From: nate@bsd.coe.montana.edu (Nate Williams)
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc
Subject: Re: kernel names
Date: 22 Sep 1993 15:26:11 GMT
Organization: Montana State University, Bozeman MT
Lines: 21
Message-ID: <27pqqj$ibk@pdq.coe.montana.edu>
References: <1993Sep21.194457.10899@fcom.cc.utah.edu> <27pe7k$4vq@germany.eu.net>
NNTP-Posting-Host: bsd.coe.montana.edu
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. :-)
Nate
--
nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone,
nate@cs.montana.edu | so let's not compete with each other, let's
work #: (406) 994-4836 | compete with folks who try to tie us down to
home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me