Subject: Re: problem in userland with nsparser.l
To: Paul Newhouse <newhouse@rockhead.com>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
List: current-users
Date: 03/31/2000 02:06:40
>> ...every problem I've had with nslexer has turned out to be a
>> missing or broken /dev/stdout.  Maybe check to make sure /dev/stdout
>> is in place and working?

> Well it's there:
>  % ls -l /dev/stdout
>  crw-rw-rw-  1 root  wheel  22, 1 Mar 26 23:55 /dev/stdout
> what test would make sure it is "working" well enough?

I'm not sure whether <22,1> is right; it depends on which port you're
using (and unless it's the sparc port I doubt I have the numbers at
ready hand anyway).

But to check it, you might find a nice small text file -
/etc/resolv.conf, if you use one, would do nicely - and copy it to
/dev/stdout, see if you get output.  (Details changed in this example.)

[Sparkle] 121> cp /etc/resolv.conf /dev/stdout
search Rodents.Montreal.QC.CA dept.school.edu otherschool.edu
nameserver 10.20.30.40
nameserver 1.2.3.4
nameserver 11.22.33.44
sortlist 10.20.0.0/16 11.21.0.0/16
[Sparkle] 122> 

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B