From owner-freebsd-questions@freebsd.org Sat Apr 16 15:08:43 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13321AEDBFB for ; Sat, 16 Apr 2016 15:08:43 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D03011128 for ; Sat, 16 Apr 2016 15:08:42 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-71-243.dynamic.qsc.de [92.195.71.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id D8A5C276E1; Sat, 16 Apr 2016 17:08:37 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u3GF8bOl002698; Sat, 16 Apr 2016 17:08:37 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 16 Apr 2016 17:08:37 +0200 From: Polytropon To: JosC Cc: "freebsd-questions@FreeBSD.org" Subject: Re: Ports upgrade script Message-Id: <20160416170837.81dddb26.freebsd@edvax.de> In-Reply-To: References: <2daca22c-7719-0776-fbe8-3c37021298bf@cloudzeeland.nl> <20160416122425.b603d040.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2016 15:08:43 -0000 On Sat, 16 Apr 2016 16:23:32 +0200, JosC wrote: > > In een bericht van 16-4-2016 12:24: > > Use either portsnap (binary upgrade) or svn (source upgrade) to keep > > your ports collection current. In your specific case, I'd probably be > > a good idea to entirely remove /usr/ports (or rename it) and start > > with a fresh copy, to be obtained by _one_ of the two methods. > Thanks for your suggestion - what I don't understand is why my /user/src > folder is emty. Terminology sidenote: The thing is called a directory, not "folder"; "folder" is the name of the graphical representation of a directory. :-) > Is that normal using portsnap? Yes. As the name _port_snap indicates, it only updates the ports collection, which is in /usr/ports. The /usr/src directory belongs to the OS and can be updated using freebsd-update, if you have the "src" component enabled in /etc/freebsd-update.conf (which is the default, if I remember correctly). Basically, freebsd-update can be used to update the kernel, the OS, and the /usr/src subtree. This directory could as well be updated using svn, but _then_ you'd have to build your system from that sources in order to upgrade it. As I said, starting with a clean /usr/src and then using either svn for it (and omitting "src" from the freebsd-update.conf settings) or freebsd-update (_with_ the "src" component). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...