Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:5358 comp.os.386bsd.misc:1105 Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!pipex!uknet!mcsun!Germany.EU.net!news From: bs@Germany.EU.net (Bernard Steiner) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: kernel names Date: 24 Sep 1993 11:46:34 +0200 Organization: EUnet Deutschland GmbH, Dortmund, Germany Lines: 21 Distribution: world Message-ID: <27uflq$75l@Germany.EU.net> References: <1993Sep21.194457.10899@fcom.cc.utah.edu> <27pe7k$4vq@germany.eu.net> <27pqqj$ibk@pdq.coe.montana.edu> NNTP-Posting-Host: qwerty.germany.eu.net In article <27pqqj$ibk@pdq.coe.montana.edu>, nate@bsd.coe.montana.edu (Nate Williams) writes: |> >*including* 386bsd) to have any other name than /vmunix. |> ^^^^ |> Yeah right, I want to get sued for using that 4-letter word. You're kidding. The do NOT have the copyright for each and every occurance of the sub-string "unix" in upper and lower case. |> 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. :-) I'll just pop off and have it registered, and then sue.... ahem. ;) My point is that it'll be different on every single machine, and that I don't like that idea. You don't go around calling /tmp something like /foo, after all. Bernard