search for: portinstallation

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

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

Hi. I have installed php5 with support for postgresql (php5-pgsql). If I install postgresql-client ver. 8.2.7 or 8.3.x apache (httpd) core-dumps. If I install postgresql-client 8.1.11 or 8.2.6 apache does not core-dump. This is the output (backtrace) from gdb: (gdb) bt #0 0x000000080651c340 in ?? () #1 0x000000080094ebd5 in puts () from /lib/libc.so.7 #2 0x000000080094f1ee in gethostbyname

I''d like to clarify some points about the ports/package system in FreeBSD. I apoligize ahead of time if this is Both packages and ports use the pkgdb system. This isn''t some lame cludge; it''s by design, and the reason is really quite simple. Packages are built from the ports collection. The only real difference between them is the mode of delivery. When you run

hi, i''ve run into somewhat of a snag with my puppet instances: when i try to have puppet install a port via portupgrade, it seems to step up each version in ports to the latest, if there are multiple versions. i''ve run into this with two ports so far: vim and postfix. my package line is: package { postfix: ensure => latest } i am however able to specify the version

Hi again, From examples I have gleaned the following snippet for manifests/site.pp Package { provider => $operatingsystem ? { FreeBSD => freebsd, #FreeBSD => ports, debian => aptitude, redhat => up2date }} Are there providers documented somewhere? I''m not sure where to look, and I haven''t come across it in my

does anybody have the same problem as I have : (running CURRENT, but the problem occurs on STABLE too) latest portupgrade, ports cvsuped today. fully reproductible with any package... am i missing something ? i hope yes... portinstall -PP teTeX ---> Checking the availability of the latest package of 'print/teTeX' ---> Fetching the package(s) for 'teTeX-2.0.2_2'

Hello :-) After days of problem with my system storage (?) I think I have located the issue, or at least I am able to reproduce it, please take a look at attached picture (photo of a crash). http://i45.tinypic.com/23qtcx.jpg At first I thought that was the Ext2 filesystem issue, but then I have replaced the filesystem to UFS2-SU+J (which increased transfer efficiency and dramatically reduced

Hi, I just installed dovecot. The installation went well and i configured dovecot to user ~/Maildir. When I tested imap via telnet the login work, but right after that the connection is cutted: Trying 192.168.0.14... Connected to op. Escape character is '^]'. * OK dovecot ready. . login jerik password . OK Logged in. Connection closed by foreign host. And the log says: dovecot:

The gnome2 port is broken? I updated the ports tree two time today, but the result is: rss@DaeMoN:/usr/ports/x11/gnome2> sudo make install clean ===> Installing for gnome2-2.4.0 ===> gnome2-2.4.0 depends on file: /usr/X11R6/libexec/cdplayer_applet2 - found ===> gnome2-2.4.0 depends on executable: gnome-cd - found ===> gnome2-2.4.0 depends on executable: gnome-dictionary -

Hello, I am running a puppet master version 2.7.5 on Centos 5.7 and a puppet agent version 2.7.5. I am simply trying to apply changes to files by defining a file resource in my manifest. When I execute my puppet agent to do the installation it complains it can not find the file meta data. Here is my manifest. class neospeech::config { file { "/usr/vwmrcpd/vwmrcpd/vwmrcpd":

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Dear FreeBSD users and system administrators, While the FreeBSD Security Team has traditionally been very good at investigating and responding to security issues in FreeBSD, this only solves half of the security problem: Unless users and administrators of FreeBSD systems apply the security patches provided, the advisories issued accomplish little beyond alerting potential attackers to the

In http://www.freebsd.org/releases/7.0R/announce.html says Updating Existing Systems > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes > a major version upgrade, so no matter which method you use to update > an older system you should reinstall any ports you have installed on > the machine. This will avoid binaries becoming linked to inconsistent > sets