Xref: utzoo unix-pc.general:5045 comp.sys.att:9047
Path: utzoo!attcan!uunet!lll-winken!brutus.cs.uiuc.edu!zaphod.mps.ohio-state.edu!mips!daver!kcdev!pars!cpsolv!rhg
From: rhg@cpsolv.CPS.COM (Richard H. Gumpertz)
Newsgroups: unix-pc.general,comp.sys.att
Subject: ls writes errors to stdout
Message-ID: <502@cpsolv.CPS.COM>
Date: 20 Mar 90 02:11:43 GMT
Reply-To: rhg@cpsolv.uucp (Richard H. Gumpertz)
Organization: Computer Problem Solving, Leawood, Kansas
Lines: 10

I have just noticed that the AT&T Unix PC version 3.51 "ls" command writes
its error messages (such as "XXX not found") to stdout instead of stderr.  Is
this unique to the Unix PC or does it affect other flavors of Unix?  Is there
a fix?  Do any other commands beside ls behave in this silly manner?

-- 
  ==========================================================================
  | Richard H. Gumpertz    rhg@CPS.COM    (913) 642-1777 or (816) 891-3561 |
  | Computer Problem Solving, 8905 Mohawk Lane, Leawood, Kansas 66206-1749 |
  ==========================================================================