Date: Wed, 06 Mar 2019 15:40:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236323] [mkimg] Allow specifying (minimum) partition table size where applicable Message-ID: <bug-236323-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236323-227>