From owner-freebsd-bugs@freebsd.org Wed Mar 6 15:40:58 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CA38151B189 for ; Wed, 6 Mar 2019 15:40:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C605791AC3 for ; Wed, 6 Mar 2019 15:40:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7CB61151B188; Wed, 6 Mar 2019 15:40:57 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57C59151B187 for ; Wed, 6 Mar 2019 15:40:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E1DF991ABB for ; Wed, 6 Mar 2019 15:40:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 22DF18C67 for ; Wed, 6 Mar 2019 15:40:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x26FeuXo090687 for ; Wed, 6 Mar 2019 15:40:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x26FeuXj090685 for bugs@FreeBSD.org; Wed, 6 Mar 2019 15:40:56 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236323] [mkimg] Allow specifying (minimum) partition table size where applicable Date: Wed, 06 Mar 2019 15:40:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: marcel@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Mar 2019 15:40:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236323 Bug ID: 236323 Summary: [mkimg] Allow specifying (minimum) partition table size where applicable Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: marcel@FreeBSD.org By default, mkimg(1) creates a disk image that uses a partition table size = that is large enough to hold the partitions given to mkimg(1). Rounding of the number of partition entries, as implemented for bin/236238, is possible whe= re it makes sense but does not structurally provide a way to make sure there a= re free partitions. Arguably, the -p option can be used to add a few empty partitions, but in t= he GPT case this gets painful if the user really desires a GPT partition table that has the default number of partition entries in it. The default number = is 128, requiring 128 -p options, of which more than 100 are for padding purpo= ses only. The APM scheme has a similar problem in that each partition entry is in its= own sector. Once the disk image has be created and the first sector of the first partition is adjacent to the last sector of the partition table, no more partitions can be added. And that's fundamentally the point of this bug: provide a way to make sure = that either 1) the number of entries can be specified, or 2) the number of extra entries can be specified. It's not clear which approach works better as a generic solution given that= it won't apply to some schemes like MBR. --=20 You are receiving this mail because: You are the assignee for the bug.=