some gcc flags, 2009-09-08 00:00:00 #
This is how I compiled openldap once. It allowed me to have all the dependencies available when I tar-ed up the openldap dir and distributed it around. export LDFLAGS="-L/usr/lib/lwp/64 -L/lib/64 -L/usr/lib/64 -L/usr/sfw/lib/sparcv9 -Wl,-R/usr/lib/lwp/64 -Wl,-R/lib/64 -Wl,-R/usr/lib/64 -Wl,-R/usr/sfw/lib/sparcv9 -L/usr/local/openldap64-ol2.3.23-bdb4.2.52/lib -Wl,-R/usr/local/openldap64-ol2.3.23-bdb4.2.52/lib -m64" export CPPFLAGS="-I/usr/local/openldap64-ol2.3.23-bdb4.2.52/include" export CFLAGS="-m64 -O2"

tags: c,programming

cfengine3 added to pkgsrc wip, 2009-08-02 00:00:00 #
I created a cfengine3 package for wip. As my second package, this one was a lot easier to get up and running. :) There are, however, a lot of tricks to know about pkgsrc. For this guy I had to use: BUILDLINK_TRANSFORM+=l:db:db4 Which helped make sure I was using the pkgsrc bdb4 instead of the whatever else the system thought I had/was trying to use. I'm also trying to figure out how to get all the right stuff moved into /var/cfengine as the architecture of cfengine is a little wild.

tags: pkgsrc

pkgsrc addition - collectd, 2009-07-18 00:00:00 #
Today I committed to . This is significant because it's the first thing I've ever committed to pkgsrc-wip AND because collectd is a cool piece of software. (although it's still rapidly evolving) Basically, it's tool that can monitor stuff and record it to rrd or csv files. It can do this with an agent, over snmp, with a custom plugin, with a perl plugin, etc etc etc. The reason I like it is that it doesn't include a gui, require a database, or any of that other stuff. It's also why I like . The package itself is pretty immature. As you can image with such a flexible tool, there are a ton of optional plugins that should all be available through the pkgsrc options framework. They are not and I have just included a few things I thought were essentials. I left out ping, though, because liboping won't compile on NetBSD (or slightly older linux missing a few headers). The compile on NetBSD part is getting fixed by adding some socketopts, but liboping really needs some portability improvements before I can url2pkg it easily. FreeBSD has a port with some patches, so maybe it will just work. As an aside- My vision of a perfect monitoring system is very flexible. I prefer to have a wiki for my intranet, and creating the whole monitoring system inside of it; with graphs included on app docs for their required servers, and also on useful pages in templates of my design showing key stats.. I could go on for hours. :) (notifications every which way..) There are also some things I don't like about collectd. Mainly that it prefers agent-based operation and doesn't include a full UCD MIB for the snmp monitor. It would be ideal if they both collected the same data in the same way so you could migrate from snmp to agent without any issues. They're also evolving the threshold notifications framework, which is pretty important to have settled. The config file syntax is single-host centric. And I'm sure I could think of a few other things. :)

tags: NetBSD

NetBSD with wpa_supplicant and dhcpcd, 2009-07-13 00:00:00 #
So a long time ago, I started an email thread called wherein I shared a problem I had with dhcpcd being a part of /etc/rc.d/network since wpa_supplicant (required to get link on a protected interface) started after /etc/rc.d/network. It led to a lot of interesting talk as you can see on the thread, but not a lot of answers. :) Anyway, the following works just fine: which tells dhcpcd to background immediately and wait forever for a lease. Otherwise, it would exit when it didn't find link (status: no carrier) because wpa_supplicant hadn't started up and authenticated the link yet! I would still prefer to see something like /etc/rc.d/network2 which re-parses rc.conf for late flags per-interface, but this works for now especially since dhcpcd is the only thing that runs per-interface instead of through a control interface. These flags are also handy because if I say I want dhcp on an interface, I mean that I want it regardless of when I choose to plug in a network cable.

tags: NetBSD

new NetBSD security advisories AND crazy meta-blogging, 2009-06-23 00:00:00 #
Read the following for security issues: Then if you're reading this on you might have noticed that has been posting about parsing in reply to an trying to do the same thing. Crazy meta fun. :)

tags: NetBSD

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25