Date: Mon, 18 Jul 2022 14:08:51 +0000 From: Glen Barber <gjb@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: dev-commits-src-main@freebsd.org Subject: Re: git: 1dfcff294e44 - main - release: increase IMAGE_SIZE for arm, arm64, riscv Message-ID: <20220718140851.GA95937@FreeBSD.org> In-Reply-To: <DBED097F-00BD-467C-8CA3-49857DA35456@yahoo.com> References: <84410D65-6F86-44E5-8B14-8A523C9919C7@yahoo.com> <20220713201327.GY30607@FreeBSD.org> <7F4F9683-B4DE-4F65-BBD7-027039A0C270@yahoo.com> <20220713204227.GA30607@FreeBSD.org> <8A02A4A4-9F3A-47F2-9985-EA2151043BB7@yahoo.com> <4D903E5A-58FB-4516-AC53-AEDFF48564A7@yahoo.com> <20220714152125.GB30607@FreeBSD.org> <3E2DCFBD-CC8F-4C13-B18C-B7DA26ED8E84@yahoo.com> <AE47C47B-33F7-4236-8A23-688C40340EA7@yahoo.com> <DBED097F-00BD-467C-8CA3-49857DA35456@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 16, 2022 at 11:24:47PM -0700, Mark Millard wrote: >=20 >=20 > On 2022-Jul-15, at 17:41, Mark Millard <marklmi@yahoo.com> wrote: >=20 > > FYI for the new snapshot build of 13.1-STABLE: > >=20 > > # mdconfig -u0 -f FreeBSD-13.1-STABLE-arm64-aarch64-RPI-20220715-831c6b= 8edda-251792.img=20 > > # gpart show md0 > > =3D> 63 10485697 md0 MBR (5.0G) > > 63 2016 - free - (1.0M) > > 2079 102312 1 fat32lba [active] (50M) > > 104391 10381329 2 freebsd (5.0G) > > 10485720 40 - free - (20K) > >=20 > > So: still has the 2016 and 2079 that do not seem to match > > what /usr/src/release/ materials would indicate --and the > > 2079 leads to poor alignment for a microsd cards, for > > example. > >=20 > > But, at least something was produced this time. There is > > now a 13.1-STABLE snapshot to test the handling related > > to the new UFS/FFS superblock validations. >=20 > In the live build environment that makes the images, > what is: >=20 > # sysctl kern.geom.part.mbr.enforce_chs > kern.geom.part.mbr.enforce_chs: 0 >=20 > I ask because of the description: >=20 > QUOTE > kern.geom.part.mbr.enforce_chs: 0 > Specify how the Master Boot Record (MBR) module does alignme= nt. > If this variable is set to a non-zero value, the module will > automatically recalculate the user-specified offset and size= for > alignment with the CHS geometry. Otherwise the values will = be > left unchanged. > END QUOTE >=20 > In particular, the text about non-zero values leading to: >=20 > QUOTE > the module will > automatically recalculate the user-specified offset and size= for > alignment with the CHS geometry > END QUOTE >=20 > This sounds like a potential way to not end up with the > what the /usr/src/release handling requests for the > small board computer images. It might explain the > mismatched alignment that I've been reporting. >=20 It is set to '1' on all three systems. If this is causing a problem, it is weird we have a problematic setting as the default. Glen --T4sUOijqQbZv57TR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmLVaW4ACgkQAxRYpUeP 4pM3Pw/8CpO99z21ds2wmP8tyCMA3ZpyoFfQcj8pY9J/OSEbm8uKOkjnio8qyBFx eWnt/dt1m62K0VU2CNN1CrRm9/ziWV6pcS06m7iyvqqam6CXh6viIVQ66jhHUBbG 818b34znPPQ6vTOOLkPfurs8CX72GipIXXJN0M6x7NCITBy1pR/iyHIqfZdpksWD Keu1xXLOovp8IHEqdiZJoqQJmQX5x+VMurgw2YZqi9fFgqvovFTaQAc0wMOX89/I dDh5aXOT91sgcdYEO/Fwyaf+L6PRlO1Ih0Ut6rfVeszVrxCWGGL5ygboZDPsGobR ioYSizK9uJKCcD9PGfg9p31di0xkCXlHUb4uGyuiXWr6eOye/HS8e539dhZo2d0c pWaW0J/JxPc31CS5t02fZZm07/WqAxFqEIiYgedH8ueLtNIv2yJGlVbI0wpGXH/0 R2VRNOHV8gOWzmDdkUSm16eiiK6slLmLSp+hYSJ2MjMSOI6WH3M0O2/7ZR/qezW9 yFXCeZlySl5qbSCfLiu0JTSzB3LE5ogJEKolNQQd9mIxOuWdyLYZL26smTT6g/fX SgVDeaDycQTHhMLXKRgqm7ZJylqx6sVLvDnN72c5Lx9pbqfeLRaEf4ayNFz1TcPT Ua2hiUeOAm0Tu9QRe3ott1K/q0O5DOWM2qRquMce7XFBsB08bUI= =yY94 -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220718140851.GA95937>