From owner-freebsd-arm@freebsd.org Thu Jul 21 07:55:43 2016 Return-Path: Delivered-To: freebsd-arm@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 14CB0BA0662 for ; Thu, 21 Jul 2016 07:55:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-156.reflexion.net [208.70.211.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D139C11CC for ; Thu, 21 Jul 2016 07:55:42 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 30597 invoked from network); 21 Jul 2016 07:55:42 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 21 Jul 2016 07:55:42 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.90.6) with SMTP; Thu, 21 Jul 2016 03:55:35 -0400 (EDT) Received: (qmail 9609 invoked from network); 21 Jul 2016 07:55:35 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Jul 2016 07:55:35 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.0.105] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id B84B51C407A; Thu, 21 Jul 2016 00:55:39 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: FreeBSD user home directory From: Mark Millard In-Reply-To: <9F4673FD-828B-4809-911B-00EDD601C425@dsl-only.net> Date: Thu, 21 Jul 2016 00:55:39 -0700 Cc: freebsd-arm , Russell Haley Content-Transfer-Encoding: quoted-printable Message-Id: <13F2EBE9-4510-4D59-8059-6279560CBAFA@dsl-only.net> References: <79BCA7CB-4D6A-45AF-8432-FD7F8577B42F@dsl-only.net> <20160721030322.GL65494@FreeBSD.org> <9F4673FD-828B-4809-911B-00EDD601C425@dsl-only.net> To: Glen Barber X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 07:55:43 -0000 On 2016-Jul-20, at 11:59 PM, Mark Millard wrote: > On 2016-Jul-20, at 8:03 PM, Glen Barber wrote: >=20 >> 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 >>=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. >>=20 >>> 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 >>=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. >>=20 >> Glen >=20 > Just an FYI: >=20 > I think I found were my amd64 /usr/home came from: I happened to have > experimented with zfs for that and /usr/libexec/bsdinstall/zfsboot = uses > the following in defining ZFSBOOT_DATASETS >=20 > # Home directories separated so they are common to all BEs > /usr/home # NB: /home is a symlink to /usr/home >=20 > (BE in "BEs" is "Boot Environment".) My only amd64 environment is the > only context that I've experimented with zfs in. >=20 > It is true that this is not likely to have much in common with how my > armv6, powerpc64, and powerpc environments got to be /usr/home style > (all tier 2). Another FYI: I think I've tracked down where my armv6 /usr/home came = from: I happened to experiment with crochet for my very first armv6 creation = and I've never had to start from scratch again for armv6 after that. # grep -i home ~/crochet/option/User/setup.sh HOME_DIR=3D/usr/home mkdir -p ${BOARD_FREEBSD_MOUNTPOINT}${HOME_DIR}/$1 $PW -V ${BOARD_FREEBSD_MOUNTPOINT}/etc/ useradd -n $1 -s /bin/csh -g = wheel -w yes -d ${HOME_DIR}/$1 $CHOWN $UGID ${BOARD_FREEBSD_MOUNTPOINT}${HOME_DIR}/$1 So crochet uses /usr/home as the directly existing directory (or did at that time anyway). (I'm not saying that crochet is a standard technique. I had forgotten = that I had happened to decide to experiment with it just the one time when I first created a armv6 context.)