Date: Tue, 10 Apr 2001 17:36:20 -0400 (EDT) From: FreeBSD Admin <fbsd@mohawk.net> To: freebsd-stable@FreeBSD.ORG Subject: how to track stable Message-ID: <Pine.BSF.4.21.0104101726230.69556-100000@mohegan.mohawk.net>
next in thread | raw e-mail | index | archive | help
For years now I have been running FreeBSD machines (since 2.0.5) but I never bothered tracking stable. I would watch for security advisories and decide if I needed to upgrade some executable. Eventually, I would backup the user content and reload from scratch to get a new release (generally by x.2). That worked for me okay, but now, with many many machines to deal with, I thought I should probably learn to track stable. Please bear with me. I have tried to understand this process, but still it is not clear to me. I have read http://www.freebsd.org/handbook/current-stable.html http://www.freebsd.org/handbook/synching.html http://www.freebsd.org/handbook/makeworld.html http://www.freebsd.org/handbook/anoncvs.html http://www.freebsd.org/handbook/cvsup.html and other docs, but I find it confusing for some reason. Maybe I'm slightly out to lunch or something, but it seems more complicated than I imagine it really is. Can someone point me to a clear step-by-step explanation of how to do this? I have cvsup'd the stable sources and the ports, but now what? Do I have to rebuild everything? There's a lot of stuff we never use. Does everything have to be done? Perhaps this is right under my nose. If so, I apologize and thank you for setting me right. Thanks in advance for any pointers about tracking stable. Thanks again. - Ralph 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?Pine.BSF.4.21.0104101726230.69556-100000>