Re: looking for testers of new console
Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:
> On Thu, Sep 19, 2002 at 04:08:04AM +0200, Marcus Brinkmann wrote:
>> Then you should add the terminals to ttys, so you get a login session
>> on them at boot time. Edit the file /etc/ttys, and add the following
>> lines (or similar if you made more/less ttys):
>> tty6 "/libexec/getty 38400" hurd on secure trusted console
> Note: You should not remove the existing entry. At least not if you want to
> be able to login locally :)
I have added a run-daemon program that takes its arguments as a
program to run and wait on, if the program dies it restarts it and
Here is a problem that I don't know how to address:
I can do the redirect to one of the consoles, but what is the right
way to disable the exec of the getty on that terminal _and_ to get the
console program to read the console device?
I have tried setting it to be the console device, using the term
translator to point to it as a device, with path /dev/vcs/9. I have
added an entry to /etc/ttys.
settrans -fgc /dev/vt9 /hurd/term /dev/vt9 device /dev/vcs/9/console
#this isn't recognized by the console client.
I have also tried using:
settrans -fgc /dev/vt9 /hurd/term /dev/vt9 hurdio /dev/vcs/9/console
#this gives a getty and is recognized by the client.
Both of the have been done with matching entries in /etc/ttys.
> Later, when the console client is started in the boot scripts, the console
> entry should be removed (in fact, if you feel adventurous, you could try
> that out for us and report back).
I have commented out
#console "/libexec/getty 9600" mach-color on secure trusted console
I can get the output to redirect to this device, but it also has a
getty running on it.
Can I get the getty to stop and get the console device to be
recognized by the console client?
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL