[Bug 40956] Re: Running ncpd in Dapper causes major input issues

[Martin Meredith]

mez at tiber % grep tty0 *                                                                  /home/mez/plp/plptools-0.12  5:12PM
configure:      for i in /dev/psion /dev/tty0p0 /dev/tty00 /dev/ttyS0 /dev/term/a /dev/ttyfa /dev/ttya /dev/tty0 /dev/ttyf1 /dev/cuaa1; do
configure.in:      PLP_FIND_CDEV(/dev/psion /dev/tty0p0 /dev/tty00 /dev/ttyS0 /dev/term/a /dev/ttyfa /dev/ttya /dev/tty0 /dev/ttyf1 /dev/cuaa1, DDEV)

having a look at it - and reading through debuugs. .. points out the
following... when it's COMPILING ... it's trying to set the default
device... which on a buildd will default to tty0 - so plptools will be
playing with the console and breaking things...

This is an upstream thing and needs to be fixed there really... it'd be
one hell of a patch from what i can see to patch it ... but i'll have a
look sometime soon and see how big a patch it'll be

-- 
Running ncpd in Dapper causes major input issues
https://launchpad.net/bugs/40956