Re: [9fans] kfs error

["rob pike" <rob@plan9.bell-labs.com>]

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]

The new, as yet unreleased system, includes this paragraph
in cons(3) documenting an idea by Russ Cox:

          The kprint file may be read to receive a copy of the data
          written to the console by the kernel's print statements or
          by processes writing to /dev/cons.  Only data written after
          the file is opened is available.  If the machine's console
          is a serial line, the data is sent both to the console and
          to kprint; if its console is a graphics screen, the data is
          sent either to the display or to kprint, but not both.  (It
          is advisable not to open kprint on terminals until you have
          started rio(1).)

-rob


[-- Attachment #2: Type: message/rfc822, Size: 2159 bytes --]

From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] kfs error
Date: Mon, 1 Oct 2001 12:45:17 +0200
Message-ID: <009b01c14a66$290975d0$a2b9c6d4@SOMA>

>> yeah, i added a function called halt to /rc/bin/termrc too.

> Is there a way to finish running 'rio' desktop ? 
> So that termrc could continue after 'rio' and halt the kfs ?

boots quickly enough so i just halt and ^t^tr it.

it's rare that i _don't_ want to run rio, although i
did log in as none to take out some kernel print's
with ed, 'cos it drives rio (well, the display and
me) nuts.