*BSD News Article 15224


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!noc.near.net!uunet!pipex!uknet!cf-cm!paul
From: paul@isl.cf.ac.uk (Paul)
Subject: Re: (lpa driver) savecore: Can't find device 1/0
Message-ID: <1993Apr27.132532.8438@cm.cf.ac.uk>
Sender: news@cm.cf.ac.uk (Network News System)
Organization: /usr/local/lib/rn/organisation
References: <C639Ln.7p@veda.is> <1993Apr26.130106.19745@gmd.de> <C63txA.15t@veda.is>
Date: Tue, 27 Apr 1993 13:25:31 +0000
Lines: 27

In article <C63txA.15t@veda.is> adam@veda.is (Adam David) writes:
>veit@mururoa.gmd.de (Holger Veit) writes:
>
>>Is the kernel you booted /386bsd or have you called it different
>>(and booted via Julian's bootloader)? savecore gets confused if it 
>>looks into /386bsd for the symbol table and uses the offset it gets
>>for lookup into /dev/kmem (which belongs to /386bsd.bootedkernel and
>>needs a different offset).
>
>Yes, this is exactly the problem. I guess the name of the booted kernel
>should be available for programs that need it to be able to look it up.
>
>I have also noticed (in the same circumstances) that ps can just wait
>around producing no output, and both w and uptime say the system has
>been up for over 8000 days, with a load average of NaN.
>
>How is (or should be) the name of the currently executed kernel
>made available?

What about someone implementing the uname function which is needed
anyway and enhancing it a little to return the name of the booted kernel
as well.

-- 
  Paul Richards, University of Wales, College Cardiff

  Internet: paul@isl.cf.ac.uk