similar to: FreeBSD portsnap class...

I just drudged through a bit of the archives and see a FreeBSD bits floating in there that are of some value, but aren''t on the wiki. I posted a few bits on the wiki regarding some FreeBSD cobbling that I''ve done recently and hope that folk find it of use (and start posting their useful bits there as well). http://reductivelabs.com/trac/puppet/wiki/PuppetFreeBSD The

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. Nowhere any signs of maintenance on the

freebsd-security-request@freebsd.org wrote: > Send freebsd-security mailing list submissions to > freebsd-security@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-security > or, via email, send a message with subject or body 'help' to > freebsd-security-request@freebsd.org > > You

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

Hello, It appears that the FreeBSD port of Samba 3.0.x may be falling behind. The port maintainter does not use Winbind and thus has not kept up with the development of it. 3.0.1 will very shortly be ported to FreeBSD, currently it is still at 3.0.0. I know there have been some recent changes to Samba that help FreeBSD out, and I wanted to make sure that the port of Samba 3.0.x on FreeBSD stays

I just upgraded the FreeBSD buildbot machine from 6.4 to 8.0, and I ran across some interesting differences. The libusb API that we use (0.1) is available in /usr/include/usb.h and /usr/lib/libusb.* as before, but it seems to be the compatibility layer from libusb 1.0. However, it doesn't include the libusb-config binary. This is from the 'ports' Makefile for NUT: ########## - -

CVSup is slow, insecure, and a memory hog. However, until now 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

Puppet 3.0.1 is a bugfix release for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328. This release contains contributions from the following people: Andrew Parker, Jeff McCune, Josh Cooper, Matthaus Owens, Moses Mendoza, Nick Fagerlund, Niels Abspoel, Patrick

We''re back with a maintenance release: 2.6.5. This release addresses a number of bugs in the 2.6.x branch and adds a handful of features and documentation updates. This release candidate contains fixes for bugs identified in the previous release candidates: - rc1 caused a warning on Ruby 1.8.6 which could cause log pollution. This release candidate no longer generates the warning. - rc1

This release addresses issues with the Puppet 2.7.0rc3 series. This release is available for download at: <http://goog_1305397870/> http://www.puppetlabs.com/downloads/puppet/puppet-2.7.0rc4.tar.gz See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected

Puppet 3.0.1-rc1 is a bugfix release candidate for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328 Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.1-rc1.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available

We''re back with a maintenance release: 2.6.5. This release addresses a number of bugs in the 2.6.x branch. 2.6.5 is a maintenance release in the 2.6.x branch and it contains only bug fixes, documentation updates and a small handful of features. The first release candidate is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.5-rc1.tar.gz We''re

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://security.freebsd.org/ >. FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 have `expired' and are no longer supported effective June 1, 2008. Users of these releases are

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://security.freebsd.org/ >. FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 have `expired' and are no longer supported effective June 1, 2008. Users of these releases are

----- Forwarded message from Nick Lewis <nick@puppetlabs.com> ----- Date: Thu, 3 Feb 2011 21:59:10 -0800 From: Nick Lewis <nick@puppetlabs.com> To: puppet-users@googlegroups.com, puppet-dev@googlegroups.com Subject: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 1 available! Message-ID: <AANLkTikjFwZ98P_NcxF54zHbU2mJf15XDrLg2cMp2GWT@mail.gmail.com> We''re back

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at <URL: http://security.freebsd.org/ >. FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 have `expired' and are no longer supported effective June 1, 2008. Users of these releases are

Using OpenSSL, is there a preferred/recommended rate of rekeying an encrypted stream of data? Does OpenSSL handle this for developers behind the scenes? Does it even need to be rekeyed? Thanks in advance. -sc -- Sean Chittenden -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 202 bytes Desc: not available

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

On Wed, Mar 01, 2023 at 06:43:11PM +0100, Laszlo Ersek wrote: > On 3/1/23 17:54, Eric Blake wrote: > > I took the easy route of crippling what I couldn't get working, on the > > grounds that partial coverage is better than none now that we have > > Cirrus CI checking commits on additional platforms. > > > > This series got me to a green checkmark: > >

Alright, well it's apparently no surprise to folks that ATA tag queuing is broken at the moment. Are there any objections to me adding a few cautious words to ata(4) and tuning(7) that advise _against_ the use of ata tag queuing given that they're likely the fastest way to reboot a -STABLE box? Here's a PR that I tacked a tad bit of info into: