Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!usc!sol.ctr.columbia.edu!caen!msuinfo!agate!doc.ic.ac.uk!uknet!pipex!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.bugs Subject: Re: (lpa driver) savecore: Can't find device 1/0 Message-ID: <C63txA.15t@veda.is> Date: 26 Apr 93 18:55:43 GMT References: <C639Ln.7p@veda.is> <1993Apr26.130106.19745@gmd.de> Organization: Veda Systems, Iceland Lines: 20 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? -- Adam D. (adam@veda.is)