Date: Fri, 6 Dec 1996 00:52:39 -0800 (PST) From: John-Mark Gurney <jmg@nike.efn.org> To: FreeBSD Hackers <hackers@freebsd.org> Subject: possible bug in comconsole code... Message-ID: <Pine.NEB.3.95.961206002559.19335E-100000@nike>
next in thread | raw e-mail | index | archive | help
well... I have set up a terminal server that has a few ports on it right now... and it doesn't have a video card... so I'm using comconsole (not intentionally)... just so you know... I'm using 2.2-960801-SNAP for the termserver (using devfs) because this is the version my machine machine is... so I finally attached a machine to monitor the port... but I was only getting part of the message... and I couldn't figure out why... I tried some basic stuff like "echo blah > /dev/cuaa0" which just returned a single "b"... then I thought that the port might be closing before the data was sent... so a "(echo blah;sleep 1)> /dev/cuaa0" got the whole thing sent out... with this info... I decided to run a getty on the port... and now... the console messages are sent out in their entirety... is there a possible fix to either "simulate" like the port is open continuously... or possibly just not have the port closed? also... is this a bug? or just an wetware bug (meaning I need to run getty on the port)? just wondering... thanks for all the help...- John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.961206002559.19335E-100000>