Date: Sun, 25 Feb 2001 14:58:57 -0500 From: Andrew J Caines <A.J.Caines@altavista.net> To: freebsd-stable@FreeBSD.ORG Subject: Re: CVSup and everything that goes with it Message-ID: <20010225145857.O83990@hal9000.bsdonline.org> In-Reply-To: <4.3.2.7.2.20010225131003.00dc8d90@dca.net>; from smackme@hardwaregroup.com on Sun, Feb 25, 2001 at 01:50:08PM -0500 References: <4.3.2.7.2.20010225131003.00dc8d90@dca.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jim, Since you are under such time pressure, I thought that I couple of scripts which I use to update my STABLE boxes might help you. They seem to have been well received by others. You can get them from: <http://hal9000.bsdonline.org/software/scripts/update_stable>; <http://hal9000.bsdonline.org/software/scripts/install_stable>; The scripts are primarily designed to update and existing STABLE install, with update_stable running periodically in multi-user mode, then install_stable run at the admin's discretion to update the system. Apart from creating a few directories and getting you sup files in order, they should either work for you, or give you enough information to do the job yourself. The last word on updating is always in /usr/src/UPDATING. > So which is it? /usr/local/etc/cvsup or /usr/sup Or is it both? You can tell cvsup which directory to use. /usr/local/etc/cvsup probably already exists. Take a look in /usr/share/examples/cvsup/ for example "sup" files. > make.conf? Is this something I can create to assist "make"? I have yet to > see this in any of the fubar installs and it isn't in this last one. Correct. Like with several other files like rc.conf, you take a look through /etc/defaults/make.conf and override any settings you want by putting them in /etc/make.conf. > The initial install... This is without SMP correct? I think so. > So what is be best approach to doing a custom kernel? (I have zero > experience here) This has worked for me... If GENERIC works for you, then look through GENERIC and remove anything which you know doesn't apply to your system. Build, install and boot the new kernel. If it works, go back and add anything you think is missing based on your study of LINT, the Handbook and other sources of good advice. Repeat, stir and rinse. In the end the goal is to have a kernel which does all of what you want and nothing you don't. Make sure that you are building your kernels in the same "world" to which you updated. That is, don't try to build only a new kernel after cvsup'ing. > >The last step is to merge in the new /etc stuff and that is most easily > Merge? From where to /etc? Yes. Mergemester takes the changes in /usr/src/etc (and maybe other places) and lets you update your existing /etc in an intelligent way with the changes. I recommend opting to let mergemaster replace any file in /etc which you don't know you've changed - typically rc scripts and such - and merge the rest, taking at least the new version header from the updated file. > Oh, my latest install... "cd /usr/ports/www/cvsup" "make clean install" > What will this do? Probably waste some of your time and add some confusion. Try something like this: # cd /usr/ports/net/cvsup-bin # make install # make clean The "cvsup-bin" port is all you need to use cvsup, that is if you haven't already added it as a package, which I suspect you have. Note that you can add packages on the net as well as from local sources. For example, # pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/packages/net/cvsup-bin-16.1.tgz If you add a package, then want to update it from the ports collection, then don't forget to remove the old package first with pkg_delete first. Have fun with your updating. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@altavista.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010225145857.O83990>