On Wed, Oct 30, 2002 at 06:37:56PM +0100, Manuel Bouyer wrote:
> On Wed, Oct 30, 2002 at 10:53:06AM +0100, Ignatios Souvatzis wrote:
> > Hi,
> > 
> > On Tue, Oct 29, 2002 at 05:32:48PM +0100, Manuel Bouyer wrote:
> > > xconsole shouldn't cause this behavior.  There is a bug somewhere, which needs
> > > to be fixed.
> > 
> > err, but xconsole is _designed_ to redirect the output to /dev/console!
> > 
> > (actually, the underlying system call is.)
> 
> Yes, but it shouldn't prevent getty on the console from working.

It seems that xconsole is blocking anything else from reading /dev/console.
If I close xconsole and do "cat /dev/console" on ttyE1, anything I type
on /dev/console (aka ttyE0) appears, and I need to hit control-c to close
cat.  If I launch xconsole and try cat /dev/console cat just exits.

With ktrace it is apparent that read() is behaving differently.
No xconsole:
  8733 cat      CALL  read(0x3,0x805c000,0x10000)
  8733 cat      RET   read RESTART
  8733 cat      PSIG  SIGINT SIG_DFL

With xconsole:
  8738 cat      CALL  read(0x3,0x805c000,0x10000)
  8738 cat      RET   read 0
  8738 cat      CALL  close(0x3)
  8738 cat      RET   close 0
  8738 cat      CALL  close(0x1)
  8738 cat      RET   close 0
  8738 cat      CALL  exit(0)

-Andrew