From owner-freebsd-questions@FreeBSD.ORG Mon Jul 21 00:54:49 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2C36DCDB for ; Mon, 21 Jul 2014 00:54:49 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E4E762F70 for ; Mon, 21 Jul 2014 00:54:48 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s6L0sk7Y091580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 20 Jul 2014 18:54:46 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s6L0sgu8091569; Sun, 20 Jul 2014 18:54:46 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 20 Jul 2014 18:54:42 -0600 (MDT) From: Warren Block To: Doug Hardie Subject: Re: Freebsd-update to 9.3 from 9.2 In-Reply-To: Message-ID: References: <4CA0146F-BD4E-4613-9050-DB0C1FDB7EA4@lafn.org> <53C8B7A2.1060504@my.hennepintech.edu> <494D0D9E-ED60-4187-ABCF-8E18CDEAB911@lafn.org> <53C8E2A7.6000000@my.hennepintech.edu> <7154054C-47D0-454C-8601-3F17095476EC@lafn.org> <066C2341-F26F-4817-B681-97119FB7EB7C@lafn.org> <0A5E66FF-D8B0-4619-91AC-C99BC2AEA04D@lafn.org> <0501F769-338A-4B23-AC7B-DBFC55C9387E@lafn.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 20 Jul 2014 18:54:46 -0600 (MDT) Cc: Andrew Berg , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2014 00:54:49 -0000 On Sun, 20 Jul 2014, Doug Hardie wrote: >> Is there anything else we can do to help make it more clear? I don't >> mean to put you on the spot, just that I've found these types of >> problems often can be used to make valuable improvements in the >> documentation. If you think of somewhere else it should be >> mentioned, or a better way to explain it, please let me or the >> freebsd-doc mailing list know. >> > > I would appreciate either examples or instructions with examples on > how to setup and properly update a system using svn. Those are the > most common things admins do if they are not involved in the > development of FreeBSD. There used to be some good info on that in > the handbook back when we used cvsup. Think more tutorial and less > man page constructs. If I knew enough about the process, I'd try > writing it, but so far most of the things I have tried have not > worked. Only one of the several systems I have tried to update to use > svn and pkg still works. pkg is not involved. I don't use binary packages, so someone else can address that. The problem with exact Subversion examples is there are numerous repositories and mirrors, so it's a factorial combination. And we (or at least, I) have found that giving specific examples means people will use those examples verbatim, even if there is a warning not to do so. So, keeping that in mind... Check out source for 10-stable from the western US mirror, first time only: # rm -rf /usr/src # svn checkout https://svn0.us-west.freebsd.org/base/stable/10 The first time, Subversion will ask to accept a security certificate fingerprint. These are shown in the Handbook Subversion appendix. To update that source later: # svn up /usr/src That's it. The process for ports is identical, just a different repository: # rm -rf /usr/ports # svn checkout https://svn0.us-west.freebsd.org/ports/head /usr/ports And then update periodically: # svn up /usr/ports The desire to avoid that repetition is why there is a generic Subversion appendix in the Handbook. Still, we have a lot of repetition of Subversion instructions elsewhere. There's a section in the Handbook. There's another in the Committer's Guide. There's another in the FDP Primer. Hence my idea to factor all that out and make our own Subversion for FreeBSD book. My outline for it already has separate sections for end-user usage for ports, source, and docs. However, it is one of many projects on the list.