From owner-freebsd-stable Wed Mar 13 3:16:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from bazooka.trit.org (bazooka.trit.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id B724737B405; Wed, 13 Mar 2002 03:16:26 -0800 (PST) Received: by bazooka.trit.org (Postfix, from userid 1000) id 59D1E3E3E; Wed, 13 Mar 2002 11:16:26 +0000 (UTC) Received: from bazooka (localhost [127.0.0.1]) by bazooka.trit.org (Postfix) with ESMTP id 584283C12E; Wed, 13 Mar 2002 11:16:26 +0000 (UTC) To: bmah@FreeBSD.ORG Cc: Cliff Sarginson , stable@FreeBSD.ORG, jhb@freebsd.org, nyan@jp.FreeBSD.org, matusita@jp.FreeBSD.org Subject: Re: /usr/sbin/sysinstall for -stable (cvs commit: src/release/sy In-Reply-To: <200203121832.g2CIWUs25950@bmah.dyndns.org>; from bmah@FreeBSD.ORG on "Tue, 12 Mar 2002 10:32:30 -0800" Date: Wed, 13 Mar 2002 11:16:21 +0000 From: Dima Dorfman Message-Id: <20020313111626.59D1E3E3E@bazooka.trit.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Bruce A. Mah" wrote: > If memory serves me right, Cliff Sarginson wrote: > > On Tue, Mar 12, 2002 at 12:30:40PM +1100, Gregory Bond wrote: > > > > Actually, it violated my POLA to discover sysinstall wasn't rebuild during > > > buildworld.... > > > > > Mine too :) > > I would have no objections to it being moved. > > I am wondering if there are any serious implications of not being able > > to run it in single-user with only / mounted. I cannot think of > > any... ? > > If there are maybe /sbin is the place. > > It is going to get moved anyway, might as well do it now. With a big > > note in UPDATING of course...and a little script to echo this fact when > > you type "./sysinstall" in "/stand" ? > > Uh...wait a sec... > > /stand/sysinstall is the crunched binary that you get on the > installation media. It is never updated with an installworld. As far > as I can tell, this is true even on -CURRENT systems. > > /usr/sbin/sysinstall exists only on -CURRENT. It is a "normal", > dynamically-linked executable that *does* get updated with a buildworld/ > installworld. Correct. The change I'm proposing to merge moves the sysinstall sources from src/release/sysinstall to src/usr.sbin/sysinstall and installs sysinstall into /usr/sbin as part of installworld. /stand is not going away, and its semantics will remain the same (e.g., we're not going to start updating it during installworld). To those who responded about this being a possible POLA violation: Could you please elaborate? The only user-visible change is the appearance of /usr/sbin/sysinstall, and the only developer-visible change is moving the sources. I think the latter is acceptable for -stable, esp. since, as bmah points out, it makes MFCs easier. To those who suggest /sbin as an alternative or other such changes: I'm proposing to merge a change from -current. We had all of these arguments before that change, and I'd rather not see them reiterated here; the archives are good enough for me :-). Per nyan's request, I'm going to hold off doing this until the problem he reported is resolved. It looks like matusita will pick up the ball on this one, so it shouldn't be long--hopefully. Thanks, guys! (FWIW, it's to avoid aggravating this kind of issue that I decided to post this proposal to -stable instead of just asking jhb.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message