Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Apr 2016 17:08:37 +0200
From:      Polytropon <>
To:        JosC <>
Cc:        "" <>
Subject:   Re: Ports upgrade script
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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).

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>