Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 May 2014 08:27:29 -0700 (PDT)
From:      Jakub Lach <jakub_lach@mailplus.pl>
To:        freebsd-current@freebsd.org
Subject:   Re: newcons and beeping X
Message-ID:  <1399044449214-5908275.post@n5.nabble.com>
In-Reply-To: <CAPyFy2Bi67k2OAhMEDjZa4F9p62=cs-VF1OR3Hj3_uc0XUEzFw@mail.gmail.com>
References:  <20140427143320.GA7138@over-yonder.net> <20140501083121.GU7138@over-yonder.net> <1398935140660-5907856.post@n5.nabble.com> <CAPyFy2B8E2juz2tfog8V48=N6cJN4fe-jG7VitOwVzY2oAqdRA@mail.gmail.com> <1398951899525-5907951.post@n5.nabble.com> <1398963647154-5908019.post@n5.nabble.com> <CAPyFy2BQm9SMNONpv=AXpP=A_C04aRM6zF0EjFpmH5ttnrTcdA@mail.gmail.com> <1398979023495-5908076.post@n5.nabble.com> <1398979896771-5908080.post@n5.nabble.com> <CAPyFy2Bi67k2OAhMEDjZa4F9p62=cs-VF1OR3Hj3_uc0XUEzFw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
By choppy I've also meant it's noticeably slower 
than syscons, but I think it's already known.

The shell was a shells/mksh.

I think I may switch to newcons permanently 
after a merge of bell patch thing.



--
View this message in context: http://freebsd.1045724.n5.nabble.com/newcons-and-beeping-X-tp5906883p5908275.html
Sent from the freebsd-current mailing list archive at Nabble.com.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1399044449214-5908275.post>