Date: Fri, 17 May 1996 07:46:17 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: "Richard Wackerbarth" <rkw@dataplex.net> Cc: "FreeBSD Hackers" <hackers@FreeBSD.ORG> Subject: Re: Re(2): Standard Shipping Containers Message-ID: <4090.832344377@time.cdrom.com> In-Reply-To: Your message of "17 May 1996 09:03:42 CDT." <n1379798653.81207@Richard Wackerbarth>
next in thread | previous in thread | raw e-mail | index | archive | help
> Don't forget the "live file system" Fair point, not that I've ever used it for that purpose to date. :-) > I'm afraid it is a little more complicated. But not an impossible task. > Where do you want the updates collected? > Do you want the updates applied automatically? > Do you want to save the updates or delete them after they are applied? OK. But certainly no more complicated than, say, the anonymous ftp setup screen. > If we are going to do this (and I think it is a good idea) it places an even > greater value on being able to do two things. > > (1) The ability to run this setup program after a system is set up: Just like > the guy who wants to add a HD after the fact, a user is likely to first get > the system up either without the sources or with the sources from the tarball > or CD and later decide that he wants to add the ctm feature. Absolutely. Just like packages, samba, anon ftp setup, etc. Not only should everything be re-entrant via the sysinstall menus at post-installation time, but we can now have shell scripts that call sysinstall with arguments now to invoke specific subsystems directly if we want to provide a few aliases (e.g. `sysinstall configPackages' for a pkg_manage replacement, or `sysinstall configCTM' to drop into your CTM configuration dialogs). I'm definitely trying to maximize its utility for post-installation tasks. > (2) The unified source product: > There is no need to download 28M again if only we can recognize what the user > already has. By making the source tree carry a tree isomorphic to a ctm > update, including the appropriate tag, we can automate the process of updatin g > from that point. This applies to both ctm and sup. That's sort of an added pain-in-the-butt, but I guess we'll figure out some way of dealing with the syncronization issues in the release tools. Currently I just check out a copy of the source tree and I don't need to worry about whether or not what's there at the end of the cvs checkout run matches the state of my captured CTM deltas. That little wrinkle has to be worked out and some major testing of the implementation done before your dream can become reality here. Also, I would expect configCTM() and configSUP() to have enough in-built smarts to detect conflicts, even going so far as to tweak the DIST_SRC flag out of Dists if the user selects a "smarter" source update method which should happen instead of unpacking the src tarball. Sysinstall is really nothing more than a collection of extremely nepotistic routines with vague pretentions of being stand-alone. I don't really mind if one shunts the user down a slightly different installation path. > It will get a little "messy" in that I will have to add a user, add the alias , > send mail, etc. See the anon ftp setup - it does all of those things too, sort of. > How can we best handle the fact that these cannot be done in real time. They > will have to wait for the system to be up and running with everything > installed, etc. Do we have a mechanism to install an execute once script that > will be activated later in the sequence? Not to worry - your config will be called after bindist is extracted and you have the system pretty much "up" and ready to configure. Then it becomes a simple post-installation time problem. > Also, what is your opinion on the "proper" (default) placement of the source > tree. I feel that there needs to be a standard location for each release > version. .../FreeBSD-2.1/src .../FreeBSD-2.2/src Under some basedir and /usr/src as a symlink? Sure, I don't care, just so long as you get the bits on the right filesystems. :-) > Or "mount union"? Broken. > I would tend to suggest /usr/FreeBSD/FreeBSD-2.1.1/src. Bleah! Don't you know The Law? For heretically proposing another directory directly under /usr, you must now die. Sorry, I don't make the rules around here. :-) Pick someplace else please. :-) Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4090.832344377>