Re: looking for testers of new console

[David Walter]

David Walter <dwalter@syr.edu> writes:

> Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:
>
>> Note that you should redirect /dev/console then.  Try Roland's new fsysopts
>> for term to do that.
>>  
>>> I tried   adding export TERM=mach-color  but it  failed still and then
>>> started the default console.
>>
>> Do you talk about the ncursesw client?  I am not sure that would work.
>
> Actually it  works with the old  console-ncurses and with  the current
> console client code.
>
> If you quit it you get dumped into a single user shell.
I'm thinking that I wasn't very clear, (one too many late nights :)

The following code works to start a console client at boot time.

But, I had the following error when  trying to scroll back after using
this for a while.

console: ../../hurd/console-client/ncursesw.c:462: ncursesw_scroll:
Assertion 'delta >= 0' failed.
Aborted.


After I get no response from the keyboard.

Logging in from another machine and killing  the hanging crash process
and I get:

sh-2-05a# kbd queue full
kbd queue full

Even pressing the control key gives this message.

killing process 6 & 7 allowed me to fall back into a shell. 

Strangely local restart of  the  shell failed,   the logins had   some
strangeness where every keystroke was  treated like a char followed by
an enter key.

reboot and try again.

** Okay: now this appears to be separate problems. **

running  with the  patch to    runsystem gives  the  console  with  no
problems.

Quitting (c+a+bksp) dumps into an sh-2-05a# prompt (single user).

restarting by  exiting the shell  does  bad things like  attempting to
restart the system :) The console then comes up in the funny cooked(?)
mode.

But if I just reattach to the console by exporting TERM=mach-color (if
needed) followed by:

        console -D /lib/hurd/console -d vga -d pc_kbd -d generic_speaker 
/dev/vcs

and continuing works just fine. ( I am currently typing in a restarted
console like this)

Cool, so it works either way with console ncursesw or vga in
/libexec/runsystem, and multiple restarts works okay. 

Of course there  is the issue  of some 'lone gun'  walking up  to your
machine  with the console  running  and c+a+bksp  gaining root  at the
single   user prompt,  but  I   imagine an   option for  --no-kill  or
--reboot-on-kill when we get around to security issues?

--- /libexec/runsystem.gnu      Sun Aug  4 20:57:11 2002
+++ /libexec/runsystem  Thu Sep 19 23:02:57 2002
@@ -130,9 +130,10 @@
   # This program reads /etc/ttys and starts the programs it says to.
   ${RUNTTYS} &
   runttys_pid=$!
-
+  export TERM=mach-color
+  console -D /lib/hurd/console -d vga -d pc_kbd -d generic_speaker /dev/vcs
   # Wait for runttys to die, meanwhile handling trapped signals.
-  wait
+#  wait
 
   # Go back to the top of the infinite loop, as if booting single-user.
   rc=false

-- 
/^\
\ /     ASCII RIBBON CAMPAIGN
 X        AGAINST HTML MAIL
/ \