🚀 go-pugleaf

 I have a bizarre (at least it seems so to me!) shutdown problem since
upgrading to 1.2.13 that manifests itself when using X.
Essentially, after using "shutdown now" to exit X (and close the machine),
the next time I reboot I cannot restart X. What seems to happen, as
the result of the shutdown, is that /dev/console gets "re-created"
(4, 192) whereas, in order to be able to restart X, I have to delete
this device file and symbolic link to  /dev/tty0.
I notice on other boxes I have (with much earlier revisions of the kernel
and with different video cards! - I'm not, at this stage willing to
re-install my old kernel on the box on which I am having the current trouble,
just to see what /dev/console was! that /dev/console is 4, 0. 


The upgrade to 1.2.13 is the first time I notice the symbolic link /dev/systty
(to /dev/console). 

In short, is this a manifestation of a known or obvious problem?
(Apart from failing to read the manual/installation instructions).
Any other hints to shed light on this would be welcome!
(at the moment - I get around the problem by avoiding "shutdown" and using 
"reboot" - is this safe?

Another rather mysterious problem is that my new kernel and new seyon
don't quite work together like the old kernel and seyon. I have a script
that I usually execute when connected (to simply log the date and telephone
number). On the "upgraded system" the script (and any other I have
tried to replace it with) seems to execute but then disrupt the session.
Seyon complains that it received signal 11 from the script process. 
If I execute

the same shell commands using the button for shell commands, rahter than my
connect script, everything is fine.
Any hints on this would also be welcome.

regards
d.s.


-- 
David Suter - Dept. of Electrical and
Computer Systems Engineering, Monash University,
Clayton, Vic. 3168, Australia
ph 905 5682 Fax 905 3454