Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:5359 comp.os.386bsd.misc:1106 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!europa.eng.gtefsd.com!uunet!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:50:09 +0200 Organization: EUnet Deutschland GmbH, Dortmund, Germany Lines: 18 Distribution: world Message-ID: <27ufsh$75q@Germany.EU.net> References: <1993Sep21.194457.10899@fcom.cc.utah.edu> <27pe7k$4vq@germany.eu.net> <27pqqj$ibk@pdq.coe.montana.edu> <michaelv.748757186@ponderous.cc.iastate.edu> NNTP-Posting-Host: qwerty.germany.eu.net In article <michaelv.748757186@ponderous.cc.iastate.edu>, michaelv@iastate.edu (Michael L. VanLoon) writes: |> 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... Now that you mention it, this was exactly what I did with 386bsd 0.0 where most of the stuff still insisted on opening /vmunix. Bernard