Date: Thu, 21 Jul 2016 03:03:22 +0000 From: Glen Barber <gjb@FreeBSD.org> To: Mark Millard <markmi@dsl-only.net> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD user home directory Message-ID: <20160721030322.GL65494@FreeBSD.org> In-Reply-To: <79BCA7CB-4D6A-45AF-8432-FD7F8577B42F@dsl-only.net> References: <79BCA7CB-4D6A-45AF-8432-FD7F8577B42F@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Cf/4ySkkvY6jtT1l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 20, 2016 at 07:54:27PM -0700, Mark Millard wrote: > Looking at my armv6 and amd64 11.0's (long in use, originally > -CURRENT, now -STABLE, maintained via source updates): >=20 > amd64 and armv6 (rpi2) both have real /usr/home directories. >=20 > armv6 (and rpi2) has no /home path established at all, not even > as a symbolic link to elsewhere. >=20 > amd64 has /home -> usr/home via a symbolic link. >=20 > (I do not have access to check my memory and will not for weeks > but if I remember right my powerpc64 and powerpc 11.0's were like > amd64 above. They dated back to somewhat before 2016-June-04 when > last updated.) >=20 > If I remember right my old powerpc and powerpc 10.x-STABLE's and > 10.x-RELEASES also agreed with amd64 above. (At the time I only was > experimenting with powerpc64 and powerpc FreeBSD.) >=20 > In comparison today's -r303119 says: >=20 > > Log: > > Create a /usr/home -> /home symlink for the arm images to > > avoid /usr/home confusingly being created as a directory. >=20 >=20 > May be which path is to directly be the actual directory by default > has changed --since all of my contexts started long ago. >=20 > But what all my confirmable examples suggest is that /usr/home > is normally the directory. >=20 > I did not manually control or create /usr/home for any of the > contexts as far as I can remember. It was automatic as a side effect > of some activity. >=20 Right, but as we do not provide binary upgrade paths for tier-2 architectures, nothing should be affected for source-based upgrades. Especially in this case. > If there is variability up to now or across architectures it might > be appropriate to have an UPDATING entry to indicate the new uniform > answer or whatever describes how things now are. >=20 > Are there alternative standard FreeBSD installation techniques > that may be should all be made to match for such properties? (POLA > for such defaults: lack of variability across [the major or official] > techniques?) >=20 This is discussion that is not applicable for the commit to which you reference. It creates a symlink on an image that is "installed" by writing a raw filesystem onto an SD card via dd(1). This does not affect source-based upgrades. Glen --Cf/4ySkkvY6jtT1l Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXkDt1AAoJEAMUWKVHj+KT41UP/iPE6utgHJrQYDoMs2pNqzWG +90EGAQn8TAe3Z4Pcv5LjHBp42Y3rr6srwxlBJ5vP0Z06LaxtchyFnV3M1txFGkQ Da3+qT53SVDAPtq2tAVkhutff2/sjNUH25QSVAlT4yhYSxnuKgk6LIf7jV/PyQyf Oi9lwRObOzDQ0TWvw2oaNvgS+X3lguOcLpvdz/+35JrFIFlYxaxtwayLG0QOYZVm vYgxgDG/uGS4B1XOKVrUR5aWb77qPNFrHTo3ADpc8+YBmNTc5I6Y7RrXp3GjoUl6 WOZQLpyolyALhTP/U5o/14zaOcLi0iGPMGIe7KIlY4HNtHwWNZwfQdWAw2kPyu8m ax4rgVoyjpZhNoxbgsOJaZB9bMTR/z9pD6p054Bo7Jcil34XRMzJQxTO5zStPxBr 8Lm2NMfmVqWSlegMsJO2/yVWsbBAqQdxCEZ0xDgBWTCRE4YBX41bRlqDfBjg4iSg OTwkob9z7koZL5jjkXCLIZrs/fd5fgEDcSW7lMIHtZ3x3a4qgalWYAw/+ujigrRX UdfzeILo4OtZ4F/he5pvuCrs9yl18YaY118VGUa4OEHNZgL0V8QTikCWHcYTAUlf QvCZdL87UedhQ5v5XMIwnJnO67Ou9TguRicM0iIHW/jx4wyvaIL4cFKfOx5EzMCn PD7Is6MJmm0WhQex4VNN =eQVK -----END PGP SIGNATURE----- --Cf/4ySkkvY6jtT1l--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160721030322.GL65494>