Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!psuvax1!psuvm!cunyvm!slvqc
From: SLVQC@CUNYVM.BITNET (Salvatore Saieva)
Newsgroups: comp.sys.next
Subject: Re: Unix `w' command not working
Message-ID: <91058.162048SLVQC@CUNYVM.BITNET>
Date: 27 Feb 91 21:20:48 GMT
References: <91057.115121SLVQC@CUNYVM.BITNET> <1367@toaster.SFSU.EDU>
Organization: City University of New York/ University Computer Center
Lines: 30

In article <1367@toaster.SFSU.EDU>, eps@toaster.SFSU.EDU (Eric P. Scott) says:
>
>In article <91057.115121SLVQC@CUNYVM.BITNET> SLVQC@CUNYVM.BITNET
>        (Salvatore Saieva) writes:
>>I recently installed NeXTStep v2.0 and the Unix `w' command no
>>longer works. (It used to work under v1.0.) Whenever I try to run
>>w I get the message ``No namelist''. Does anyone know what this
>>message means? Any ideas why it doesn't work?
>
>w attempts to get a namelist from /mach--this is normally a
>symbolic link to the $BOOTFILE metalink.  If you've booted
>from od or sd you shouldn't have any problems (unless you
>mucked with the system files).  If you've booted from en or
>tp the metalink may be invalid--but since you had it working
>under 1.0, I'm inclined to rule this out.
>

[Which starts me thinking...] The last time I booted the system it
was from OD to build the hard drive (I just installed a Maxtor 8760S
no too long ago). Apparently, w was confused as to where to look for
/mach. After a quick reboot everything is working fine, including w.
Thanks!

Sal.
-------
 Salvatore Saieva                            Internet: slvqc@cunyvm.cuny.edu
 Queens College, Academic Computer Center      BITNET: slvqc@cunyvm.bitnet
 65-30 Kissena Blvd, Flushing, N.Y. 11367     DeskNet: (718) 520-7662

      awk, sed, grep, lex, yacc, make, >, <, |,... ``I got the Power!''