From owner-freebsd-questions Wed May 30 10:48: 6 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7630C37B423 for ; Wed, 30 May 2001 10:48:03 -0700 (PDT) (envelope-from doug@safeport.com) Received: from localhost (doug@localhost) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f4UHlfg51454; Wed, 30 May 2001 13:47:41 -0400 (EDT) (envelope-from doug@safeport.com) X-Authentication-Warning: fledge.watson.org: doug owned process doing -bs Date: Wed, 30 May 2001 13:47:40 -0400 (EDT) From: Doug Denault X-Sender: doug@fledge.watson.org To: Don Dugger Cc: Bill Moran , freebsd-questions@FreeBSD.ORG Subject: Re: upgrades [each time more trouble] In-Reply-To: <3B1520FD.59D3A483@hotlz.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It updates the base system. This is a moving target as openssh and the crypto stuff has been added recently. It is that part of the system you would install from the CD excluding ports and package distributions such as XFree86. If you have a good network connection it works great. Until 4.3 you had to track stable, assuming you are not a developer. Stable has been "broken" once or twice in the past two years. While I think this is a pretty great track record, if you happen to get caught it, is a disaster of large proportions. To protect from this rare occurrence, I cvsup to a test machine and then update my network from that source tree. With 4.3 a security track has been added. There was a post (here or in announcements??) that detailed what is covered. The process itself is pretty simple, I use a process posted to stable by Paul Howes a while back. My version: On the client system(s) you will need to nfs-mount these file systems. mount -i nfs server:/usr/src /usr/src mount -i nfs server:/usr/obj /usr/obj Now, on the server you can do: make buildworld make buildkernel KERNCONF=client And on the client do: make installkernel KERNCONF=client make installworld mergemaster reboot You may also have a common ports source tree, just mount -i nfs server:/usr/ports /usr/ports On Wed, 30 May 2001, Don Dugger wrote: > I'll admit I've never tried cvsup, I've been meaning to look into it. > How mush of the system dose it update? > > Don 8) > [cut] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message