Edd Barrett wrote:
Hi,
I am experiencing some odd behavior with the cu serial line command.
From a (non-X11) terminal I am able to connect to the serially
connected sparc using 'sudo cu -l cua00' or 'sudo cu -l tty00'. This
is what I would expect.
When using X windows 'sudo cu -l cua00' presents the following:
---8<---
/dev/cua00: Device busy
link down
---8<---
When using X windows 'sudo cu -l tty00' reports that it is connected,
but does not work. No login prompt is displayed upon hitting return as
one would expect.
I have looked at the output of stty on both setups, they differ:
---8<---
--- /tmp/A Tue Feb 12 09:47:20 2008
+++ /tmp/B Tue Feb 12 09:47:11 2008
@@ -1,3 +1,3 @@
-speed 9600 baud;
-lflags: echoe echoke echoctl pendin
+speed 38400 baud;
+lflags: echoe echok echoke echoctl pendin
cflags: cs8 -parenb
---8<---
This lead me to think that perhaps X was picking up that 38400.
Unfortunately not the case:
---8<---
sudo cu -s 9600 -l cua00
/dev/cua00: Device busy
link down
---8<---
Does anyone have any ideas? I am sure I used to use cu in X.
further to my last message - root should be able to connect - regardless
of permissions - does visudo have the following line:
# Defaults specification
Defaults env_keep +="DESTDIR FETCH_CMD FLAVOR FTPMODE MAKE
MULTI_PACKAGES OKAY_FILES PKG_DBDIR PKG_DESTDIR PKG_CACHE PKG_PATH
PKG_TMPDIR PORTSDIR RELEASEDIR SUBPACKAGE"
The change to sudo that happened between 4.1 and 4.2 meant that sudo
does not pass environment variables.
HTH
Fred
--
http://www.crowsons.com/puters/x41.htm
