From owner-freebsd-cloud@freebsd.org Fri Sep 1 21:24:58 2017 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59734E07EAE for ; Fri, 1 Sep 2017 21:24:58 +0000 (UTC) (envelope-from raf@rafal.net) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A2AB64545 for ; Fri, 1 Sep 2017 21:24:57 +0000 (UTC) (envelope-from raf@rafal.net) Received: from [192.168.40.37] (unknown [86.40.118.125]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 13243509B6 for ; Fri, 1 Sep 2017 17:24:49 -0400 (EDT) From: Rafal Lukawiecki Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Launch and boot times of AWS FreeBSD AMI Message-Id: Date: Fri, 1 Sep 2017 22:24:46 +0100 To: freebsd-cloud@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2017 21:24:58 -0000 I wonder if there is any possibility to shorten the launch and reboot = times of the FreeBSD AMI. I understand that it is necessary to have the = first post-install and update reboot, after the initial launch, but it = seems to take a longish time compared to Amazon Linux. Without any solid = measurements, it seems, from the =E2=80=9CVGA=E2=80=9D console, that it = does pause a bit after printing the SSH fingerprint and starting cron, = sendmail, configuring vt, scheduling a background fsck in 60 secs, and = printing these odd messages: [: =3D: unexpected operator [: =3D: unexpected operator mount: /dev/gpt/rootfs: Device busy [: =3D: unexpected operator ...all before rebooting itself for that first time. I wonder if it could be optimised, somehow. It would be nice to shave a = minute or more from the waits, if possible. I am also curious what those = errors are. Rafal -- Rafal Lukawiecki Data Scientist=20 Project Botticelli Ltd