Date: Fri, 10 Aug 2001 00:12:13 -0400 From: "Tom Gottheil" <tom@gottheil.com> To: "alexus" <ml@db.nexgen.com> Cc: <freebsd-security@FreeBSD.ORG> Subject: Re: RELEASE 4.3 -> RELENG_4_3: SUCCESSFULLY but ... Message-ID: <000a01c12152$a32b66d0$0200a8c0@humbaba> References: <Pine.BSF.4.33.0108092234470.33832-100000@cloud9.pain.net> <002501c1214d$07a5cf70$0100a8c0@alexus>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, nobody has to, it's just more fun that way... Mostly you can get bug fixes and such, but as has been repeatedly discussed (and then a bit more), -STABLE is not necessarily "stable". (No, I'm not trying to start anything again...) Mostly people who cvsup that frequenly are developers or at least interested in the cutting edge (then there's current...) ----- Original Message ----- From: "alexus" <ml@db.nexgen.com> To: "erb" <erb@cloud9.pain.net>; "Jim Durham" <durham@w2xo.pgh.pa.us> Cc: "Josef Karthauser" <joe@tao.org.uk>; "Nuno Teixeira" <nuno.mailinglists@pt-quorum.com>; <freebsd-security@FreeBSD.ORG> Sent: Thursday, August 09, 2001 11:32 PM Subject: Re: RELEASE 4.3 -> RELENG_4_3: SUCCESSFULLY but ... > i'm more or less newbie here > > can you explain me why would you ever want to > > do cvsup+rebuild kernel every friday? what's wrong with your old kernel? > > ----- Original Message ----- > From: "erb" <erb@cloud9.pain.net> > To: "Jim Durham" <durham@w2xo.pgh.pa.us> > Cc: "Josef Karthauser" <joe@tao.org.uk>; "Nuno Teixeira" > <nuno.mailinglists@pt-quorum.com>; <freebsd-security@FreeBSD.ORG> > Sent: Thursday, August 09, 2001 10:40 PM > Subject: Re: RELEASE 4.3 -> RELENG_4_3: SUCCESSFULLY but ... > > > > Hmm.. I only update the 'world' if I am changing something that requires > > it, other then that I use a crontab entry that looks similiar to this.. > > > > #run cvsup every week at 2:30 AM (Friday) + compile/install new kernel > > 30 2 * * 5 root newkernel > > > > and the newkernel script is as follows.. > > > > #!/bin/sh > > # New kernel script, will cvsup, configure, compiling and install > > # new kernel from source. -erb > > # > > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin > > export PATH > > cvsup -g -L 2 /etc/supfile >/var/tmp/cvsup.out 2>&1 > > cd /usr/src/sys/i386/conf > > config CLOUD9 >/var/tmp/config.out 2>&1 > > cd /usr/src > > make update >/var/tmp/update.out 2>&1 > > #make buildworld >/var/tmp/buildworld.out 2>&1 > > #make installworld >/var/tmp/installworld.out 2>&1 > > make buildkernel KERNCONF=CLOUD9 >/var/tmp/buildkernel.out 2>&1 > > make installkernel KERNCONF=CLOUD9 >/var/tmp/installkernel.out 2>&1 > > echo "CVSUp, & Kernel compile/install completed. For more information > > referr to /var/tmp and browse through the .out files." | mail -s "cvsup & > kernel compile completed" sysadmin@cloud9.pain.net > > > > seems to do the trick just fine, could anyone let me know if this is a bad > > idea? > > > > On Thu, 9 Aug 2001, Jim Durham wrote: > > > > > On Wed, 1 Aug 2001, Josef Karthauser wrote: > > > > > > > On Wed, Aug 01, 2001 at 10:01:41PM +0100, Nuno Teixeira wrote: > > > > > > > > > My question is: what is the real danger of doing `installworld` in > > > > > multiuser mode? I have doing a lot of tests in other machines > tracking > > > > > STABLE and I have no problems so far. > > > > > > > > I've _always_ done installworld in multiuser on many servers. That > > > > doesn't mean that it's the safest way, but it was safe enough for me. > > > > > > > > Joe > > > > > > > > > > Well, I got talked into trying this and it panic'd the running > > > kernel, so I won't do it that way again! I know lots of folks have > > > gotten away with this, but it seems to be Russian Roulette.. > > > > > > I now have a "boot.config" file with "-h" in it and a null modem > > > cable to my portmaster. I reboot into single-user, telnet into > > > the portmaster and get on the serial port. Works very well. > > > You could also cross-connect serial ports from another server. > > > > > > -Jim Durham > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-security" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-security" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000a01c12152$a32b66d0$0200a8c0>