On Wed, 2002-10-16 at 09:27, BigBrother wrote: > > > I have freebsd 4.6 release and I am interesting to > update it to 4.7 via CVSUP > > The box is located 3000 Kms away and I can only connect > via ssh. > > a) How much space is required in order to make a buildworld > (downloading CVSUP, compiling, installing)
A few hundred MB is a safe bet. > > b) What is the best failsafe method, so in case I do this and > happen to have an error, my system will continue to operate > on the 4.6? As I said I am too far away to go to fix it there... >From personal experience, update sources, rm -rf /usr/obj/*, compile world, compile kernel, drop to single user, install world, install kernel, reboot. If they both compile, it's a good bet they'll run. You can happily compile the new world and kernel, that is 100% sure to not screw anything up, as they both stay under /usr/obj/. You can do what you want, it's still 4.6 until you install them. > > c) Can somebody point me or give me a sample CVSUP configuration > for updating to the 4.7 release? *default host=cvsup2.uk.FreeBSD.org *default base=/usr/local *default prefix=/usr *default release=cvs tag=RELENG_4_7_0_RELEASE *default delete use-rel-suffix *default compress That's mine. Change the host to a local one is all you should need to do. > > > d) Are there any tips for remote updates/buildworld? I know that is not > suggested but I find too difficult to live with all the critical bugs > that 4.6 has and I would like to get rid of them. uh... be careful? Other than that, I wouldn't know. > > e) Do I have to compile only a kernel on 4.7 or to make a buildworld too > for the new binaries to be replaced? If I compile only a 4.7 kernel and > my binaries are 4.6 will this poses any trouble? Very bad idea to only compile a new kernel. Compile the world and the kernel if you want to be sure they won't screw up somehow. > > > Thanks in advance guys! > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message >
signature.asc
Description: This is a digitally signed message part
