<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.6" -->
<rss version="0.92">
<channel>
	<title>FreeBSD ala Folsom</title>
	<link>http://blogs.freebsdish.org/gcooper</link>
	<description>Just another FreeBSD Committers Blogs weblog</description>
	<lastBuildDate>Sat, 14 Jul 2007 23:12:24 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Modifications to pkg_install &#8212; the positive and (slightly) negative implications</title>
		<description>Commentary:

What's being profiled:
In my simple profiling Perl scripts I count the number of iterations I see a given header tag, along with count the time reported by clock_gettime(3). I've placed simple printf's around the following subroutines/sections of code, as I believe they are critical (high number of iterations, large amount ...</description>
		<link>http://blogs.freebsdish.org/gcooper/2007/07/14/modifications-to-pkg_install-the-positive-and-negative-implications/</link>
			</item>
	<item>
		<title>The inefficiencies of pkgdb.db&#8230;</title>
		<description>Continuing on with my analysis of the Ruby tools, I find that pkgdb.db is really inefficiently mapping files to packages, and packages to origins.

In the given pkgdb.db I have (which is toy in comparison to my server and other desktops' pkgdb.db files -- only 25 installed packages), I am seeing ...</description>
		<link>http://blogs.freebsdish.org/gcooper/2007/05/20/the-inefficiencies-of-pkgdbdb/</link>
			</item>
	<item>
		<title>Behind INDEX-*.db</title>
		<description>Seizing the opportunity of having more free time from my internship, I've been able to unravel a bit more behind INDEX-*.db's format.

Based on the information dumped from MySQL 5.0.x's db_dump185 source, I can see that the Ruby generated the following formatted database:

:categories{Categories}
:db_version
[db specific version string]
:origins
{Package name
Package origin}
:pkgnames
{Package name
Package origin}
:virtual categories
{
{?Virtual ...</description>
		<link>http://blogs.freebsdish.org/gcooper/2007/05/19/behind-index-db/</link>
			</item>
	<item>
		<title>/usr/lib/libc/db/ and friends, and INDEX&#8217;es</title>
		<description>So, over the past couple days I've been looking over the db code under libc, trying to get a grasp on what needs to be done to get the packaging stuff up and running, and it turns out that my results have been fairly successful. In order to remain fully ...</description>
		<link>http://blogs.freebsdish.org/gcooper/2007/05/06/usrliblibcdb-and-friends-and-indexes/</link>
			</item>
	<item>
		<title>Work, work, and more work</title>
		<description>I apologize for the lack of info, but work at Intel is proving to be a bit challenging right now (pending internal tool release soon at the end of the financial Quarter).

I've looked at the internals of db.h, pkg_which, pkgdb, /usr/ports/INDEX-7* and played around with perforce a bit, but I ...</description>
		<link>http://blogs.freebsdish.org/gcooper/2007/04/25/4/</link>
			</item>
	<item>
		<title>First Post</title>
		<description>So, this is my first post to my FreeBSD blog. In here I'll discuss my triumphs, tribulations, and the entire learning process of my SoC 2007 project, of which it's comprised of several mini-projects:

	Revise FreeBSD's package tools (pkg_*) to use a BDB hash table backend.
	Write a common Bourne shell frontend ...</description>
		<link>http://blogs.freebsdish.org/gcooper/2007/04/16/first-post/</link>
			</item>
</channel>
</rss>
