[Top][All Lists]

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

Re: /dev/console switching: the continuing saga

From: Marcus Brinkmann
Subject: Re: /dev/console switching: the continuing saga
Date: Wed, 20 Nov 2002 16:30:24 +0100
User-agent: Mutt/1.4i

(btw, marcus@debian.org is not one of my addresses)

On Wed, Nov 20, 2002 at 09:23:37AM -0500, David Walter wrote:
> I've been noticing that if the initial term process running on console
> isn't killed console output doesn't change to the new device.
> If process 7 is killed (/hurd/term /dev/console ...) then there is a
> lost resource.

The purpose of the fsysopts call is exactly to change the options of the
running term process, and thus redirect all live users of the term node.

It's completely illogical that killing the running term process helps in
bringing a change to effect that is initiated with fsysopts.  Are you really
using fsysopts to redirect the term process, or are you by any chance
running settrans?  Please list the exact sequence of commands you are
running, it's not clear from your message what you were doing.

The problem that some programs open the device directly is unrelated to


`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]