Posts on

The case for Infra as Code

Thu, 08 Dec 2022 00:00:00 +0000

Infra as Code in the Enterprise

As someone who has done infrastructure provisioning and automation for better parts of my career, I am constantly surprised at how ill informed a lot of people working in traditional enterprise IT is on the topic.

When an organisation moves workloads to one of the major clouds, too frequently people fall into the trap of thinking that the console is there as the primary means of setting up resources. Unfortunately the cloud providers in many cases build up under this assumption, as there is a distinct advantage in showing how “easy” it is to use the UI, over complicating efforts by introducing Infrastructure as Code (IaC).

However while the barrier to entry might seem low for the first couple of simple VMs you set up, what inevitably happens is that organic growth of the ClickOps (resources created by clicking in the UI) system will very soon create a lot of issues.

Reproducibility

I have heard a number of horror stories about critical ClickOps infrastructure that was inadvertently deleted or destructively altered, causing real production incidents. The perceived ease of use of the UI is often an illusion, where the UI tries to hide away important complexity.

When a team instead of using ClickOps writes a Terraform/Pulumi/Cloudformation config and deploys it, most such changes will both be preventible (see CICD below) and also, the resource in question can also be reproduced from the code.

CI/CD process for IaC

Most modern IaC pipelines have introduced a set of quality and security checks that will prevent most common mistakes, ensure policies are not broken and that consistent configuration is kept. Without defining the infra as code, the options for setting up these quality gates will be severely limited, and much more intrusive policy management will be required (automated checks of running resources etc.)

Change history

Using IaC with a sensible version control system enables the best kind of change history, again this is hard or impossible to replicate in a ClickOps environment.

IaC as documentation

When a cloud environment is defined sensibly via Infra as Code, that doubles as documentation for the setup. Without this, any resource created needs to be manually documented, a process which is prone to both (human) error and gaps in what is documented.

What now?

I hope more traditional enterprise IT engineers will see the IaC light, as more and more enterprises lift workloads from old outdated on-premise systems to cloud environments. However the general immaturity around the topic makes me worry..

Migration complete

Sun, 21 Jun 2020 00:00:00 +0000

As 2020 seems like a good year to get stuff done that has otherwise been neglected, I finally migrated my setup off a very old DigitalOcean droplet. It had been a steady host for years, but my initial plans to migrate from Ubuntu to CentOS7 a while back were never really completed. Centos8 is the new goodness, and I must say it was mostly a real pleasure to set up via DigitalOcean.

In my work at Varnish Software I liked to “dogfood” our products and technology, to learn and constantly flex some configuration muscles. So the old stack on denis.no was influenced by this and consisted of:

      ---------
      | Hitch |     (TLS termination)
      ---------
          |
     -----------
     | Varnish |    (Caching and routing)
     -----------
          |
      ---------
      | Nginx |     (File serving)
      ---------

In addition to Nginx, I had a bunch of smaller daemons that were directly fronted by Varnish, including Gitea, Filebin and other misc services.

As the need for dogfooding isn’t there anymore, and convenience outweighs most other factors these days, I’ve now reduced that stack to:

     ----------
     | Caddy2 |    (TLS termination, file serving and routing)
     ----------

I still have a couple of smaller services left which are set up with reverse_proxy in Caddy. Installing Caddy2 was almost too easy, and it involved ditching hundreds of lines of configuration for a very neat and consise Caddyfile.

The documentation for Caddy2 was pretty good, and made the process of migrating relatively quick and painless. I always wanted the super-neat LetsEncrypt cert integration, and that worked out just as well as I expected.

Rebooting the blog

Sun, 21 Jun 2020 00:00:00 +0000

The major content platforms of 2020 are all pretty horrible, so it seems like a good time as any to reboot personal web publishing, as a micro contribution to taking back the web. Thanks to Marcus for inspiring this, and for having good ideas about making publishing small posts easy on the go.

I exported the handful of Wordpress posts and have now gotten Hugo to work pretty well. Let’s see how many posts I manage to do this time ;)

Munin 2.0 on CentOS7 with Nginx and FastCGI

Wed, 13 Jul 2016 00:00:00 +0000

As the various bits of official Munin documentation seems to be in a limbo state where the current stable version (2.0.x) isn’t very well handled between the old and the new site, finding a good howto on setting up Munin with FastCGI and Nginx wasn’t as easy as it should have been.

There are articles (notably https://www.webfoobar.com/node/48 ) that are a bit on the overly complicated side, as it turns out, there exists a package called munin-nginx which simplifies things a lot.

So, assuming you are going to run munin without a URL prefix (https://munin.yoursite.com/) setting up Munin to use CGI for graphs and HTML turns out to be quite easy. The below steps were successfully performed using CentOS Linux release 7.2.1511, with munin-2.0.25-11 and munin-nginx-2.0.25-11.

sudo yum -y install munin munin-nginx nginx 

sudo sed -i 's/\(.*\)_strategy.*/\1_strategy cgi/;s/#cgiurl_graph/cgiurl_graph/' /etc/munin/munin.conf

for svc in munin-fcgi-graph munin-fcgi-html ; do sudo service $svc stop ; sudo chkconfig $svc on ; sudo service $svc start

htpasswd -c /etc/nginx/.htpasswd-munin-users munin

The Nginx config you need is:

<pre>server {
  listen 80; # IPv4
  listen [::]:80 ipv6only=on; # IPv6
  server_name munin.yoursite.com;
  
  ## Logs
  log_not_found off;
  error_log /var/log/nginx/munin.yoursite.com_error_log error;
  access_log off;

  location / {
    fastcgi_split_path_info ^(/)(.*);
    fastcgi_param PATH_INFO $fastcgi_path_info;
    fastcgi_param SCRIPT_FILENAME /var/www/cgi-bin/munin-cgi-html;
    include fastcgi_params;
    fastcgi_pass unix:/var/run/munin/fcgi-munin-html.sock;
    auth_basic "Restricted";
    auth_basic_user_file /etc/nginx/.htpasswd-munin-users;

    # Serve static files
    location /static/ {
      alias /etc/munin/static/;
      expires 30d;
    }

    # Munin CGI graph
    location ^~ /munin-cgi/munin-cgi-graph/ {
      access_log off;
      fastcgi_split_path_info ^(/munin-cgi/munin-cgi-graph)(.*);
      fastcgi_param PATH_INFO $fastcgi_path_info;
      fastcgi_param SCRIPT_FILENAME /var/www/cgi-bin/munin-cgi-graph;
      include fastcgi_params;
      fastcgi_pass unix:/var/run/munin/fcgi-munin-graph.sock;

      # Bypass cache.
      fastcgi_cache_bypass 0;
      fastcgi_no_cache 0;
      expires epoch;
    }
  }
}

Then restart nginx, and you should be able to use munin with cgi-generated graphs and html pages:

sudo service nginx restart

iTerm2 productivity

Thu, 07 May 2015 00:00:00 +0000

If you’re like me, you spend most of your time in the terminal. On OSX that means iTerm2 for me. I won’t go into details on how many orders of magnitude better iTerm2 is than the default Terminal app, because most likely you’re already familiar with it.

Update 2018, the following is not longer true, and personally I’ve switched back to stable releases of iTerm2. What you might not know is that what is considered the stable version of iTerm, is a bit like the stable version of Debian. It’s very conservatively updated, and most features take quite a bit of time to trickle down into a major release. So after I discovered that the Nightly builds are relatively stable I switched, and have not looked back.
Yes granted the updates keep rolling in, but as I’ll get to, using tmux for window arrangement means this doesn’t really bother me. So go get the nightly build now!

One of the best features of iTerm2 is the tmux integration. What it enables is a way for iTerm2 to communicate with tmux via tmux’ “Control Mode”. Basically you start an iTerm window and enter :
tmux -CC
which will open a new iTerm window linked with tmux. So any iTerm session operations (opening a new tab, a new window or a split) will be handed off to tmux. If you then were to quit iTerm, or close the window, you could easily get your complete window arrangement back by doing tmux -CC attach. This is indeed very handy.

So now we have pretty persistent window arrangements, which will give you the opportunity to over-indulge on tabs/splits/windows etc. Now we apply some order to the mess we inevitably will create.
iTerm has two cool features that will enable quick navigation of your sessions. The first one is badges. I’ve found that I like to set custom badges instead of relying on automatically set badges. So, first I set the badge options

printf "\e]1337;SetBadgeFormat=%s\a" $(echo -n "\(user.myBadge)" | base64)

and then define a bash function:

setbadge() { printf "\e]1337;SetUserVar=myBadge=%s\a" $(echo $1 | base64); }

Now we can easily set badges in tabs, by typing: setbadge BadgeName
The second feature that ties nicely into this is Session Search. Open with Cmd+Shift+O and you can quickly search and switch to the tab/window you like. There is also Tab Exposé Cmd+Alt+E but it’s slower.

There are tons of other ways iTerm2 can improve your everyday terminal life, I just found this to be a very handy addition to my toolbox.

Provisioning Vagrant with Salt

Mon, 05 May 2014 00:00:00 +0000

Vagrant sports out of the box integration with Saltstack, which works very well with minimum effort. However under the hood the default way this integration works is via a 4000-line bash script that bootstraps Saltstack on the VM. This would all be well and good, however, even if you were to pre-install the salt-call and salt-minion binaries onto your Vagrantbox, the salt-integration uses the same bash-script to install the configuration provided in the Vagrantfile.

So it has come to this.. I don’t really want this in my workflow. And I suspect any heavy Saltstack users might want to skip this aswell.

I found a way, that was not completely obvious, to make the Salt-integration work as quick and painless as I wanted in the Masterless mode:

Create a vagrantbox (in my case I use Packer with a set of templates), with the salt-binaries pre-installed.
Make sure the salt-minion daemon is disabled.
Overwrite the default minion config with the contents “file_client: local” (and of course any other configuration you require)

This way you do not have to use the “minion_config” setting in your Vagrantfile, and the salt provisioner plugin will happily skip the bootstrapping script.

You could always check the Saltstack installation-script for the Packer-template for reference.

You can now use the following setup in your Vagrantfile:

config.vm.synced_folder "salt/roots/", "/srv/salt/"

config.vm.provision :salt do |salt|
  salt.run_highstate = true
end

In salt/roots/ place your top.sls which could look something like this:

pre>base:
  '*':
    - default
</pre>

Which would then execute the salt/roots/default/init.sls state.

Media services

Thu, 08 Aug 2013 00:00:00 +0000

I thought I’d write a little summary on current media services I use, and why. I have mostly stopped buying music pressed on plastic discs, and the amount of movies I buy on-disc has also gone down. However that does not mean I don’t pay for my entertainment. Well on to the services.

Music

Spotify

I used to use Spotify actively, mainly due to their very good selection of EDM (Electronic Dance Music) and iOS-app, which has enabled me to completely stop syncing music from my computer. I was a premium subscriber for over a year, and the service (which cost around the price of 1 CD per month) was awesome. I used Spotify apps everywhere; iPhone, iPad, Mac, Linux (still a shamefully shoddy version though), and on Squeezebox. In addition to EDM, Spotify also features a more than good enough selection of “kid friendly” Norwegian music. When I checked out Rdio though I moved on..

Rdio

A few annoyances with the Spotify iOS app, and a constantly hopeless experience on Linux made me very ripe for a migration when I was introduced to Rdio. Rdio is a very similar service to Spotify, it generally has a comparable selection of music to stream, has about the same quality and cost the same for a mobile-enabled subscription.

Where Rdio differs is firstly in the quality of its apps. If you are on desktop, you can just use a normal web-browser to stream, or download a prepared Site-Specifc-Browser “app” that will give you a similar experience to the Spotify app. It does not have indexing of local media as an option though, so if you use that you’re out of luck. On iOS the app is a lot more snazzy design-wise, also it correctly purges content you no longer want synced offline (you can select what content to mobile sync from the app/web too).

Secondly, Rdio lets me build a “collection” of albums and artists. By doing so I get notifications of new music from these artists, and I can easily browse my subset of all available music. This mode of browsing is highly preferable to the search focused Spotify experience to me.

Soundcloud

Soundcloud has mostly taken over the role Myspace had as a channel for artists to share their tunes, demos, live-recordings, DJ-mixes etc. I know there are some issues concerning takedowns of more mainstream DJ-mixes, and that everything is not perfect in the Soundcloud, but for me it works very well as a nice way to keep in touch with my favourite artists and their work. I pay for a premium service here too, but would probably not if it wasn’t for wanting to share my own DJ-sets. As a consumer the service works very well without a subscription. Their iOS-apps are workable, but not nearly as polished as Rdio, and have no way to utilize downloads/off-line storage as far as I know.

Last.fm

This used to be a lot higher on my list of services I used actively. But due to their very limited streaming capabilites and somewhat lackluster selection of hosted music I quit being a paying subscriber of Last.fm, and instead use it solely as a place to aggregate my listening statistics, and keep up with what others are listening to. The Facebook/Spotify-connected service has filled some of this need lately, but my Last.fm connections are still a source of interesting finds every now and then.

Bandcamp

There are several issues with Bandcamp. One being that it has a very limited function for gifting music, or sharing CC-marked material, which is a shame really, as that would probably have made the service more interesting for both artists and fans. As it is Bandcamp provides a smooth way for me to pay the artists directly for FLAC downloads, and I highly prefer this model to Beatport (see below). Recently Bandcamp improved their music discovery options by introducing “My Bandcamp”. This allows me to track other peoples buying etc. and is better than not having any such features at all. It’s still no “Amazon for Music”, but getting better.

Beatport

Despite exorbitant prices, there is still no way to get around Beatport. The wide amount of EDM available through Beatport is mostly unmatched, even if one can often find tracks elsewhere. For the widest array of artists and tracks in lossless quality, it’s hard to beat Beatport though.. The website is almost workable too, but there are so many problems with the often half-assed approach to meta-data, and classification that it’s hard not to get a bit frustrated. I mean, when I pay more for a digital download than for a CD-copy (incl. shipping) I think I deserve proper metadata and the feeling that someone at Beatport cares enough to ensure classification remains somewhat appropriate?

Ektoplazm

While Beatport pushes material from any established artist, for the fresh stuff in my niche genre(s) I rely on Ektoplazm. An awesome source of free music, often free as in CC-licensed (type of CC license varies) too. And, just because it’s free doesn’t mean it features music that is worthless. Far from it, Ektoplazm often delivers music that is way more interesting than the commercial releases. I am sure there are other sites like Ektoplazm in other genres, or at least I hope so, as everyone deserves a service like this.

Gnome 3 adjustments and addons for a Gnome 2 user

Mon, 16 Apr 2012 00:00:00 +0000

As a long time professional Linux desktop user (since 2000 or so) I have used numerous desktop environments over the years. Initially Gnome1, then KDE2, then Gnome2 for a long time.

With the advent of Unity and Gnome 3.x, the distro vendors primary focus has understandably switched to supporting the future instead of maintaining the past. I will not go into the discussion whether this has happened too fast, or just fast enough.

Upgrading from the last Ubuntu that supported Gnome 2, I chose to try Unity, found out that it wasn’t for me (dual 1600×1200 monitor setup, multi workspace setup), then tried my luck with KDE (which I parted with around KDE3), and ended up with “Gnome Classic”. Now, after several issues in the process towards Precise Pangolin, I finally jumped ship to Fedora 16, and in that process tried to make the modern Gnome 3 work for me.

I will update this post as I make additional modifications, keeping it as a reference for my own use. Let me know in the comments if you have tips or suggestions.

Here are the adjustments and addons I have found, that improve the out-of-the-box Gnome 3 experience:

Prerequisites

In Fedora, ensure you have the following packages :

gnome-shell-extension-places-menu gnome-shell-extension-auto-move-windows gnome-shell-extension-alternative-status-menu gnome-shell-extension-pidgin gnome-shell-extension-remove-bluetooth-icon gnome-shell-extension-systemMonitor gnome-shell-extension-user-theme gnome-shell-extension-workspace-indicator gnome-shell-extension-remove-accessibility-icon gnome-shell-extension-apps-menu gnome-shell-theme-atolm gnome-tweak-tool

The very nice System Monitor shell extension is not packaged, but is easily installed from git:

https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/tree/gnome-3.2

I had little luck installing it into ~/.local/share/gnome-shell/extensions, but installing it globally under_ /usr/local/share/gnome-shell/extensions/_ worked fine.

Most of the settings and extensions mentioned below are enabled through gnome-tweak-tool (listed as “Advanced Settings in the Gnome launcher).

Shell extensions

Workspace Indicator (re-enables a workspace indicator in the “tasktray”)
Pidgin IM Integration (improves the usability of Pidgin under Gnome 3, not as good as it used to be in Gnome 2 but still ..)
Remove Accessibility Icon (with the agressive removal of useful indicators in G3 it surprises me how much unnecessary stuff is default enabled)
Applications Menu (mostly improves the “familiar feeling”, I don’t really use this much)
System Monitor (visual, ever present system monitor, even looks pretty good)
Remove Bluetooth Icon (I don’t use BT on my desktop, so this is totally redundant)
Places Status Indicator (re-enables quick access to folders in the file browser)
User Themes (let’s the user configure Gnome Theme settings)

Theme

I kept most of the defaults, but found that using the “Atolm” Shell Theme made me feel more at home (it makes Gnome 3 look a lot more like Gnome 2 in earlier Ubuntu’s..). I also enabled “Menus Have Icons” and “Buttons Have Icons”. Cursor, Icon, GTK+ and Window themes were kept to their default settings.

Tweaks

In gconf-editor (aka “Configuration Editor” in the launcher) I modified these keys :

/desktop/gnome/shell/windows/workspaces_only_on_primary – False (This makes my dual monitor setup work as I want it and disables the second screen from being a “sticky” workspace)
/desktop/gnome/shell/windows/button_layout – close,minimize,maximize:menu (My other OS of choice is OSX, and this makes the transition between them smoother)

Update for Gnome Shell 3.4

Settings that were previously in gconf are now migrated to dconf:

org.gnome.shell.overrides : workspaces-only-on-primary – False
org.gnome.shell.overrides : button-layout – close,minimize,maximize:menu
org.gnome.shell.overrides : attach-modal-dialogs – False (this detaches popupdialogs from their parent window)

Site moved

Sat, 05 Feb 2011 00:00:00 +0000

Moved to our new VPS running Ubuntu LTS, and in the process I migrated my blog from Drupal to WordPress. Drupal 7 seems great, but when it comes to simple blogging WordPress has the edge in simplicity, admin UI and maintainability. Maybe this means I’ll manage to blog a little more often, or maybe not, time will tell.

Why I almost didn’t get an iPhone

Mon, 13 Jul 2009 00:00:00 +0000

  <p>
    AppStore is cool, but Apples rules and rights of refusal are not. There are many stories of weird rejections and strict rules against improving on the experience with apps that cover basic functionality Apple itself already have developed solutions for. This means that nobody can create a better music player (with better codec support, integrated Last.fm scrobbling or other nice features), a better video player (again maybe including support for commonly used &#8220;internet-codecs&#8221;) or release a better browser or calendar..
  </p>
  
  <p>
    It also means Apple, or rather Apples app-judges, can refuse to distribute an app even without giving a reason why. I know this is &#8220;the Apple way&#8221; but it's stupid and frustrating. Even Microsoft would know better 😛
  </p>
  
  <p>
    I already mentioned it, but it's a major annoyance for me; the lack of codecs the i*-experience can handle (iTunes, iPhone, iPod). If you are like me and have a lot of FLACs lying around, you're pretty much left to your own devices. There are various solutions to this, <a href="http://elektronisk.net/node/12">mp3fs</a> being one, but nothing would be better than if iTunes could just get it right and convert my FLACs directly for me when sending to the portable gadget.
  </p>
  
  <p>
    The connector required for charging is also a minus, not the biggest one, and one that will probably <a href="http://www.macrumors.com/2009/06/29/apple-to-adopt-micro-usb-connectors-for-iphone-charging-in-europe/">resolve itself</a> anyway, but it's still less than optimal.
  </p>
  
  <p>
    I don't think Apple will ever fix the two biggest, most important issues I have with the platform. And if you are now laughing and saying that this is to be expected when you sell out to a vendor of proprietary software and platforms, you're of course right 😉 But there are simply <a href="http://elektronisk.net/node/13/">too many things</a> going for the iPhone right now, and the Android needs to grow up before it can be a viable alternative. (It probably will in time.)
  </p>
</div>

Why I will get an iPhone

Mon, 13 Jul 2009 00:00:00 +0000

  <p>
    I've been weighing it back and forth for a while. Which smartphone will be my first, after the Nokia N93 fiasco some years ago? (Symbian S60 seemed so cool back then.) Well, I think I've come to the conclusion that it'll be an iPhone 3GS. Here is why.
  </p>
  
  <p>
    I like Android as a mobile OS, probably more than iPhone OSX. But, and this is an important objection, there is no comparably cool hardware devices out yet to run Android. The iPhone 3GS hardware is <a href="http://www.anandtech.com/gadgets/showdoc.aspx?i=3579&p=1">awesome</a>, has a fast GL capable 3D chip and a speedy ARM CPU. A colleague, who recently got himself an HTC Magic, said that after getting accustomed to the graphics/3D capabilities of the iPod Touch (1st gen) he wasn't exactly bowled over by the Magic.
  </p>
  
  <p>
    Then there is the camera features, or lack of, on the Android devices so far. Neither the HTC Magic nor the HTC Hero have very sophisticated camera features. They're decent enough for sure, but one thing the N93 actually did pretty well was to eliminate the need for bringing a pocket digicam. I still have a decent amount of &#8220;in the moment&#8221; snaps and vids, shot with the phonecam. This includes the need for a proper flash/camera led. Are you listening HTC? The Samsung 7500 something rather will feature a 5 megapixel camera, but megapixels aren't everything, it could be good though.
  </p>
  
  <p>
    Another factor is the amount of available addons, cases, cables, gadgets, stuff and weirdness for the iPhone family. This is of course not something one can blame Google or HTC for, it's just a matter of Apple selling so many devices that the 3rd party manufacturers are sprouting around the platform.
  </p>
  
  <p>
    The AppStore and the amount of awesome apps and games is another strong reason to get the iPhone. Multitouch and the aforementioned 3D chip launched the iPhone/iPod Touch as a gaming platform in its own right. Sony is forced on the defence and just launched the &#8220;PSP Go&#8221; as a countermeasure (I don't think it's a good counter though, more on that later). The AppStore is mostly a win for everyone, it's an effective content distribution platform with a massive potential customer base.
  </p>
  
  <p>
    Summing it up, when I want the iPhone it's not simply as an advanced smartphone. The iPhone will enable me to bring one gadget that does a lot of things well enough that it eliminates the need for other gadgets in my pockets. No longer will I need a separate mp3-player, I can shoot photos and short videos, I can surf the web efficiently with a browser that works (the Android also covers this bit well), I have a mobile gaming device with a good selection of cheap and cool games on the go. Throw in a GPS and I'm pretty content. This is also why the PSP Go will not succeed. It might be a decent gaming platform (but less so than the Nintendo DS), but it still lacks the other features of the iPhone.
  </p>
  
  <p>
    With the iPhone platform, Apple has done a lot of things right, it mixes an attractive OS, good application support, a decent mix of features with a properly sized hardware platform (Nokia has failed on the latter point so many times). At the moment I cannot see any real competition for my kroner. Now I just need to choose a provider. Any thoughts why choose one over the other?
  </p>
  
  <p>
    There are sore spots with the iPhone / Apple experience. These will be the focus of my next post..
  </p>
</div>

mp3fs for Linux

Thu, 28 May 2009 00:00:00 +0000

  <p>
    1. sudo aptitude install libfuse-dev libflac-dev libmp3lame-dev libid3tag0-dev<br /> 2. wget mp3fs-0.13.tar.gz (<a href="http://sourceforge.net/project/showfiles.php?group_id=174365">http://sourceforge.net/project/showfiles.php?group_id=174365</a>)<br /> 3. tar xfz mp3fs-0.13.tar.gz<br /> 4. cd mp3fs-0.13<br /> 5. ./configure<br /> 6. make && sudo make install<br /> 7. sudo mkdir /srv/mp3fs<br /> 8. sudo mp3fs /FLAC/,256 /srv/mp3fs/ -o allow_other,ro
  </p>
</div>

mp3fs in OSX

Thu, 28 May 2009 00:00:00 +0000

  <p>
    mp3fs is a very nice idea and a smooth way to use a vast library of lossless archived CDs in the awesome <a href="http://flac.sourceforge.net/">FLAC</a> with <a href="http://www.apple.com/no/ipod/whichipod/">silly mp3players</a> without native support.
  </p>
  
  <p>
    The concept of mp3fs is a FUSE filesystem which converts FLACs to mp3s on the fly (CBR only as of now) via lame. Thus you can have the original FLACs stored, and expose a folder structure of converted mp3s to whatever you want. In my case iTunes.
  </p>
  
  <p>
    This is all pretty easy under Linux, but in OSX there are a few hurdles along the way. First one is that the current OSX <a href="http://www.uwe-arzt.de/node/32">patch</a> for mp3fs is only compatible with the Macports version of MacFUSE (currently 1.7_1). So any currently installed MacFUSE package (via DMG or otherwise) has to be removed.
  </p>
  
  <p>
    Once this is done installing mp3fs and MacFUSE is as easy as installing the mp3fs port. Here is a step-by-step working guide (tested with OSX Leopard 10.5.7).
  </p>
  
  <p>
    1. Install Macports (<a href="http://www.macports.org/install.php">http://www.macports.org/install.php</a>).<br /> 2. Open your favourite terminal.<br /> 3. &#8220;sudo port install mp3fs&#8221;<br /> 4. Make yourself a nice cup of your favourite hot beverage.<br /> 5. Create a mountpoint : &#8220;mkdir mp3fs&#8221;<br /> 6. Mount the mp3fs : &#8220;sudo mp3fs /Path/To/Your/FLAC/Dir,BITRATE /Path/To/Your/Mountpoint -o allow_other,ro&#8221;<br /> Example : &#8220;sudo mp3fs /Users/denis/Music/CDRips,256 /mnt/mp3fs -o allow_other,ro&#8221;<br /> 7. You now have an mp3fs filesystem at /mnt/mp3fs 🙂
  </p>
  
  <p>
    Running &#8220;mp3fs&#8221; with no options will show usage (no manpage yet), and running &#8220;mp3fs /Dir1,256 /Mountpoint -h&#8221; will show you FUSE mountoptions, one of these is -d for debug which could come in handy.
  </p>
  
  <p>
    Thanks to the coders of this nifty little FUSE fs, and to the guys patching it for OSX. Any chance we could have a cleaner patch that would also work with newer MacFUSE versions?
  </p>
</div>

How to read Mac .dmg images in Linux

Fri, 08 May 2009 00:00:00 +0000

  <p>
    Quick Guide that was tested on Ubuntu Linux Jaunty Jackalope.
  </p>
  
  <p>
    1. Download and compile DMG2IMG <a href="http://vu1tur.eu.org/tools/download.pl?dmg2img.tar.gz">http://vu1tur.eu.org/tools/download.pl?dmg2img.tar.gz</a> (<a href="http://vu1tur.eu.org/tools/">http://vu1tur.eu.org/tools/</a>) :
  </p>
  
  <blockquote>
    <p>
      wget -O dmg2img.tar.gz <a href="http://vu1tur.eu.org/tools/download.pl?dmg2img.tar.gz">http://vu1tur.eu.org/tools/download.pl?dmg2img.tar.gz</a><br /> tar xfz dmg2img.tar.gz<br /> cd dmg2img<br /> make
    </p>
  </blockquote>
  
  <p>
    2. Convert the DMG to IMG with dmg2img :
  </p>
  
  <blockquote>
    <p>
      ./dmg2img file.dmg
    </p>
  </blockquote>
  
  <p>
    3. Install hfsplus :
  </p>
  
  <blockquote>
    <p>
      sudo apt-get install hfsplus
    </p>
  </blockquote>
  
  <p>
    4. Mount the image as a loopback device :
  </p>
  
  <blockquote>
    <p>
      sudo mkdir /mnt/macimage<br /> sudo mount -t hfsplus -o loop file.img /mnt/macimage
    </p>
  </blockquote>
  
  <p>
    Voila.
  </p>
</div>

Norwegian holidays in Zimbra

Mon, 23 Mar 2009 00:00:00 +0000

  <p>
    1. Switch to the Calendar view in the Zimbra webui.<br /> 2. Click &#8220;New Calendar&#8221; (or &#8220;Ny kalender&#8221; in Norwegian).<br /> 3. Name it something nice like &#8220;Norwegian public holidays&#8221;.<br /> 4. Check the box &#8220;Synchronize events from remote calendar&#8221; (&#8220;Synkroniser avtaler mot ekstern kalender&#8221; in Norwegian).<br /> 5. Paste <a href="http://ical.mac.com/bjorkheim/Norske%20helligdager.ics">http://ical.mac.com/bjorkheim/Norske%20helligdager.ics</a><br /> 6. Click Ok.
  </p>
  
  <p>
    As long as the calendar maintainer bothers to update, Zimbra wil automatically receive updates. If you have another remote .ICS calendar you&#8217;d like to subscribe to, just add that one instead..
  </p>
</div>

Sqlite VACUUM for fun and profit

Wed, 18 Mar 2009 00:00:00 +0000

  <p>
    Sigurds triks gjengitt for allmennheten :
  </p>
  
  <p>
    Avslutt firefox.
  </p>
  
  <p>
    $ cd ~/.mozilla/firefox/<br /> $ cd PROFILFOLDER (byttes med din profilfolder)<br /> $ mkdir sqlite.back<br /> $ for file in *.sqlite ; do ls -lh $file ; cp $file sqlite.back ; echo &#8220;VACUUM;&#8221;|sqlite3 $file; ls -lh $file; done
  </p>
  
  <p>
    Start firefox.
  </p>
  
  <p>
    I mitt tilfelle fikk jeg krympet den største filen fra 51 til 17MB.
  </p>
  
  <p>
    At VACUUM av sqlite filer er mulig var jeg rett og slett ikke klar over, kjekt å vite ettersom mye rart bruker slike embedded-databaser for tiden.
  </p>
</div>

Store Norske lansert

Wed, 25 Feb 2009 00:00:00 +0000

  <p>
    Flere utviklere i Redpill Linpro (min arbeidsgiver) har bidratt i utviklingen av et på mange måter spennende produkt. Det er uansett hvordan man vurderer det bra med flere kilder til faktaopplysninger på nett, og en god kilde med norsk språk er jo flott.
  </p>
  
  <p>
    Det tok meg ikke mange klikk og søk rundt i de &#8220;kvalitetssikrede&#8221; artiklene før jeg snublet over innhold jeg stusset over. <a href="http://www.snl.no/Linux/IT">Linux</a> artikkelen på SNL sier nemlig i skrivende stund at Minix er &#8220;opphavet&#8221; til Linux og at Linus Torvalds videreutviklet Minix. Her er det potensielt en misforståelse. Torvalds benyttet Minix på universitetet og var som artikkelen hevder intressert i mer funksjonalitet enn Minix kunne tilby, men Torvalds begynte fra bunnen av på Linuxkjernen. Han videreutviklet ikke Minix.
  </p>
  
  <p>
    Registreringsprosessen på SNL var relativt enkel, og trass litt fikling med klipp-og-lim funksjonaliteten var redigering relativt lett. Vi får nå se hvor fort SNL plukker opp endringen.
  </p>
  
  <p>
    <strong>Oppdatering (2011-02-10): </strong>I ettertiden viste det seg at Store Norske fikk problemer med økonomien, men i skrivende stund er <a href="http://www.snl.no/Norsk_nettleksikon/Store_norske_leksikon_overdratt_til_nye_eiere">eierskapet på vei til nye hender</a>.
  </p>
</div>

Lightweight Web servers

Fri, 23 Jan 2009 00:00:00 +0000

  <p>
    En artig oppsummering av et bredt spekter servere. Hvorvidt mange av disse er mer enn akademisk intressante er et annet spørsmål..
  </p>
</div>

Red Hat Enterprise Linux 5.3

Wed, 21 Jan 2009 00:00:00 +0000

  <p>
    mod_perl-2.0.2-6.3.el5 -> mod_perl-2.0.4-6.el5<br /> openssl-perl-0.9.8b-10.el5_2.1 -> openssl-perl-0.9.8e-7.el5<br /> perl-5.8.8-15.el5_2.1 -> perl-5.8.8-18.el5<br /> perl-DBD-MySQL-3.0007-1.fc6 -> perl-DBD-MySQL-3.0007-2.el5<br /> perl-DBI-1.52-1.fc6 -> perl-DBI-1.52-2.el5<br /> openldap-2.3.27-8.el5_2.4 -> openldap-2.3.43-3.el5<br /> yum-3.2.8-9.el5_2.1 -> yum-3.2.19-18.el5
  </p>
  
  <p>
    Ellers diverse større eller mindre bumps av andre pakker.<br /> Full diffliste fra en utvalgt server etter skillet.
  </p>
  
  <p>
    NetworkManager-0.6.4-8.el5 -> NetworkManager-0.7.0-3.el5<br /> ORBit2-2.14.3-4.el5 -> ORBit2-2.14.3-5.el5<br /> OpenIPMI-2.0.6-6.el5_2.2 -> OpenIPMI-2.0.6-11.el5<br /> OpenIPMI-libs-2.0.6-6.el5_2.2 -> OpenIPMI-libs-2.0.6-11.el5<br /> OpenIPMI-tools-2.0.6-6.el5_2.2 -> OpenIPMI-tools-2.0.6-11.el5<br /> SysVinit-2.86-14 -> SysVinit-2.86-15.el5<br /> acpid-1.0.4-5 -> acpid-1.0.4-7.el5<br /> alsa-lib-1.0.14-1.rc4.el5 -> alsa-lib-1.0.17-1.el5<br /> alsa-lib-1.0.14-1.rc4.el5 -> alsa-lib-1.0.17-1.el5<br /> audit-1.6.5-9.el5 -> audit-1.7.7-6.el5<br /> audit-libs-1.6.5-9.el5 -> audit-libs-1.7.7-6.el5<br /> audit-libs-1.6.5-9.el5 -> audit-libs-1.7.7-6.el5<br /> audit-libs-python-1.6.5-9.el5 -> audit-libs-python-1.7.7-6.el5<br /> authconfig-5.3.21-3.el5 -> authconfig-5.3.21-5.el5<br /> autofs-5.0.1-0.rc2.88.el5_2.1 -> autofs-5.0.1-0.rc2.102<br /> bash-3.2-21.el5 -> bash-3.2-24.el5<br /> bind-libs-9.3.4-6.0.3.P1.el5_2 -> bind-libs-9.3.4-10.P1.el5<br /> bind-utils-9.3.4-6.0.3.P1.el5_2 -> bind-utils-9.3.4-10.P1.el5<br /> binutils-2.17.50.0.6-6.el5 -> binutils-2.17.50.0.6-9.el5<br /> ccid-1.0.1-6.el5 -> ccid-1.3.8-1.el5<br /> coreutils-5.97-14.el5 -> coreutils-5.97-19.el5<br /> cpuspeed-1.2.1-3.el5 -> cpuspeed-1.2.1-5.el5<br /> crash-4.0-5.0.3 -> crash-4.0-7.2.3.el5<br /> cryptsetup-luks-1.0.3-2.2.el5 -> cryptsetup-luks-1.0.3-4.el5<br /> cryptsetup-luks-1.0.3-2.2.el5 -> cryptsetup-luks-1.0.3-4.el5<br /> cups-1.2.4-11.18.el5_2.3 -> cups-1.3.7-8.el5<br /> cups-libs-1.2.4-11.18.el5_2.3 -> cups-libs-1.3.7-8.el5<br /> cups-libs-1.2.4-11.18.el5_2.3 -> cups-libs-1.3.7-8.el5<br /> dbus-1.0.0-7.el5_2.1 -> dbus-1.1.2-12.el5<br /> dbus-glib-0.70-5 -> dbus-glib-0.73-8.el5<br /> device-mapper-1.02.24-1.el5 -> device-mapper-1.02.28-2.el5<br /> device-mapper-1.02.24-1.el5 -> device-mapper-1.02.28-2.el5<br /> device-mapper-event-1.02.24-1.el5 -> device-mapper-event-1.02.28-2.el5<br /> device-mapper-multipath-0.4.7-17.el5 -> device-mapper-multipath-0.4.7-23.el5<br /> dhcdbd-2.2-1.el5 -> dhcdbd-2.2-2.el5<br /> dhclient-3.0.5-13.el5 -> dhclient-3.0.5-18.el5<br /> dmraid-1.0.0.rc13-15.el5_2.1 -> dmraid-1.0.0.rc13-33.el5<br /> dosfstools-2.11-6.2.el5 -> dosfstools-2.11-7.el5<br /> e2fsprogs-1.39-15.el5 -> e2fsprogs-1.39-20.el5<br /> e2fsprogs-libs-1.39-15.el5 -> e2fsprogs-libs-1.39-20.el5<br /> e2fsprogs-libs-1.39-15.el5 -> e2fsprogs-libs-1.39-20.el5<br /> elfutils-libelf-0.125-3.el5 -> elfutils-libelf-0.137-3.el5<br /> ethtool-5-1.el5 -> ethtool-6-2.el5<br /> file-4.17-13 -> file-4.17-15<br /> filesystem-2.4.0-1 -> filesystem-2.4.0-2<br /> findutils-4.2.27-4.1 -> findutils-4.2.27-5.el5<br /> firstboot-tui-1.4.27.3-1.el5 -> firstboot-tui-1.4.27.7-1.el5<br /> ftp-0.17-33.fc6 -> ftp-0.17-35.el5<br /> ghostscript-8.15.2-9.1.el5_1.1 -> ghostscript-8.15.2-9.4.el5<br /> glibc-2.5-24.el5_2.2 -> glibc-2.5-34<br /> glibc-2.5-24.el5_2.2 -> glibc.2.5-34<br /> glibc-common-2.5-24.el5_2.2 -> glibc-common-2.5-34<br /> gnupg-1.4.5-13 -> gnupg-1.4.5-14<br /> hal-0.5.8.1-35.el5 -> hal-0.5.8.1-38.el5<br /> httpd-2.2.3-11.el5_2.4 -> httpd-2.2.3-22.el5<br /> hwdata-0.213.6-1.el5 -> hwdata-0.213.11-1.el5<br /> initscripts-8.45.19.1.EL-1 -> initscripts-8.45.25-1.el5<br /> iproute-2.6.18-7.el5 -> iproute-2.6.18-9.el5<br /> iputils-20020927-43.el5 -> iputils-20020927-45.el5<br /> kbd-1.12-20.el5 -> kbd-1.12-21.el5<br /> kpartx-0.4.7-17.el5 -> kpartx-0.4.7-23.el5<br /> krb5-libs-1.6.1-25.el5_2.2 -> krb5-libs-1.6.1-31.el5<br /> krb5-libs-1.6.1-25.el5_2.2 -> krb5-libs-1.6.1-31.el5<br /> krb5-workstation-1.6.1-25.el5_2.2 -> krb5-workstation-1.6.1-31.el5<br /> ksh-20060214-1.7 -> ksh-20080202-2.el5<br /> kudzu-1.2.57.1.17-1 -> kudzu-1.2.57.1.21-1<br /> libgcc-4.1.2-42.el5 -> libgcc-4.1.2-44.el5<br /> libgcc-4.1.2-42.el5 -> libgcc-4.1.2-44.el5<br /> libgcj-4.1.2-42.el5 -> libgcj-4.1.2-44.el5<br /> libgcj-4.1.2-42.el5 -> libgcj-4.1.2-44.el5<br /> libgcrypt-1.2.3-1 -> libgcrypt-1.2.4-1.el5<br /> libgcrypt-1.2.3-1 -> libgcrypt-1.2.4-1.el5<br /> libhugetlbfs-1.2-5.el5 -> libhugetlbfs-1.3-3.el5<br /> libhugetlbfs-1.2-5.el5 -> libhugetlbfs-1.3-3.el5<br /> libpcap-0.9.4-12.el5 -> libpcap-0.9.4-14.el5<br /> libselinux-1.33.4-5.el5 -> libselinux-1.33.4-5.1.el5<br /> libselinux-1.33.4-5.el5 -> libselinux-1.33.4-5.1.el5<br /> libselinux-python-1.33.4-5.el5 -> libselinux-python-1.33.4-5.1.el5<br /> libstdc++-4.1.2-42.el5 -> libstdc++-4.1.2-44.el5<br /> libstdc++-4.1.2-42.el5 -> libstdc++-4.1.2-44.el5<br /> libutempter-1.1.4-3.fc6 -> libutempter-1.1.4-4.el5<br /> libutempter-1.1.4-3.fc6 -> libutempter-1.1.4-4.el5<br /> libvolume_id-095-14.16.el5 -> libvolume_id-095-14.19.el5<br /> logrotate-3.7.4-8 -> logrotate-3.7.4-9<br /> lvm2-2.02.32-4.el5_2.1 -> lvm2-2.02.40-6.el5<br /> m2crypto-0.16-6.el5.2 -> m2crypto-0.16-6.el5<br /> man-pages-2.39-10.el5 -> man-pages-2.39-12.el5<br /> mcstrans-0.2.7-1.el5 -> mcstrans-0.2.11-3.el5<br /> mesa-libGL-6.5.1-7.5.el5 -> mesa-libGL-6.5.1-7.7.el5<br /> mesa-libGL-6.5.1-7.5.el5 -> mesa-libGL-6.5.1-7.7.el5<br /> mkinitrd-5.1.19.6-28 -> mkinitrd-5.1.19.6-44<br /> mkinitrd-5.1.19.6-28 -> mkinitrd-5.1.19.6-44<br /> mod_perl-2.0.2-6.3.el5 -> mod_perl-2.0.4-6.el5<br /> module-init-tools-3.3-0.pre3.1.37.el5 -> module-init-tools-3.3-0.pre3.1.42.el5<br /> nash-5.1.19.6-28 -> nash-5.1.19.6-44<br /> neon-0.25.5-5.1 -> neon-0.25.5-10.el5<br /> neon-0.25.5-5.1 -> neon-0.25.5-10.el5<br /> net-snmp-libs-5.3.1-24.el5_2.2 -> net-snmp-libs-5.3.2.2-5.el5<br /> newt-0.52.2-10.el5 -> newt-0.52.2-12.el5<br /> nfs-utils-1.0.9-35z.el5_2 -> nfs-utils-1.0.9-40.el5<br /> nscd-2.5-24.el5_2.2 -> nscd-2.5-34<br /> nss_ldap-253-13.el5_2.1 -> nss_ldap-253-17.el5<br /> nss_ldap-253-13.el5_2.1 -> nss_ldap-253-17.el5<br /> ntp-4.2.2p1-8.el5 -> ntp-4.2.2p1-9.el5<br /> numactl-0.9.8-2.el5 -> numactl-0.9.8-7.el5<br /> numactl-0.9.8-2.el5 -> numactl-0.9.8-7.el5<br /> openldap-2.3.27-8.el5_2.4 -> openldap-2.3.43-3.el5<br /> openldap-2.3.27-8.el5_2.4 -> openldap-2.3.43-3.el5<br /> openssh-4.3p2-26.el5_2.1 -> openssh-4.3p2-29.el5<br /> openssh-clients-4.3p2-26.el5_2.1 -> openssh-clients-4.3p2-29.el5<br /> openssh-server-4.3p2-26.el5_2.1 -> openssh-server-4.3p2-29.el5<br /> openssl-0.9.8b-10.el5_2.1 -> openssl-0.9.8e-7.el5<br /> openssl-0.9.8b-10.el5_2.1 -> openssl-0.9.8e-7.el5<br /> openssl-perl-0.9.8b-10.el5_2.1 -> openssl-perl-0.9.8e-7.el5<br /> pam-0.99.6.2-3.27.el5 -> pam-0.99.6.2-4.el5<br /> pam-0.99.6.2-3.27.el5 -> pam-0.99.6.2-4.el5<br /> pam_krb5-2.2.14-1.el5_2.1 -> pam_krb5-2.2.14-10<br /> pam_krb5-2.2.14-1.el5_2.1 -> pam_krb5-2.2.14-10<br /> paps-0.6.6-17.el5 -> paps-0.6.6-18.el5<br /> parted-1.8.1-17.el5 -> parted-1.8.1-23.el5<br /> parted-1.8.1-17.el5 -> parted-1.8.1-23.el5<br /> patch-2.5.4-29.2.2 -> patch-2.5.4-29.2.3.el5<br /> perl-5.8.8-15.el5_2.1 -> perl-5.8.8-18.el5<br /> perl-DBD-MySQL-3.0007-1.fc6 -> perl-DBD-MySQL-3.0007-2.el5<br /> perl-DBI-1.52-1.fc6 -> perl-DBI-1.52-2.el5<br /> pkinit-nss-0.7.3-1.el5 -> pkinit-nss-0.7.6-1.el5<br /> pm-utils-0.99.3-6.el5.19 -> pm-utils-0.99.3-10.el5<br /> policycoreutils-1.33.12-14.el5 -> policycoreutils-1.33.12-14.2.el5<br /> popt-1.10.2-48.el5 -> popt-1.10.2.3-9.el5<br /> ppp-2.4.4-1.el5 -> ppp-2.4.4-2.el5<br /> prelink-0.3.9-2.1 -> prelink-0.4.0-2.el5<br /> procps-3.2.7-9.el5 -> procps-3.2.7-11.1.el5<br /> psacct-6.3.2-41.1 -> psacct-6.3.2-44.el5<br /> python-2.4.3-21.el5 -> python-2.4.3-24.el5<br /> python-urlgrabber-3.1.0-2 -> python-urlgrabber-3.1.0-5.el5<br /> quota-3.13-1.2.3.2.el5 -> quota-3.13-1.2.5.el5<br /> rdate-1.4-6 -> rdate-1.4-8.el5<br /> redhat-menus-6.7.8-2.el5 -> redhat-menus-6.7.8-3.el5<br /> redhat-release-5Server-5.2.0.4 -> redhat-release-5Server-5.3.0.3<br /> redhat-release-notes-5Server-15 -> redhat-release-notes-5Server-25<br /> rhel-instnum-1.0.8-1.el5 -> rhel-instnum-1.0.9-1.el5<br /> rhn-check-0.4.17-8.el5 -> rhn-check-0.4.19-17.el5<br /> rhn-client-tools-0.4.17-8.el5 -> rhn-client-tools-0.4.19-17.el5<br /> rhn-setup-0.4.17-8.el5 -> rhn-setup-0.4.19-17.el5<br /> rhnlib-2.2.5-1.el5 -> rhnlib-2.2.6-2.el5<br /> rpm-4.4.2-48.el5 -> rpm-4.4.2.3-9.el5<br /> rpm-libs-4.4.2-48.el5 -> rpm-libs-4.4.2.3-9.el5<br /> rpm-python-4.4.2-48.el5 -> rpm-python-4.4.2.3-9.el5<br /> selinux-policy-2.4.6-137.1.el5_2 -> selinux-policy-2.4.6-203.el5<br /> selinux-policy-targeted-2.4.6-137.1.el5_2 -> selinux-policy-targeted-2.4.6-203.el5<br /> setup-2.5.58-1.el5 -> setup-2.5.58-4.el5<br /> shadow-utils-4.0.17-13.el5 -> shadow-utils-4.0.17-14.el5<br /> smartmontools-5.36-4.el5 -> smartmontools-5.38-2.el5<br /> sos-1.7-9.2.el5_2.2 -> sos-1.7-9.16.el5<br /> stunnel-4.15-2 -> stunnel-4.15-2.el5<br /> subversion-1.4.2-2.el5 -> subversion-1.4.2-4.el5<br /> subversion-1.4.2-2.el5 -> subversion-1.4.2-4.el5<br /> sudo-1.6.8p12-12.el5 -> sudo-1.6.9p17-3.el5<br /> sysstat-7.0.2-1.el5 -> sysstat-7.0.2-3.el5<br /> system-config-network-tui-1.3.99.10-2.el5 -> system-config-network-tui-1.3.99.12-1.el5<br /> tcp_wrappers-7.6-40.4.el5 -> tcp_wrappers-7.6-40.6.el5<br /> tcp_wrappers-7.6-40.4.el5 -> tcp_wrappers-7.6-40.6.el5<br /> tcpdump-3.9.4-12.el5 -> tcpdump-3.9.4-14.el5<br /> tcsh-6.14-12.el5 -> tcsh-6.14-14.el5<br /> tmpwatch-2.9.7-1.1.el5.1 -> tmpwatch-2.9.7-1.1.el5<br /> traceroute-2.0.1-3.el5 -> traceroute-2.0.1-5.el5<br /> udev-095-14.16.el5 -> udev-095-14.19.el5<br /> unzip-5.52-2.2.1 -> unzip-5.52-3.el5<br /> usermode-1.88-3.el5.1 -> usermode-1.88-3.el5<br /> util-linux-2.13-0.47.el5 -> util-linux-2.13-0.50.el5<br /> vixie-cron-4.1-72.el5 -> vixie-cron-4.1-76.el5<br /> words-3.0-9 -> words-3.0-9.1<br /> wpa_supplicant-0.4.8-10.2.el5 -> wpa_supplicant-0.5.10-8.el5<br /> ypbind-1.19-8.el5 -> ypbind-1.19-11.el5<br /> yum-3.2.8-9.el5_2.1 -> yum-3.2.19-18.el5<br /> yum-rhn-plugin-0.5.3-12.el5_2.9 -> yum-rhn-plugin-0.5.3-30.el5<br /> yum-security-1.1.10-9.el5 -> yum-security-1.1.16-13.el5<br /> zip-2.31-1.2.2 -> zip-2.31-2.el5
  </p>
</div>

Støtt Wikipedia

Tue, 23 Dec 2008 00:00:00 +0000

  <p>
    Jeg vet ikke om noen informasjonstjeneste (søkemotorer ekskludert) på nett jeg bruker så ofte som Wikipedia.
  </p>
  
  <p>
    <a href="http://wikimediafoundation.org/wiki/Donate/en"><img border="0" alt="Wikipedia Affiliate Button" src="http://upload.wikimedia.org/wikipedia/foundation/1/1a/2008_fundraiser_banner_button-en.png" /></a>
  </p>
</div>

HOTEL PRO FORMA | Tomorrow, in a year

Fri, 28 Nov 2008 00:00:00 +0000

Blogging?

Thu, 27 Nov 2008 00:00:00 +0000

  <p>
    Hvem vet, kanskje overlever bloggen min litt lenger enn to måneder denne gangen? Det er vel første gang jeg velger å skrive norsk, kan jo hende det faller mer naturlig da. Vi får se.
  </p>
  
  <p>
    Valgte selvfølgelig Drupal siden jeg er en skikkelig fanboy, og jeg må si at ut-av-boksen opplevelsen med Drupal6 var utrolig bra!
  </p>
</div>

Drupal i vinden?

Thu, 27 Nov 2008 00:00:00 +0000

  <p>
    Drupal er ikke et perfekt publiseringssystem, som alle andre løsninger har Drupal feil, mangler og svakheter. Men Drupal er utrolig fleksibelt, har en yrende brukermasse, er GPLv2 lisensiert (fri programvare), og har ikke minst en haug funksjonalitet tilgjengelig som moduler som kan settes sammen mer eller mindre slik man ønsker.
  </p>
  
  <p>
    Når ABC Startsiden skulle velge publiseringssystem vurderte vi proprietære løsninger, bygg alt selv fra bunnen prosjekt, og en rekke fri programvareløsninger. Nå hadde sikkert <a href="http://www.abcnyheter.no">ABC Nyheter</a> blitt et glimrende produkt også med en proprietær løsning. Bak avgjørelsen lå uansett ønsket om friheten til å styre utviklingen akkurat dit vi ville. Vi ville ikke betale en enorm sum penger til en leverandør som så selv skulle avgjøre hvilken retning produktet utviklet seg.
  </p>
  
  <p>
    Av erfaring er nemlig publiseringsløsninger produkter som nesten aldri passer ut av boksen. Med mindre du har svært standardiserte behov (eksempelvis en normal blogg) kreves det alltid en viss mengde skreddersøm for å bygge det produktet redaksjonen og øvrige intressenter ser for seg. Med det spesielle fokuset ABC Nyheter hadde på involvering av brukere var det rimelig å anta at å bruke pengene på egenstyrt utvikling ville gi best avkastning på investerte penger..
  </p>
</div>