From owner-freebsd-stable@FreeBSD.ORG Sun Feb 26 20:28:47 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F353816A422 for ; Sun, 26 Feb 2006 20:28:46 +0000 (GMT) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (tensor.andric.com [213.154.244.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45F2B43D5D for ; Sun, 26 Feb 2006 20:28:44 +0000 (GMT) (envelope-from dimitry@andric.com) Received: from [192.168.0.3] (kilgore.lan.dim [192.168.0.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTP id BBA1DB80D; Sun, 26 Feb 2006 21:28:42 +0100 (CET) Message-ID: <44020D57.5050507@andric.com> Date: Sun, 26 Feb 2006 21:19:35 +0100 From: Dimitry Andric User-Agent: Thunderbird 1.5 (Windows/20060223) MIME-Version: 1.0 To: Ed Maste References: <200602260034.aa33612@nowhere.iedowse.com> <44010701.1050007@andric.com> <20060226020433.GA55658@sandvine.com> In-Reply-To: <20060226020433.GA55658@sandvine.com> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig163E20593D5769000507856F" Cc: Ian Dowse , stable@freebsd.org Subject: Re: RELENG_6: serial console drops back from 115200 to 9600 baud X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 20:28:47 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig163E20593D5769000507856F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ed Maste wrote: >> Okay, but why did 4.x through 5.x through 6.x (these have all been on >> this particular machine) always boot with 115200 until now? :) > Because now the loader has new behaviour of using the existing speed > if the previous stage indicates a serial port is in use, instead > of blindly jamming in a compile-time setting. Fine, but please be aware that this new behaviour violates POLA, at least without a stern notice in UPDATING. :) My idea about hard coded defaults has always been that they are followed, not ignored... > comconsole_speed=3D in /boot/loader.conf > existing speed, if comconsole is already set by previous stage > BOOT_COMCONSOLE_SPEED compile time default Well, the last item will simply never be hit, since there is ALWAYS a previous stage, isn't there? So then you might as well remove the compile time default. Or at least make clear that the compile time default only applies to boot[12], and not the loader. >> Anyway, I also thought that installworld would take care of installing= >> any updated boot blocks, if necessary. I'll manually install them and= >> see what I end up with. >=20 > It doesn't seem that way. They'll be placed in /boot, but not > in the mbr or slice I think. Indeed, as Ian explained. FYI, I've just installed new boot blocks with a configured BOOT_COMCONSOLE_SPEED, commented out the console=3D and comconsole_speed=3D entries in loader.conf, and this works as expected no= w. However, please keep in mind that this might hit non-binary upgraders who use serial consoles, e.g. people with remote boxes in faraway places. They should be warned to either upgrade their bootblocks manually, or set the speed directives in loader.conf. --------------enig163E20593D5769000507856F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) iD8DBQFEAg1fsF6jCi4glqMRA8N1AJoCKlrqOHhCwTZNc/KihFiPz0VrYQCdHgdp kIymVU4LHXd/NhDm5G9etIM= =VKeJ -----END PGP SIGNATURE----- --------------enig163E20593D5769000507856F--