From owner-freebsd-current  Mon May  4 11:05:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA20228
          for freebsd-current-outgoing; Mon, 4 May 1998 11:05:25 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from jeeves.egr.msu.edu (jeeves.egr.msu.edu [35.9.37.127])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA20209
          for <freebsd-current@FreeBSD.ORG>; Mon, 4 May 1998 11:05:19 -0700 (PDT)
          (envelope-from mcdougall@ameritech.net)
Received: from ameritech.net by jeeves.egr.msu.edu (SMI-8.6/SMI-SVR4)
	id OAA23909; Mon, 4 May 1998 14:04:57 -0400
Message-ID: <354E0348.2C9D840B@ameritech.net>
Date: Mon, 04 May 1998 14:04:56 -0400
From: Adam Ryan Mcdougall <mcdougall@ameritech.net>
X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: Tom Bartol <bartol@salk.edu>
CC: Bob Willcox <bob@luke.pmr.com>, current list <freebsd-current@FreeBSD.ORG>
Subject: Re: w: /dev//bob: No such file or directory  ???
References: <Pine.BSF.3.96.980504084825.26792A-100000@cole.salk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tom Bartol wrote:
> 
> Im running -current as of April 24 and I see this problem as well.
> Perhaps John's recent VM fixes will correct the problem (but it looks like
> your kernel is recent enough to include these fixes already).  I may
> back-up my -current to April 20 as has been suggested by some to see if
> that fixes the problem.
> 
> Tom
> 
> On Mon, 4 May 1998, Bob Willcox wrote:
> 
> > I get this error message:
> >
> >     w: /dev//bob: No such file or directory
> >
> > from the w command whenever I run it on my -current system.  Anybody
> > have some pointers on what to fix/look at?

I have seen something similar before. I do not think its the Vm changes,
but more likely an out of date xterm, shell(s) from ports, or sshd.  If
you are using any of these, they may need recompiling at times.  If this
doesnt fix it, try recompiling libkvm and w, etc.

-- 
"To err is human, to forgive, beyond the scope of the Operating System"

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message