Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:5357 comp.os.386bsd.misc:1104
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!swrinde!cs.utexas.edu!usc!howland.reston.ans.net!vixen.cso.uiuc.edu!moe.ksu.ksu.edu!hobbes.physics.uiowa.edu!news.uiowa.edu!news.weeg.uiowa.edu!jboggs
From: jboggs@umaxc.weeg.uiowa.edu (John D. Boggs)
Subject: Re: kernel names
Message-ID: <1993Sep24.132759.29302@news.weeg.uiowa.edu>
Sender: jboggs@news.weeg.uiowa.edu (John D. Boggs)
Organization: University of Iowa, Iowa City, IA, USA
References: <27ufsh$75q@Germany.EU.net>
Date: Fri, 24 Sep 1993 13:27:59 GMT
Lines: 26
From article <27ufsh$75q@Germany.EU.net>, by bs@Germany.EU.net (Bernard Steiner):
>
> 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
And is what I've done on Net-BSD-0.9 to get xload to work.
[ln -s /netbsd /386bsd]
--
John D. Boggs jdb@erato.iowa-city.ia.us
or ...!access1!erato!jdb