Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!caen!ox.com!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: What is exactely /dev/console?
Keywords: /dev/console
Message-ID: <4f9d8a8d.1bc5b@pisa.ifs.umich.edu>
Date: 4 Feb 91 16:32:06 GMT
References: <1991Feb1.193832.8060@alchemy.chem.utoronto.ca> <1079@eba.eb.ele.tue.nl> <4f9a812d.1bc5b@pisa.ifs.umich.edu> <1080@eba.eb.ele.tue.nl>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 9

In article <1080@eba.eb.ele.tue.nl>, wjw@ebs.eb.ele.tue.nl (Willem Jan Withagen) writes:

  Writting to /dev/console will get you a file in /usr/adm 
  (\`node_data/system_logs) at which you'll be able to take a look. 
  I never realised that until now. 

You could also RTFM.  'apropos console' points you at both console(4) and
mkcon(8), which discuss system_logs/console.  I haven't tried mkcon but it's
an intriguing concept.