From 4c710b6756bbf8fdca97a8b6ed40f69bec8ab291 Mon Sep 17 00:00:00 2001 From: Marcel Moolenaar Date: Sat, 5 Apr 2014 22:25:10 +0000 Subject: Do not prevent processes from making changes to the baudrate or the CLOCAL and HUPCL control flags. There are legit reasons for allowing those to be changed. When /etc/ttys has the "3wire" type (without a baudrate) for the serial port that is the low-level console, then this change has no effect. Obtained from: Juniper Networks, Inc. --- UPDATING | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'UPDATING') diff --git a/UPDATING b/UPDATING index 1af673cab87db..1d4faae4a2f71 100644 --- a/UPDATING +++ b/UPDATING @@ -31,6 +31,20 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW: disable the most expensive debugging functionality run "ln -s 'abort:false,junk:false' /etc/malloc.conf".) +20140405: + The uart(4) driver has been changed with respect to its handling + of the low-level console. Previously the uart(4) driver prevented + any process from changing the baudrate or the CLOCAL and HUPCL + control flags. By removing the restrictions, operators can make + changes to the serial console port without having to reboot. + However, when getty(8) is started on the serial device that is + associated with the low-level console, a misconfigured terminal + line in /etc/ttys will now have a real impact. + Before upgrading the kernel, make sure that /etc/ttys has the + serial console device configured as 3wire without baudrate to + preserve teh previous behaviour. E.g: + ttyu0 "/usr/libexec/getty 3wire" vt100 on secure + 20140325: It is no longer necessary to include the dwarf version in your DEBUG options in your kernel config file. The bug that required it to be -- cgit v1.2.3