search for: portsnap

...w it's been the only option for keeping an up-to-date ports tree, and (thanks to all of the recent work on vuxml and portaudit) it has become quite obvious that keeping an up-to-date ports tree is very important. To provide a secure, lightweight, and fast alternative to CVSup, I've written portsnap. As the name suggests, this is a system for building, *signing*, and distributing compressed snapshots of the ports tree, which can then be extracted into /usr/ports as needed. Portsnap is: * Lightweight. It's a 15kB shell script which uses under 50kB of other binaries. * Designed for fr...

I''ve posted a FreeBSD portsnap class for those wanting to automate the use of portsnap for ports maintenance (fetch, extraction, cron, and update). http://reductivelabs.com/trac/puppet/wiki/PuppetFreeBSD#portsnap ## EXAMPLE import ''freebsd.pp'' import ''schedule.pp'' node ''freebsd...

Hello, Probably the wrong mailinglist. But portsnap is not updating since a few days while there are commits on the ports tree. [1] After some searching I found I am not the only one. Apparently there is maintenance being done on the servers. http://www.mail-archive.com/freebsd-ports at freebsd.org/msg45395.html I read a lot of blogs/RSS/etc....

Dear FreeBSD users, Slightly more than three years ago, I released FreeBSD Update, my first major contribution to FreeBSD. Since then, I have become a FreeBSD committer, joined the FreeBSD Security Team, released Portsnap, and become the FreeBSD Security Officer. However, as I have gone from being a graduate student at Oxford University -- busy writing my thesis -- to a researcher at Simon Fraser University -- busy doing research and writing papers -- my "to do" list of FreeBSD-related work has continued...

I have been using Freebsd for along time. I have a client of mine that wants me to use Centos for his email server and web server. Anyway with Freebsd to update the packages file you use the following commands. portsnap fetch fetches all the current port trees portsnap update adds all the new ports to the tree on the server portupgrade -arR will install all the ports that are installed on the server. Now my question is what are the commands for Centos to fetch ,update and install, all the packages installed...

...gt; > Content-Type: text/plain; charset=ISO-8859-1 > > Dear FreeBSD users, > > Slightly more than three years ago, I released FreeBSD Update, my first > major contribution to FreeBSD. Since then, I have become a FreeBSD > committer, joined the FreeBSD Security Team, released Portsnap, and > become the FreeBSD Security Officer. However, as I have gone from > being a graduate student at Oxford University -- busy writing my thesis > -- to a researcher at Simon Fraser University -- busy doing research > and writing papers -- my "to do" list of FreeBSD-related...

Hello, I'm experiencing a kernel panic that appears to be caused by zfs. No errors are making it into /var/log/messages, but here is the error message that appears on my screen after panic (transcribed): panic solaris assert BSWAP_32(sa_hdr_phys->sa_magic) == SA_MAGIC, file: /src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c, line 1262 I can reproduce this by

We are currently using cvs for both source and ports. I have begun changing to portsnap for ports, and I would also like to try changing at least some of our servers to freebsd-update. But all servers have been patched, using either RELENG_8_3 or RELENG_9_0 as cvs tag. I need to revert them to their respective RELEASE to be able to use freebsd-update. Complete reinstall from eg CD is...

Dear members, It may sound a silly question. I have curl installed: # pkg_info |grep curl curl-7.24.0_3 Non-interactive tool to get files from FTP, GOPHER, HTTP(S) Today portsnap updated the ftp/curl port, and patch-CVE-2013-2174 appeared in files/, but the port version remained such that portaudit, and portupgrade still complain about curl's version. What is the recommended way to upgrade the package? # portupgrade curl-7.24.0_3 ---> Upgrading 'curl-7.24.0_...

Hi list, after the security announcement (http://www.freebsd.org/news/2012-compromise.html) I use svn to update my local ports tree. I've found out that the port index is not updated. What is the preferred/recommended way to update port indexes when using svn? Thanks, Serguey.

Hi all, I have update recently to freebsd 9.1 via freebsd-update and I was quite happy with the process and the instructions on freebsd-handbook, I think well documented. But I would like to understand what is the best practice to update the ports too as I used the package tools (pkg_add -r) to add few package to the base install. Keeping in mind my server have disk space constrain (small disk

I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to install dovecot 2.2.31_1 I run portsnap fetch update daily, and I ran it again after this error, but same result. ===> Installing for dovecot2-2.2.31_1 ===> Checking if dovecot2 already installed ===> Registering installation for dovecot2-2.2.31_1 as automatic Installing dovecot2-2.2.31_1... pkg-static: dovecot2-2.2.31_1 co...

...ory will now build SSP by default as well. SSP is "Stack Smashing Protection" and can be read about at https://en.wikipedia.org/wiki/Buffer_overflow_protection. This only applies to the head (/latest) packages, not the Quarterly branch packages. This applies to the ports checkout that portsnap uses. WITHOUT_SSP can be defined in make.conf to not use this feature. SSP will be used to build ports (with -fstack-protector) on all amd64 releases and i386 releases which are 10.0 or newer. The "ssp" repository and "new_xorg" repositories will no longer be updated after...

...ory will now build SSP by default as well. SSP is "Stack Smashing Protection" and can be read about at https://en.wikipedia.org/wiki/Buffer_overflow_protection. This only applies to the head (/latest) packages, not the Quarterly branch packages. This applies to the ports checkout that portsnap uses. WITHOUT_SSP can be defined in make.conf to not use this feature. SSP will be used to build ports (with -fstack-protector) on all amd64 releases and i386 releases which are 10.0 or newer. The "ssp" repository and "new_xorg" repositories will no longer be updated after...

...ory will now build SSP by default as well. SSP is "Stack Smashing Protection" and can be read about at https://en.wikipedia.org/wiki/Buffer_overflow_protection. This only applies to the head (/latest) packages, not the Quarterly branch packages. This applies to the ports checkout that portsnap uses. WITHOUT_SSP can be defined in make.conf to not use this feature. SSP will be used to build ports (with -fstack-protector) on all amd64 releases and i386 releases which are 10.0 or newer. The "ssp" repository and "new_xorg" repositories will no longer be updated after...

...time support for running software from the ports tree on FreeBSD 5.x is also ceasing: Packages for binary installations will no longer be built for FreeBSD 5.5, building ports from source on FreeBSD 5.x will no longer be supported, and the ports INDEX will no longer be built and made available via portsnap or the 'make fetchindex' target. Patches for individual ports specific for their functioning on FreeBSD 5.5 may still be accepted at the discretion of the port maintainer. [Excerpt from http://security.freebsd.org/ follows] FreeBSD Security Advisories The FreeBSD Security Officer pro...

...time support for running software from the ports tree on FreeBSD 5.x is also ceasing: Packages for binary installations will no longer be built for FreeBSD 5.5, building ports from source on FreeBSD 5.x will no longer be supported, and the ports INDEX will no longer be built and made available via portsnap or the 'make fetchindex' target. Patches for individual ports specific for their functioning on FreeBSD 5.5 may still be accepted at the discretion of the port maintainer. [Excerpt from http://security.freebsd.org/ follows] FreeBSD Security Advisories The FreeBSD Security Officer pro...

...time support for running software from the ports tree on FreeBSD 5.x is also ceasing: Packages for binary installations will no longer be built for FreeBSD 5.5, building ports from source on FreeBSD 5.x will no longer be supported, and the ports INDEX will no longer be built and made available via portsnap or the 'make fetchindex' target. Patches for individual ports specific for their functioning on FreeBSD 5.5 may still be accepted at the discretion of the port maintainer. [Excerpt from http://security.freebsd.org/ follows] FreeBSD Security Advisories The FreeBSD Security Officer pro...

...s point, support for running software from the ports tree on FreeBSD 4.x is ceasing: Packages for binary installations will no longer be built for FreeBSD 4.11, building ports from source on FreeBSD 4.x will no longer be supported, and the ports INDEX will no longer be built and made available via portsnap or the 'make fetchindex' target. Patches for individual ports specific for their functioning on FreeBSD 4.11 may still be accepted at the discretion of the port maintainer. [Excerpt from http://security.freebsd.org/ follows] FreeBSD Security Advisories The FreeBSD Security Officer pro...

Hi, I am running an environment with 15 FreeBSD servers on which I want to maintain ports, rc.conf settings, and assorted configuration in /usr/local/etc/. Looked around the existing Puppet docs, I got a puppetmaster and a test client to work and install a package as specified in the site manifest. This is very basic but awesome! I want to create a puppet FreeBSD HowTo that addresses a