Date: Tue, 11 Feb 1997 20:07:38 +1100 From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@freefall.freebsd.org, jmg@nike.efn.org Subject: Re: bin/174 stty doesn't give very good output on error... Message-ID: <199702110907.UAA13503@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
[ stty -f /dev/cua00 76800 ] > the bug can't be fixed unless there is some restructuring of stty... and > this probably shouldn't happen... Another problem is that according to POSIX.1, success of tcsetattr() doesn't mean that all the attributes were set. It means that at least one attribute was set, and that other attributes were set if the system supports them. Perhaps the best way to fix this is to fix tcsettattr() in all drivers to succeed if at least one attribute could be set, so that an unsupported speed is never fatal (it's always possible to set a non-hardware attribute like OPOST to any value, so one attribute can always be set :-). stty.c could then check which attributes were set. It probably should do this anyway. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702110907.UAA13503>