From owner-freebsd-stable@FreeBSD.ORG Sun Feb 26 20:28:45 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 2543516A420 for ; Sun, 26 Feb 2006 20:28:45 +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 B61FD43D5A for ; Sun, 26 Feb 2006 20:28:43 +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 EE9F3B80C; Sun, 26 Feb 2006 21:28:41 +0100 (CET) Message-ID: <440200F2.9010106@andric.com> Date: Sun, 26 Feb 2006 20:26:42 +0100 From: Dimitry Andric User-Agent: Thunderbird 1.5 (Windows/20060223) MIME-Version: 1.0 To: Ian Dowse References: <200602260156.aa34941@nowhere.iedowse.com> In-Reply-To: <200602260156.aa34941@nowhere.iedowse.com> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigABF0B2A94073A4A90424DE4E" Cc: stable@freebsd.org, Ed Maste 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:45 -0000 X-List-Received-Date: Sun, 26 Feb 2006 20:28:45 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigABF0B2A94073A4A90424DE4E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ian Dowse 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? :) > They probably used 9600 for the boot blocks, and then switched to > 115200 when /boot/loader started, so you didn't notice. Now the > settings from the boot blocks get used by /boot/loader. Ah, but this still means that /boot/loader used to use a hardcoded default specified in /etc/make.conf, and now it doesn't honor that anymor= e. There should at least be a notice in UPDATING, e.g. "don't forget to set comconsole_speed in your loader.conf, or your serial console won't work anymore after upgrading." It would probably save some people a drive to the colocation facility... ;) > Boot blocks need to be installed manually - installworld installs > the boot blocks as files in /boot/boot{1,2}, but when booting, it > is the boot blocks in the first 8k of the slice that are used, not > the /boot/boot{1,2} files. Okay. I still think it would be wiser to just reinstall them during installworld, just to be sure there's no incompatibilities... --------------enigABF0B2A94073A4A90424DE4E 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) iD8DBQFEAgD4sF6jCi4glqMRA/m4AJ9dcRlXK3Pp62V+bCDKXA+v7JvHuQCghI2r aHSGlm6wUYcZliH530MlGYE= =fTjY -----END PGP SIGNATURE----- --------------enigABF0B2A94073A4A90424DE4E--