From: Doug DeJulio (ddj+@cs.cmu.edu)
Date: 09/17/92


From: ddj+@cs.cmu.edu (Doug DeJulio)
Subject: Re: Can you access a virtual console directly?
Date: Thu, 17 Sep 1992 20:00:31 GMT

In article <716730355.F00055@remote.halcyon.com> Rob.Levin@f217.n3802.z1.fidonet.org (Rob Levin) writes:
>Or, perhaps someone might explain to *you* that there is only ONE
>physical console on a system, and it ought to be able to achieve
>priority, subject to limitations imposed by time-critical device
>drivers, etc.
>
>After all, the system display console is *always* running in the
>foreground. If you want to reduce the conversation to cute catch
>phrases, how about, "Inefficient allocation of resources, just say NO."

I don't agree. On a typical Unix system there's no guarantee that a
login process will be running on the console, and even if there is
it's not always the case that the most important users will be
accessing the machine that way. Once I set up my Linux box (still
collecting hardware) I'll probably set up a login on a serial port,
and connect that to my NeXT machine so I can access Linux while logged
into the NeXT. Once I get a network driver for my ethernet card and
get TCP/IP working, people will be telnetting in from all over the
world, and the console user shouldn't get any higher priority than
anyone else.

Any user with sufficent privelages should be able to change the
priority anyway, using renice.

-- 
Doug DeJulio
ddj+@cmu.edu