Path: utzoo!attcan!uunet!decwrl!sgi!shinobu!odin!elysium!archer
From: archer@elysium.esd.sgi.com (Archer Sully)
Newsgroups: comp.sys.sgi
Subject: Re: IRIS console - how do servers work ?
Message-ID: <10756@odin.corp.sgi.com>
Date: 23 Jul 90 16:49:42 GMT
References: <5076@minyos.xx.rmit.oz> <1990Jul23.083435.838@urz.unibas.ch>
Sender: news@odin.corp.sgi.com
Distribution: comp.sys.sgi
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 24

In <1990Jul23.083435.838@urz.unibas.ch> doelz@urz.unibas.ch writes:

| In article <5076@minyos.xx.rmit.oz>, rxcob@minyos.xx.rmit.oz (Owen Baker) writes:
| > Does anyone know if you can make a terminal the console on an IRIS 4D2D?
| > I mean when the system is up not just when booting.
| > 
| 
| I'm interested in this as well (as of october '88), and didn't find a
| practicable solution yet. 
| Pointers welcome- how do the servers work? There might be a hint to fool 
| the graphics console if one knew how the server configureations 
| address the problem. 
| 

Its really quite simple.  There is an environment variable in the PROM
called "console".  It can have any of several values, usually "G" (for
graphics).  However, if it is set to "d" (debug), the console is switched
to serial port 0.  The console variable can be set from either the PROM
monitor or with the 'nvram' command.

--
Archer Sully          |  Ask not what you can do for you country,
archer@esd.sgi.com    |  But what your country's been doing to you.
                      |                    -- The Avengers