From owner-freebsd-current@freebsd.org Fri Mar 18 21:33:06 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 5B818AD4A3B for ; Fri, 18 Mar 2016 21:33:06 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D4C28EB; Fri, 18 Mar 2016 21:33:05 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi0-f50.google.com with SMTP id r187so99552744oih.3; Fri, 18 Mar 2016 14:33:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc; bh=aIdPumz3sn1TSgEGs5ALekE7PK0nIa9c+BtbLYDxMeI=; b=Rpo49wUd2sisIt0Bj2kbWuJBK3CijnlHCkbVex73kIK7S87LdQPaCBC9gXv2LxQAkU FyjSc3uUB3KYIFPeAjbfou+toISvB1JM8KX/Sb9oouFwWXEx+IklOxIVUgUy018cV4YB FQBXa7S5IHG+uCydsLnMxWvHQbioFr93QOQfudoZbcxEmWZp3Xt3+1TlxU7Gb01/s55V wLNcj7BgSqLVVzhZSp91UJHbnWcK3KJtW8BFjura9ozQLlMV7MAi0mjTaorCAYzvRDoL dWkMEM5Lvcc0aD0HY35ATwtU9ARqtDzOstXkKFZA5zJ4RxqxXgiYzJf/b7U9Sti6GwJZ znfQ== X-Gm-Message-State: AD7BkJI3zkUKG/4Wr5sQ+50/y50S5UmklLrtoGQcNDjxiWI/+94ACFqNyCM1vC996G08Jw== X-Received: by 10.202.85.14 with SMTP id j14mr9956043oib.45.1458322767635; Fri, 18 Mar 2016 10:39:27 -0700 (PDT) Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com. [209.85.214.175]) by smtp.gmail.com with ESMTPSA id fg6sm6247143obc.9.2016.03.18.10.39.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Mar 2016 10:39:27 -0700 (PDT) Received: by mail-ob0-f175.google.com with SMTP id ts10so123042806obc.1; Fri, 18 Mar 2016 10:39:27 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.58.97 with SMTP id p1mr10326273obq.33.1458322767084; Fri, 18 Mar 2016 10:39:27 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.157.36.202 with HTTP; Fri, 18 Mar 2016 10:39:27 -0700 (PDT) In-Reply-To: <56EC34CE.1000002@freebsd.org> References: <56EC2DD3.6050803@madpilot.net> <56EC34CE.1000002@freebsd.org> Date: Fri, 18 Mar 2016 10:39:27 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: boot loaders got fatter in the last few days From: Conrad Meyer To: Allan Jude Cc: freebsd-current Content-Type: text/plain; charset=UTF-8 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 21:33:06 -0000 On Fri, Mar 18, 2016 at 10:03 AM, Allan Jude wrote: > On 2016-03-18 12:33, Guido Falsi wrote: >> >> 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): >> >> -r--r--r-- 1 root wheel 85794 Mar 18 16:47 /boot/gptboot >> >> from a machine I still have not updated(r296719): >> >> -r--r--r-- 1 root wheel 16059 Mar 13 21:01 /boot/gptboot So the loader grew 70 kB. How big are your disks? >> I noticed because mu gpt boot partition is 64K and gptzfsboot just >> passed 100K. > > This is a side effect of the loader gaining the ability to boot from GELI > encrypted partitions. > > ... > > Maybe we should be putting the GELI enabled boot blocks in a different > filename? I generally wanted to avoid creating a new version of each > bootcode with GELI support. I think we should just suggest that boot partitions be much larger than 64kB (1MB is still <0.1% of any disk sold today) and not worry about it too much. Embedded applications can disable GELI loader support to save a few bytes. Best, Conrad