[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: console-client close to initial check in

From: Marcus Brinkmann
Subject: Re: console-client close to initial check in
Date: Fri, 13 Sep 2002 20:53:50 +0200
User-agent: Mutt/1.4i

On Fri, Sep 13, 2002 at 08:41:17PM +0200, Niels Möller wrote:
> Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:
> > I don't see a need for them to be able to attach to them.  Maybe you should
> > illustrate what is the advantage in being able to do so.  I have thought up
> > various scenarios (public terminals etc), but can not bring myself to the
> > conclusion that it is a distinct feature that is worth to have.
> I don't have a strong argument. Say I'm logged in on a virtual
> terminal directly on the console. Then I go elsewhere, and log in to
> my home machine over the network. Then it's nice to be able to attach
> to my virtual terminals on the console. And it would be cool to be
> able to do that without having to start screen or a separate console
> server in advance.

In this specific case, where you leave a login session unattended, you
probably have the machine in your home or office, and already have the root
password.  You would not leave a login shell unattended on a public

So, you can login remotely, and start the console client as root.

> But on the other hand, perhaps that functionality is better put
> elsewhere. For instance, it would also be nice to be able to attach to
> terminals running under X, or perhaps even to an arbitrary pty.

This is not feasible, because a pty or tty in the Hurd doesn't have much
state, certainly not the state of what is visible on the screen or was
output in the past - that is exactly what the console server is responsible


`Rhubarb is no Egyptian god.' GNU      http://www.gnu.org    marcus@gnu.org
Marcus Brinkmann              The Hurd http://www.gnu.org/software/hurd/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]