From owner-freebsd-current@freebsd.org Fri Mar 18 16:56:35 2016 Return-Path: Delivered-To: freebsd-current@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 09624AD54A0; Fri, 18 Mar 2016 16:56:35 +0000 (UTC) (envelope-from fbl@aoek.com) Received: from srv56-45.cdn.bestreaming.com (ns330343.ip-37-187-119.eu [37.187.119.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BF48D1DC3; Fri, 18 Mar 2016 16:56:31 +0000 (UTC) (envelope-from fbl@aoek.com) Received: from mail.yourbox.net (localhost [IPv6:::1]) by srv56-45.cdn.bestreaming.com (8.15.2/8.15.2) with ESMTP id u2IGso2K077199; Fri, 18 Mar 2016 17:54:50 +0100 (CET) (envelope-from fbl@aoek.com) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 18 Mar 2016 17:54:50 +0100 From: =?UTF-8?Q?Jos=C3=A9_P=C3=A9rez?= To: Guido Falsi Cc: freebsd-current@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: boot loaders got fatter in the last few days In-Reply-To: <56EC2DD3.6050803@madpilot.net> References: <56EC2DD3.6050803@madpilot.net> Message-ID: <184a723793384094ded3c6037dd19529@mail.yourbox.net> X-Sender: fbl@aoek.com User-Agent: Roundcube Webmail/1.1.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 16:56:35 -0000 Hi Guido, maybe it's because of this: https://svnweb.freebsd.org/base?view=revision&revision=296963 Regards, --- José Pérez El 2016-03-18 17:33, Guido Falsi escribió: > Hi, > > I have just update one of my machines and noticed the booloaders files > got quite fat in the last few days, some by a big margin. > > on an updated machine(r296993): > >> ls -l /boot/*boot* > -r--r--r-- 1 root wheel 8192 Mar 18 16:47 /boot/boot > -r--r--r-- 1 root wheel 512 Mar 18 16:47 /boot/boot0 > -r--r--r-- 1 root wheel 512 Mar 18 16:47 /boot/boot0sio > -r--r--r-- 1 root wheel 512 Mar 18 16:47 /boot/boot1 > -r-xr-xr-x 1 root wheel 72152 Mar 18 16:47 /boot/boot1.efi > -r--r--r-- 1 root wheel 819200 Mar 18 16:47 /boot/boot1.efifat > -r--r--r-- 1 root wheel 7680 Mar 18 16:47 /boot/boot2 > -r--r--r-- 1 root wheel 1185 Mar 18 16:47 /boot/cdboot > -r--r--r-- 1 root wheel 85794 Mar 18 16:47 /boot/gptboot > -r--r--r-- 1 root wheel 110546 Mar 18 16:47 /boot/gptzfsboot > -r--r--r-- 1 root wheel 358400 Mar 18 16:47 /boot/pxeboot > -r--r--r-- 1 root wheel 341248 Mar 18 16:47 /boot/userboot.so > -r--r--r-- 1 root wheel 66048 Mar 18 16:47 /boot/zfsboot > > from a machine I still have not updated(r296719): > >> ls -l /boot/*boot* > -r--r--r-- 1 root wheel 8192 Mar 13 21:01 /boot/boot > -r--r--r-- 1 root wheel 512 Mar 13 21:01 /boot/boot0 > -r--r--r-- 1 root wheel 512 Mar 13 21:01 /boot/boot0sio > -r--r--r-- 1 root wheel 512 Mar 13 21:01 /boot/boot1 > -r-xr-xr-x 1 root wheel 72152 Mar 13 21:01 /boot/boot1.efi > -r--r--r-- 1 root wheel 819200 Mar 13 21:01 /boot/boot1.efifat > -r--r--r-- 1 root wheel 7680 Mar 13 21:01 /boot/boot2 > -r--r--r-- 1 root wheel 1185 Mar 13 21:01 /boot/cdboot > -r--r--r-- 1 root wheel 16059 Mar 13 21:01 /boot/gptboot > -r--r--r-- 1 root wheel 41511 Mar 13 21:01 /boot/gptzfsboot > -r--r--r-- 1 root wheel 288768 Mar 13 21:01 /boot/pxeboot > -r--r--r-- 1 root wheel 341208 Mar 13 21:01 /boot/userboot.so > -r--r--r-- 1 root wheel 66048 Mar 13 21:01 /boot/zfsboot > > I noticed because mu gpt boot partition is 64K and gptzfsboot just > passed 100K. > > Is this expected and I'm supposed to repartition or is this an unwanted > mistake? > > Thanks in advance.