| 1 |
On 6/28/06, Iain Buchanan <iaindb@××××××××××××.au> wrote: |
| 2 |
> The suggestions were screen, and showconsole. showconsole only shows |
| 3 |
> output, and doesn't let you type into it; and screen can't (?) attach to |
| 4 |
> such a virtual console. |
| 5 |
|
| 6 |
Screen can definitely attach to a virtual console. I just tried the |
| 7 |
following in /etc/inittab: |
| 8 |
|
| 9 |
c5:2345:respawn:/usr/bin/screen -R tty5.localhost /bin/login |
| 10 |
>/dev/tty5 </dev/tty5 2>&1 |
| 11 |
c6:2345:respawn:/usr/bin/screen -R tty6.localhost /bin/login |
| 12 |
>/dev/tty6 </dev/tty6 2>&1 |
| 13 |
|
| 14 |
You can then attach to either of those with |
| 15 |
|
| 16 |
screen -D -r tty5.localhost |
| 17 |
screen -D -r tty6.localhost |
| 18 |
|
| 19 |
The only thing you really can't do is login as root, because screen |
| 20 |
uses psuedo tty's which are declared unsecure by default. Unless you |
| 21 |
want to add all pty devices to /etc/securetty... |
| 22 |
|
| 23 |
But there is no security with this setup anyway, because on a console |
| 24 |
all one has to do is "Ctrl-a c" to get a root shell. |
| 25 |
|
| 26 |
Still, this should give you an idea of what you will have to do if you |
| 27 |
are going to write your own program to manage this... |
| 28 |
|
| 29 |
-Richard |
| 30 |
-- |
| 31 |
gentoo-user@g.o mailing list |
Archives