🚀 go-pugleaf

> Sorry, but I have to disagree here.  I don't know what you mean by
> "less stable", but it hasn't crashed on me in my full-time use of it.
> If it crashes for you, make it better for everyone by submitting a bug
> report.
> 
> It *does* coexist with gpm.  I don't usually run gpm, but I just tried
> it and it worked fine.  I can switch between text & X virtual consoles
> and the mouse works in both.  Make sure that you have configured gpm
> and Metro to use the same device (ie. don't use ttyS0 for Metro and
> cua0 for gpm).  If you use different devices, that would cause it to
> fail.
> 
> Harder to use is of course relative, but I think the graphical
> configuration is quite nice, and once it's up and running there isn't
> any difference in use.
k

When I run the MetroX server, I cannot print anything. I have done 
several identical istallations with MetroX and with SVGA as servers.

I know for a fact that it is only the existence of MetroX on my system
that prohibits me from printing.  I must admit to being partial to the
graphical interface though.  Very proffesionally implemented but
MetroX is much slower for my cirrus logic 5429 VLB 1meg card.

BUT the real turnoff is losing printing.  I haven't got the time to submit
a bug report to people who develop commercially when I use linux to get 
away from all that (with the exception of Executor; I can't imagine 
anyone writing a MacROM free Mac emulator for linux anytime this 
millenium).  

I should have seen it coming I guess.  MetorX is listed as a BETA package 
under GLINT after all.

Just my opinion folks,
Michelle*-)