<?xml version="1.0"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:res="http://blogreen.org/TR/Resources" xmlns:bgn="http://blogreen.org" bgn:template-name="rss" version="2.0"><channel><title>FreeBSD</title><link>https://romain.blogreen.org/categories/freebsd/</link><description>An advanced operating system for modern server, desktop, and embedded computer platforms.</description><link xmlns="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="https://romain.blogreen.org/categories/freebsd/rss-short.xml"/><item><title>Contributions to Free Software in 2025</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">
            Three years ago, I started working on
            <a href="https://github.com/smortex/wtr"><tt>wtr(1)</tt></a>
            (Work Time Recorder), a time tracking system that complies with my intolerance to toil but allows me to track the time spent on projects for work (as one would expect) and for fun (as one might not have expected).
            Time tracking happening without me having to think about it, I try to track all "major" projects or at least each "organization" I am involved in in my contributions to Free Software.
          </p><p xmlns="http://www.w3.org/1999/xhtml">
            I now have 2 full years of metrics, and so can compare them and maybe learn a few things!  First, let's see a fancy graph similar to the one produced by GitHub for my overall activity over 2024 and 2025:
          </p><p xmlns="http://www.w3.org/1999/xhtml" class="figure">
            <img src="/images/wtr-graph-last-2-years-by-year.png" alt=""/>
          </p><p xmlns="http://www.w3.org/1999/xhtml">
            Beside showing obvious periods of vacations, this view provide a few interesting metrics:
          </p><ul xmlns="http://www.w3.org/1999/xhtml">
            <li>The <em>number of days</em> with/without activity recorded for the full date range (578/731);</li>
            <li>The <em>median duration</em> of activity recorded by day (9:16:15)</li>
            <li>The <em>total duration</em> of activity recorded for the full date range (223 days 17:43:32)</li>
          </ul>]]></description><link>https://romain.blogreen.org/blog/2026/01/contributions-to-free-software-in-2025/</link><category>FreeBSD</category><category>Sysadmin</category><category>The Real Life</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2026/01/contributions-to-free-software-in-2025/</guid><pubDate>Mon, 12 Jan 2026 13:00:00 GMT</pubDate></item><item><title>Call For Testers: Puppet 5 ports on FreeBSD</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">
            Lately, I have been working on bringing Pupept 5 to FreeBSD.  For now, this effort is avialable through a set of ports on GitHub:<br/>
            <a href="https://github.com/smortex/puppet5">https://github.com/smortex/puppet5</a>
          </p><p xmlns="http://www.w3.org/1999/xhtml">
            The following article describes how I used this ports to update to Puppet 5.  If you try to update, please tell me if you succeeded or failed, and how to improve this!
          </p>]]></description><link>https://romain.blogreen.org/blog/2017/07/call-for-testers-puppet-5-ports-on-freebsd/</link><category>Sysadmin</category><category>FreeBSD</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2017/07/call-for-testers-puppet-5-ports-on-freebsd/</guid><pubDate>Mon, 10 Jul 2017 18:00:00 GMT</pubDate></item><item><title>Patching screens EDID information</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">Quite a long time ago (September 2012), the <a href="http://www.freshports.org/x11/nvidia-driver/">x11/nvidia-driver</a> port was updated to 304.43, which brought-in some major changes.  The most noticeable one from my point of view was the inability to use my two <em>Samsung SyncMaster BX2240</em> monitors at a resolution better than 800x600 (they have a native resolution of 1920x1080), providing a stunning 1600x600 desktop experience.  With no time to dig-in this at that time, I reverted to the previous nvidia-driver and planned to have a look at it <em>later</em>.</p><p xmlns="http://www.w3.org/1999/xhtml">I finally took the time to search for a solution.  I post it here for two reasons: a) I might need this information at some point in the future and am more likely to find it that way and b) I might not be the only one here which faced this situation.</p><p xmlns="http://www.w3.org/1999/xhtml">The first step was to modify my Xorg configuration to be a bit more verbose about the process of choosing a screen resolution when X starts to see if something was different with both drivers.  This can be achieved by editing the <em>Monitor</em> section:</p><pre xmlns="http://www.w3.org/1999/xhtml">Section "Monitor"
    ...
    Option "ModeDebug" "TRUE"
EndSection</pre>]]></description><link>https://romain.blogreen.org/blog/2013/02/patching-screens-edid-information/</link><category>FreeBSD</category><category>Sysadmin</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2013/02/patching-screens-edid-information/</guid><pubDate>Thu, 07 Feb 2013 10:42:37 GMT</pubDate></item><item><title>TeXLive 2012 on FreeBSD</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">Two months ago (August 2nd, 2012), I <a href="http://code.google.com/p/freebsd-texlive/source/detail?r=700">updated</a> the <a href="https://code.google.com/p/freebsd-texlive/">freebsd-texlive project</a> to provide TeXLive 2012 to the <a href="http://www.FreeBSD.org">FreeBSD</a> community.</p><p xmlns="http://www.w3.org/1999/xhtml">More recently (October 1st, 2012), I made major changes in the freebsd-texlive project to fix the long-standing problem of TeXLive shipping distfiles with no version in the filename and replacing them in place.  After <a href="http://texlive-distfiles.blogreen.org/">setting up a new mirror with renamed distfiles</a> (sponsored by <a href="http://www.nfrance.com/">NFrance</a>, a French hosting company using the FreeBSD operating system.  Many thanks to them for providing hosting and bandwidth!), <a href="http://code.google.com/p/freebsd-texlive/source/detail?r=758#">updating the program that creates and updates ports</a>, <a href="http://code.google.com/p/freebsd-texlive/source/detail?r=759#">updating the updating tools</a>, <a href="http://code.google.com/p/freebsd-texlive/source/detail?r=760#">switching to the new mirror</a> and <a href="http://code.google.com/p/freebsd-texlive/source/detail?r=761#">updating all ~2250 ports</a>; all the caveats around this choice from the maintainers of the TeXLive distribution should be gone!</p><p xmlns="http://www.w3.org/1999/xhtml">This change will however not be without consequences for users.  Distfiles version numbers where created by using the date at which a file appeared or where updated on the upstream mirrors, but because of the mirroring delays, the file <tt>mtime</tt> could be earlier by more than one day.  As a consequence, a file updated on 17th May, 2012 could have version number <tt>2012051<strong>8</strong></tt> (getting the <em>real</em> package version number in the distfile is a <acronym title="Pain In The Ass">PITA</acronym>).  Because having the version in the distfile filename require consistent dates, the new ports use the date from the upstream distfile <tt>mtime</tt>, and many ports had their version going backwards…  <tt>PORTEPOCH</tt> have so been bumped, and port management tools will want to update all these ports which are in fact unchanged.</p><p xmlns="http://www.w3.org/1999/xhtml">It's the first time such a bad situation happen in the freebsd-texlive repository.  I hope this will be the last and apologies to users who will be worried with this massive update.</p><p xmlns="http://www.w3.org/1999/xhtml">Happy TeXing!</p>]]></description><link>https://romain.blogreen.org/blog/2012/10/texlive-2012-on-freebsd/</link><category>FreeBSD</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2012/10/texlive-2012-on-freebsd/</guid><pubDate>Thu, 04 Oct 2012 11:11:26 GMT</pubDate></item><item><title>Book Review: FreeBSD Device Drivers</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">
Joseph Kong strikes again!  When I saw <a href="http://nostarch.com/rootkits.htm">Designing BSD Rootkits</a> I was quite
excited because:
</p><ol xmlns="http://www.w3.org/1999/xhtml">
            <li>it was on some topics I had interests in but had not as much time as I would have liked to to dig in;</li>
            <li>it was focussed on my main operating system.</li>
          </ol><p xmlns="http://www.w3.org/1999/xhtml">I bought the book and although it was rather small (~140 pages) enjoyed learning quite a large amount of things about the FreeBSD kernel.</p><p xmlns="http://www.w3.org/1999/xhtml">So, when I was contacted by <a href="http://nostarch.com/">No Stash Press</a> to know if I would be interested in a review copy of their upcoming book <a href="http://nostarch.com/bsddrivers">FreeBSD Device Drivers</a> by the same author in exchange of writing what I though about it, I had no hesitation and accepted the deal.</p><p xmlns="http://www.w3.org/1999/xhtml" class="figure">
            <img src="https://romain.blogreen.org/images/freebsd_device_drivers.png" alt="Book cover" width="169" height="225"/>
          </p>]]></description><link>https://romain.blogreen.org/blog/2012/07/book-review-freebsd-device-drivers/</link><category>FreeBSD</category><category>Sysadmin</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2012/07/book-review-freebsd-device-drivers/</guid><pubDate>Wed, 27 Jun 2012 20:10:24 GMT</pubDate></item><item><title>Updating a ZFS Mirror</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">A few days ago, while I was on the phone, my machine experienced a kernel panic.  The backtrace pointed a problem somewhere in the swap management code.  I was on a hurry at that time and rebooted the machine without taking the time dig in the problem deeper.</p><p xmlns="http://www.w3.org/1999/xhtml">On the next day, I eventually realised that an hard disk was logically missing on the system and the ZFS mirror it was belonging to was working in a degraded mode.  This disk holding a swap partition, the panic quite makes sense: some data was stored there and could not be paged-out anymore.</p><pre xmlns="http://www.w3.org/1999/xhtml" class="highlight-keyword"># zpool list
NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
data   294G  68,2G   226G    23%  1.25x  <strong>DEGRADED</strong>  -
tank  1,81T   300G  1,52T    16%  1.06x  ONLINE  -</pre><pre xmlns="http://www.w3.org/1999/xhtml" class="highlight-keyword"># zpool status data
  pool: data
 state: <strong>DEGRADED</strong>
<strong>status: One or more devices could not be opened.  Sufficient replicas exist for
        the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
   see: http://www.sun.com/msg/ZFS-8000-2Q</strong>
  scan: none requested
config:

NAME                                            STATE     READ WRITE CKSUM
data                                            DEGRADED     0     0     0
  mirror-0                                      DEGRADED     0     0     0
    gptid/36711e52-a69e-11de-8adf-0018f38af467  ONLINE       0     0     0
    15152536002702365387                        <strong>UNAVAIL</strong>      0     0     0  <strong>was /dev/gptid/602da1ae-c474-11de-960d-0008a14dbca1</strong>

errors: No known data errors</pre>]]></description><link>https://romain.blogreen.org/blog/2012/01/updating-a-zfs-mirror/</link><category>FreeBSD</category><category>Sysadmin</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2012/01/updating-a-zfs-mirror/</guid><pubDate>Wed, 04 Jan 2012 11:27:08 GMT</pubDate></item><item><title>TeXLive 2011 on FreeBSD</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">A few weeks ago, I updated the <a href="https://code.google.com/p/freebsd-texlive/">freebsd-texlive project</a> to make TeXLive 2011 (the latest verison) available as ports for <a href="http://www.freebsd.org/">FreeBSD</a>.</p><p xmlns="http://www.w3.org/1999/xhtml">In order to help users who don't want to install the whole TeXLive collection (~2000 ports), <a href="http://freebsd-texlive.googlecode.com/svn/trunk/Tools/scripts/texlive-port-seek">a basic script</a> has been developed to ease-up finding which port provides some file required by a given package.</p><p xmlns="http://www.w3.org/1999/xhtml">As usual, feedback is welcomed!</p>]]></description><link>https://romain.blogreen.org/blog/2011/08/texlive-2011-on-freebsd/</link><category>FreeBSD</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2011/08/texlive-2011-on-freebsd/</guid><pubDate>Fri, 26 Aug 2011 02:10:00 GMT</pubDate></item><item><title>Typesetting Korean with TeXLive</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">Today, I received a request for <a href="http://code.google.com/p/freebsd-texlive/issues/detail?id=15">adding support for ko.teX to the FreeBSD TeXLive ports</a>. I created 3 ports for this purpose: <a href="http://freebsd-texlive.googlecode.com/svn/branches/ports/print/kotex-util/">print/kotex-util</a>, <a href="http://freebsd-texlive.googlecode.com/svn/branches/ports/print/kotex-macros/">print/kotex-macros</a> and <a href="http://freebsd-texlive.googlecode.com/svn/branches/ports/print/kotex-fonts-all/">kotex-fonts-all</a>.</p><p xmlns="http://www.w3.org/1999/xhtml">I did some basic testing locally, but I don't read Korean, thus I could not test beyond the (minimalistic) examples. I am therefore looking for FreeBSD TeXLive users who are able to write Korean to help testing this package.  If you are one of them, please give it a try and report any success or failures <a href="http://code.google.com/p/freebsd-texlive/issues/detail?id=15">on the issue page</a>.</p>]]></description><link>https://romain.blogreen.org/blog/2011/02/typesetting-korean-with-texlive/</link><category>FreeBSD</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2011/02/typesetting-korean-with-texlive/</guid><pubDate>Sun, 06 Feb 2011 12:13:31 GMT</pubDate></item><item><title>TeXLive 2010 on FreeBSD</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">I definitively have a lack of time at the moment.  Since this blog last entry is about <q>Hey guys, I have just pushed TeXLive 2009 in the <a href="http://code.google.com/p/freebsd-texlive/">freebsd-texlive</a> project</q>, I guess I have to take the time to write this short post:</p><p xmlns="http://www.w3.org/1999/xhtml">One month ago, I pushed TeXLive 2010 to the <a href="http://code.google.com/p/freebsd-texlive/">freebsd-texlive</a> repository.  Moreover, because <a href="http://www.freshports.org/ports-mgmt/portshaker/">portshaker</a> is now in the FreeBSD ports tree, <a href="http://code.google.com/p/freebsd-texlive/wiki/Installing">installing bleeding-edge TeXLive on FreeBSD</a> has never been so easy!</p>]]></description><link>https://romain.blogreen.org/blog/2010/11/texlive-2010-on-freebsd/</link><category>FreeBSD</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2010/11/texlive-2010-on-freebsd/</guid><pubDate>Mon, 01 Nov 2010 12:13:31 GMT</pubDate></item><item><title>TeXLive 2009 on FreeBSD</title><description><![CDATA[<p xmlns="http://www.w3.org/1999/xhtml">I recently updated the <a href="https://code.google.com/p/freebsd-texlive/">freebsd-texlive project</a> to make TeXLive 2009 (the latest verison) available as ports for <a href="http://www.freebsd.org/">FreeBSD</a>.</p><p xmlns="http://www.w3.org/1999/xhtml">I used <a href="https://romain.blogreen.org/blog/2009/05/texlive-for-freebsd-updated/">a script for update TeXLive 2008 on a regular basis</a>, but since these new ports feature <tt>pkg-plist</tt> files, I had to setup an update jail.  So updates for FreeBSD TeXLive ports will be generated daily at 5:30 CET.</p>]]></description><link>https://romain.blogreen.org/blog/2010/04/texlive-2009-on-freebsd/</link><category>FreeBSD</category><guid isPermaLink="true">https://romain.blogreen.org/blog/2010/04/texlive-2009-on-freebsd/</guid><pubDate>Mon, 12 Apr 2010 09:14:00 GMT</pubDate></item></channel></rss>