Date: Thu, 31 Oct 2002 14:37:20 -0800 From: Steve Warwick <ukla@attbi.com> To: <freebsd-questions@FreeBSD.ORG> Subject: Re: Separating the OS from the data [Addendum] Message-ID: <B9E6F0A0.3B38%ukla@attbi.com> In-Reply-To: <3DC1AD20.1050304@cs.umu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
[Addendum] Cvsup / makeworld: I apologize for missing that piece of information Yes, I could use the usual update procedure, however, this is a production machine. So my thought is: build a new OS on a staging machine, add required symlinks, pull the drive (sled) and slot it into the production machine. In THEORY it should be possible to do an upgrade in the time it takes to do a reboot. For server farms this would be a big benefit... Steve >> -- Problem: >> Separating OS from underlying data. Which parts of the BSD OS are not part >> of the initial, never modified OS? Or, which pieces of the OS change due to >> useage. > > [...snip...] > > Not a direct answer to your question, as I assume you want to reformat > the disk for every new installation, but... > > The easiest way to upgrade the OS is by using cvsup. Then you'll get > the changes of the source files, and after you've cvsup'ed you just > compile the sources and install them. > > It's as easy as this... > > cvsup sources > make buildworld > make buildkernel KERNCONF=KERNEL > mergemaster -p > make installkernel > reboot > make installworld > mergemaster > reboot(?) > > (If I remember the steps correct) > > No need to reformat the disk, no need to recreate symbolic links and > all is updated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B9E6F0A0.3B38%ukla>