Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!decwrl!pyramid!ut-sally!seismo!rochester!ur-helheim!badri
From: badri@ur-helheim.UUCP (Badri Lokanathan)
Newsgroups: net.unix-wizards
Subject: Why do ps, uptime (& probably others) check vmunix version?
Message-ID: <457@ur-helheim.UUCP>
Date: Mon, 10-Feb-86 12:43:09 EST
Article-I.D.: ur-helhe.457
Posted: Mon Feb 10 12:43:09 1986
Date-Received: Thu, 13-Feb-86 19:22:12 EST
Reply-To: badri@ur-helheim.UUCP (Badri Lokanathan)
Organization: U. of Rochester, EE Dept.
Lines: 23

We run BSD4.2 on a 750.
I installed a new vmunix and did not link it to /vmunix, but left it
as /vmunix.blah. Then I booted with B/1 and entered the appropriate
stuff. Well, it booted off fine; everything was OK till I checked
uptime and ps and got garbage. I tracked down the problem in the
source of ps to the following:

getkvars(argc, argv)
	char **argv;
{
	register struct nlist *nlp;

	nlistf = argc > 1 ? argv[1] : "/vmunix";
	.
	.
	.
Since /vmunix was linked to the old version of vmunix, naturally it barfed.
So, here is my question. Why should ps (and any other program) examine the
name of vmunix? This is particularly aggravating if a new kernel is being
tested - I do not want to make too many changes, just in case.
My apologies if I sound terribly naive!

Badri Lokanathan