<?xml version="1.0"?>
<!-- name="generator" content="blosxom/2.0" -->
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">
  <channel>
    <title>Daniel Baumann - Random Debian Blog   </title>
    <link>http://blog.daniel-baumann.ch</link>
    <description>Yet another Random Debian Blog.</description>
    <language>en</language>

  <item>
    <title>Debian Live Autobuilds</title>
    <pubDate>Sun, 17 Jul 2011 01:49:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2011/07/17#20110717_debian-live-autobuilds</link>
    <description>
&lt;p&gt;
	Right now I am sitting in the train to the airport for going to DebCamp/DebConf 11 in Banja Luka, Bosnia and Herzegovina. During DebCamp amongst other things I am going to work on finishing up the last bits on getting daily/weekly Debian Live autobuilds back for wheezy.
&lt;/p&gt;

&lt;p&gt;
	This spring Jimmy Kaplowitz offered to help with the task of overseeing the debian-live autobuilder and to coordinate necessary bits with cdimage.debian.org. Having them on cdimage.d.o became recently possible as Steve McIntyre offered to make a VM available for us (live-build requires root privileges, and naturally, you would not want to let that run on the host system itself, that is why in the past it was not possible to build them on cdimage.d.o).
&lt;/p&gt;

&lt;p&gt;
	The remaining issues are, and this is why the autobuilds are not yet back since spring, that live-build still needs two things: a couple of tweeks for wheezy, and the autobuild stuff need to be properly integrated into live-build itself. That will happen as an additional binary package live-build-cron with a bunch of debconf questions, so that everyone and his dog can setup a debian-live autobuild server on his own machine. The initial upload (which will not yet work, do not bother to try) was uploaded to experimental this week and cleared the new queue, now looking forward to get this all finished up and resulting in a live-build uploaded to unstable by the end of the week. In the second week, Jimmy arrives, I will be introducing him to live-build and the various little things to watch for and hopefully manage to persuade him to take over the autobuilds maintenance.
&lt;/p&gt;

&lt;p&gt;
	Having all images that are based on packages solely from the stable/testing/unstable archives moved to cdimage.d.o is freeing up ressources on live.debian.net which did the job in the past since etch. Ben Armstrong volunteered to help with overseeing the live.d.n instance of live-build-cron that will build more then once per day images for si, with the only difference that they will not use live-* from the archive but the latest snapshots from our git snapshots repository. This will be a big help for the development as eventually we will be autotesting these images for various things.
&lt;/p&gt;

&lt;p&gt;
	Last but not least, thanks to both Jimmy and Ben for all your kindness, patience and help with this during the last couple of months. We have interesting times ahead.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Debian Live 6.0.2 Images</title>
    <pubDate>Wed, 13 Jul 2011 08:23:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2011/07/13#20110713_debian-live-6.0.2-images</link>
    <description>
&lt;p&gt;
	Two days before the 6.0.2 squeeze point release a user reported that usb-hdd images are not bootable for him. We could not reproduce that for several days but thanks to David Endler, we found out a few days ago that the reason for this is the following commit:
&lt;/p&gt;

&lt;p&gt;
	&lt;a href=&quot;http://live.debian.net/gitweb?p=live-build.git;a=commitdiff;h=3fa575103c6549ad7df429e385ce69f228e7ee31;hp=5ee20800049808498d0e5550d2842bfac5ccd25c&quot;&gt;&lt;tt&gt;Setting partition flags after creating the filesystem, workaround for bug in parted where we result in having the partition type set to linux otherways.&lt;/tt&gt;&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;
	The original problem was that in some situation the code resulted in having a wrong partition type and that can let to confusion for some bioses. For other reasons, the applied workaround has the side effect to cause parted to not set the bootable flat at all anymore and by that creating an even bigger problem - most crappy bioses these days require the bootable flag to be set and refuse to boot from a device otherwise (&lt;tt&gt;Missing Operating System&lt;/tt&gt;). Or in other words, the fix solved the original problem but created another one that is affecting much more bioses.
&lt;/p&gt;

&lt;p&gt;
	Rather than doing a hasty and suboptimal build of 6.0.2 with the commit reverted (and wasting resources for a 6.0.2a build some time later), we have looked into fixing the original problem properly without causing side effects. Images for the 6.0.2 squeeze point release will therefore be published in the next couple of days.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Re: Dealing with missing locales on remote hosts</title>
    <pubDate>Mon, 04 Jul 2011 06:25:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2011/07/04#20110704_re_dealing-with-missing-locales-on-remote-hosts</link>
    <description>
&lt;p&gt;
	&lt;a href=&quot;http://vincent.bernat.im/en/blog/2011-ssh-and-locales.html&quot;&gt;Vincent&lt;/a&gt;, the right way to deal with missing locales on remote hosts is to not deal with them at all.
&lt;/p&gt;

&lt;p&gt;
	On Debian wheezy and newer systems, eglibc contains the C.UTF-8 locale in the libc-bin package. This together with unsetting &lt;tt&gt;AcceptEnv&lt;/tt&gt; (or when customized, removing &lt;tt&gt;LANG&lt;/tt&gt; and &lt;tt&gt;LC_*&lt;/tt&gt; from it) in &lt;tt&gt;sshd_config&lt;/tt&gt; allows to get rid of locales on servers entirely (if you really require locales, then you would have installed locales-all anyway and the problem would not exist in the first place).
&lt;/p&gt;

&lt;p&gt;
	Some time ago, I have backported the C.UTF-8 changes (&lt;a href=&quot;http://vcs.progress-linux.org/?p=packages/eglibc.git;a=commitdiff;h=eec2703197a88039c36492618da28357607540ef&quot;&gt;1&lt;/a&gt;, &lt;a href=&quot;http://vcs.progress-linux.org/?p=packages/eglibc.git;a=commitdiff;h=5e7c9e35a4154e0e6f4bb8075f4bcd1dbe433806&quot;&gt;2&lt;/a&gt;, and &lt;a href=&quot;http://vcs.progress-linux.org/?p=packages/eglibc.git;a=commitdiff;h=c1a21eda78251bf620b7d5bef2c4a118365497eb&quot;&gt;3&lt;/a&gt;) and applied to &lt;a href=&quot;http://archive-master.progress-linux.org/packages/distribution/progress-artax/eglibc/&quot;&gt;my build&lt;/a&gt; of eglibc for Debian squeeze.
&lt;/p&gt;

&lt;p&gt;
	More information about C.UTF-8 can be found in &lt;a href=&quot;http://bugs.debian.org/609306&quot;&gt;#609306&lt;/a&gt;.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Progress Linux 1.0.0~pre1 (artax)</title>
    <pubDate>Wed, 16 Feb 2011 00:47:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2011/02/16#20110215_progress-linux-1.0.0~pre1</link>
    <description>
&lt;p&gt;
	The Progress Linux project is pleased to announce the availability of the first prerelease of the upcoming Progress Linux 1.0 (artax).
&lt;/p&gt;

&lt;p&gt;
	The images are available for download at:
&lt;/p&gt;

&lt;p&gt;
	&lt;a href=&quot;http://archive.progress-linux.org/progress-images/artax/&quot;&gt;http://archive.progress-linux.org/progress-images/artax/&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;
	A full list of changes may be viewed at:
&lt;/p&gt;

&lt;p&gt;
	&lt;a href=&quot;http://www.progress-linux.org/releases/artax/1.0.0_pre1/&quot;&gt;http://www.progress-linux.org/releases/artax/1.0.0_pre1/&lt;/a&gt;
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Booting images from within EXTLINUX</title>
    <pubDate>Fri, 07 Jan 2011 08:16:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2011/01/07#20110107_booting-images-from-within-extlinux</link>
    <description>
&lt;p&gt;
	Similar as people are doing with a seperate package for &lt;a href=&quot;http://michael-prokop.at/blog/2011/01/07/booting-iso-images-from-within-grub2/&quot;&gt;grub&lt;/a&gt;, Debians extlinux package as of version 2:4.03+dfsg-5 (and if you want a graphical boot menu, you will need syslinux-themes-debian version 4-1 or newer; both uploaded to experimental) handles booting images through memdisk out of the box now.
&lt;/p&gt;

&lt;p&gt;
	After you have upgraded your packages, just do:
&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Copy or symlink your images with the suffix &lt;tt&gt;.iso&lt;/tt&gt; or &lt;tt&gt;.img&lt;/tt&gt; to &lt;tt&gt;/boot&lt;/tt&gt;.&lt;/li&gt;
	&lt;li&gt;&lt;strike&gt;Set &lt;tt&gt;EXTLINUX_MEMDISK=&quot;true&quot;&lt;/tt&gt; in &lt;tt&gt;/etc/default/extlinux&lt;/tt&gt;.&lt;/strike&gt;&lt;/li&gt;
	&lt;li&gt;Run &lt;tt&gt;extlinux-update&lt;/tt&gt;.
	&lt;li&gt;Profit.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
	&lt;img src=&quot;http://www.daniel-baumann.ch/images/extlinux-memdisk.png&quot; alt=&quot;Booting images from within EXTLINUX&quot;/&gt;
&lt;/p&gt;

&lt;p&gt;
	&lt;b&gt;Update:&lt;/b&gt; After some more testing, &lt;tt&gt;EXTLINUX_MEMDISK&lt;/tt&gt; defaults to &lt;tt&gt;true&lt;/tt&gt; now.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Adding support for Lzip compression to reprepro</title>
    <pubDate>Thu, 14 Oct 2010 17:40:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2010/10/14#20101014_adding-support-for-lzip-compression-to-reprepro</link>
    <description>
&lt;p&gt;
	Today, I prepared a &lt;a href=&quot;http://bugs.debian.org/600230&quot;&gt;patch&lt;/a&gt; to reprepro to add support for debian packages using &lt;a href=&quot;http://www.nongnu.org/lzip/lzip.html&quot;&gt;Lzip&lt;/a&gt; compression.
&lt;/p&gt;

&lt;p&gt;
	A patched reprepro of squeeze for amd64 and i386 can be fetched from &lt;a href=&quot;http://people.debian.org/~daniel/dpkg-lzip/reprepro/&quot;&gt;here&lt;/a&gt;. An example package using Lzip compression, &lt;a href=&quot;http://packages.qa.debian.org/lzip&quot;&gt;lzip&lt;/a&gt; itself, is &lt;a href=&quot;http://people.debian.org/~daniel/dpkg-lzip/lzip/&quot;&gt;here&lt;/a&gt; (for this example, the package is build as 3.0 native on purpose).
&lt;/p&gt;

&lt;p&gt;
	Hopefully the patch will be merged so lzip compressed binary and source packages can be handled with reprepro.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Adding support for Lzip compression to dpkg</title>
    <pubDate>Wed, 13 Oct 2010 15:49:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2010/10/13#20101013_adding-support-for-lzip-compression-to-dpkg</link>
    <description>
&lt;p&gt;
	Today, I prepared a &lt;a href=&quot;http://bugs.debian.org/600094&quot;&gt;patch&lt;/a&gt; to dpkg to add support using &lt;a href=&quot;http://www.nongnu.org/lzip/lzip.html&quot;&gt;Lzip&lt;/a&gt; compression.
&lt;/p&gt;

&lt;p&gt;
	A patched dpkg of squeeze for amd64 and i386 can be fetched from &lt;a href=&quot;http://people.debian.org/~daniel/dpkg-lzip/dpkg/&quot;&gt;here&lt;/a&gt;. An example package using Lzip compression, &lt;a href=&quot;http://packages.qa.debian.org/lzip&quot;&gt;lzip&lt;/a&gt; itself, is &lt;a href=&quot;http://people.debian.org/~daniel/dpkg-lzip/lzip/&quot;&gt;here&lt;/a&gt; (for this example, the package is build as 3.0 native on purpose).
&lt;/p&gt;

&lt;p&gt;
	Hopefully the patch will be merged so we can make use of lzip compressed binary and source packages in Debian.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>dosfstools 3.0.10</title>
    <pubDate>Sun, 12 Sep 2010 03:50:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2010/09/12#20100912_dosfstools-3.0.10</link>
    <description>
&lt;p&gt;
	dosfstools did not correctly handle LFN (see Debian bug &lt;a href=&quot;http://bugs.debian.org/596329&quot;&gt;#596329&lt;/a&gt; for more information) and had some false positives with bad filenames (see Debian bug &lt;a href=&quot;http://bugs.debian.org/596327&quot;&gt;#596327&lt;/a&gt; for more information). Todays release of version 3.0.10 fixes this.
&lt;/p&gt;

&lt;p&gt;
	Source tarballs can be downloaded as usual from &lt;a href=&quot;http://www.daniel-baumann.ch/software/dosfstools/&quot;&gt;its homepage&lt;/a&gt;.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>The World's most powerful Wireless Network Card</title>
    <pubDate>Tue, 27 Jul 2010 09:25:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2010/07/27#20100727_the-worlds-most-powerful-wireless-network-card</link>
    <description>
&lt;p&gt;
	About two weeks ago I got a &lt;a href=&quot;http://www.wifly-city.com.tw/cp/html/?85.html&quot;&gt;Wifly-City G2000&lt;/a&gt;, the world's most powerful 802.11bg wireless network card. It features 2000mW which is 10 times more than the legally allowed limit of 200mW in Switzerland (or 2 times more than the allowed 1000mW in the USA, 5 times more than the allowed 400mW in Brazil, or 20 times more than the allowed 100mW in the EU).
&lt;/p&gt;

&lt;h1&gt;Contents&lt;/h1&gt;

&lt;p&gt;
	The adapter is sold as a set named &lt;a href=&quot;http://www.wifly-city.com.tw/cp/html/?85.html&quot;&gt;Wifly-City AVATAR-4PA&lt;/a&gt; with some accessories.
&lt;p&gt;

&lt;p&gt;
	&lt;table&gt;
		&lt;tr&gt;
			&lt;td&gt;
				&lt;a href=&quot;http://www.daniel-baumann.ch/images/wifly-city-g2000-1.jpg&quot;&gt;&lt;img src=&quot;http://www.daniel-baumann.ch/images/wifly-city-g2000-1_small.jpg&quot; /&gt;&lt;/a&gt;
			&lt;/td&gt;
			&lt;td&gt;
				&lt;a href=&quot;http://www.daniel-baumann.ch/images/wifly-city-g2000-2.jpg&quot;&gt;&lt;img src=&quot;http://www.daniel-baumann.ch/images/wifly-city-g2000-2_small.jpg&quot; /&gt;&lt;/a&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
		&lt;tr&gt;
			&lt;td&gt;
				&lt;a href=&quot;http://www.daniel-baumann.ch/images/wifly-city-g2000-3.jpg&quot;&gt;&lt;img src=&quot;http://www.daniel-baumann.ch/images/wifly-city-g2000-3_small.jpg&quot; /&gt;&lt;/a&gt;
			&lt;/td&gt;
			&lt;td&gt;
				&lt;a href=&quot;http://www.daniel-baumann.ch/images/wifly-city-g2000-4.jpg&quot;&gt;&lt;img src=&quot;http://www.daniel-baumann.ch/images/wifly-city-g2000-4_small.jpg&quot; /&gt;&lt;/a&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
	&lt;/table&gt;
&lt;/p&gt;

&lt;p&gt;
	&lt;small&gt;click on the images for full resolution&lt;/small&gt;
&lt;/p&gt;

&lt;p&gt;
	The box prominelty lists Linux compatibility and contains the following part:
&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;1x Wireless Network Adapter with standard USB Type Mini-B&lt;br /&gt;
	    (blue top face, black rear side)&lt;/li&gt;
	&lt;li&gt;1x 7dbi omnidirectional Antenna (black; SMA)&lt;/li&gt;
	&lt;li&gt;1x 10db directional Antenna (black; SMA)&lt;/li&gt;
	&lt;li&gt;1x 1m USB Cable (black; one Type A to Type Mini-B)&lt;/li&gt;
	&lt;li&gt;1x 5m USB Y Cable&lt;sup&gt;&lt;small&gt;1&lt;/small&gt;&lt;/sup&gt; (transparent; two Type A in Y to Type Mini-B)&lt;/li&gt;
	&lt;li&gt;1x Suction Cup (black)&lt;/li&gt;
	&lt;li&gt;1x 8cm Mini-CD with drivers and a manual&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
	The adapter has a Realtek 8187L chipset. This is particulary nice since there is no firmware needed for this chipset (therefore no questinable binary-only firmware blob). Also, it works out of the box with any Linux as of kernel version 2.6.30 and newer. I tested it on lenny with kernel backports, vanilla squeeze and vanilla sid. In all of these setups, it works out of the box without any configuration whatsoever - just plug it in and it works. I know that this is how it is supposed to be but still, I am always surprised again when things just work.
&lt;/p&gt;

&lt;p&gt;
	For those who care, this is the output of dmesg when plugging in the card...
&lt;/p&gt;

&lt;pre&gt;
[...]
usb 1-1: new high speed USB device using ehci_hcd and address 6
usb 1-1: New USB device found, idVendor=0bda, idProduct=8187
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: RTL8187_Wireless_LAN_Adapter
usb 1-1: Manufacturer: Manufacturer_Realtek_RTL8187_
usb 1-1: SerialNumber: xxxxxxxxxxxx
usb 1-1: configuration #1 chosen from 1 choice
phy1: Selected rate control algorithm 'minstrel'
phy1: hwaddr xx:xx:xx:xx:xx:xx, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
rtl8187: Customer ID is 0xFF
Registered led device: rtl8187-phy1::tx
Registered led device: rtl8187-phy1::rx
rtl8187: wireless switch is on
usbcore: registered new interface driver rtl8187
ADDRCONF(NETDEV_UP): wlan1: link is not ready
wlan1: direct probe to AP xx:xx:xx:xx:xx:xx (try 1)
wlan1: direct probe responded
wlan1: authenticate with AP xx:xx:xx:xx:xx:xx (try 1)
wlan1: authenticated
wlan1: associate with AP xx:xx:xx:xx:xx:xx (try 1)
wlan1: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=0 aid=5)
wlan1: associated
ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
wlan1: no IPv6 routers present
[...]
&lt;/pre&gt;

&lt;p&gt;
	...and this is the output of lsusb:
&lt;/p&gt;

&lt;pre&gt;
Bus 001 Device 006: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
&lt;/pre&gt;

&lt;h1&gt;Special Offer&lt;/h1&gt;

&lt;p&gt;
	I have played with the card for some time now and am really pleased with it. It works nicely with all the standard tools (aircrack-ng, kismet, etc.).
&lt;/p&gt;

&lt;p&gt;
	The only bummer is that the card is quite expensive. Fortunately, we could arrange a good deal for Free Software people where the store selling it does not make any money on it: instead of 89 USD you can get it for 68 USD (including everything).
&lt;/p&gt;

&lt;p&gt;
	If you are interested in getting one and you are comming to &lt;a href=&quot;http://debconf10.debconf.org&quot;&gt;DebConf 10&lt;/a&gt; in New York between 2010-07-25 and 2010-08-08, you can write an email to &lt;a href=&quot;mailto:ralph.amissah@gmail.com&quot;&gt;Ralph Amissah&lt;/a&gt; or speak to Ralph personally during the event.
&lt;/p&gt;

&lt;p&gt;
	&lt;sup&gt;&lt;small&gt;1&lt;/small&gt;&lt;/sup&gt; I have no idea why they are shipping with a Y cable because the adapter does not need one. However, it does not disturb and in case I ever need an Y cable, I now have one :)
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Debian Live Web Images Builder</title>
    <pubDate>Sun, 20 Jun 2010 11:46:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2010/06/20#20100620_debian-live-webbuilder</link>
    <description>
&lt;p&gt;
	&lt;a href=&quot;mailto:unixabg@gmail.com&quot;&gt;Richard Nelson&lt;/a&gt;, an outstanding &lt;a href=&quot;http://live.debian.net/&quot;&gt;debian-live&lt;/a&gt; contributor and team member since many years, has setup an instance of the live-helper CGI scripts that are included within live-helper.
&lt;/p&gt;

&lt;p&gt;
	This webbuilder lets users get their own customized images without the need of having to install &lt;a href=&quot;http://packages.qa.debian.org/live-helper&quot;&gt;live-helper&lt;/a&gt; and build them on their own. It's available at &lt;a href=&quot;http://live-helper.debian.net/&quot;&gt;&lt;b&gt;live-helper.debian.net&lt;/b&gt;&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	Apart from having some better looking html form and adding an online-help that will be worked on soon, it's working great. Thanks you, Richard.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Syslinux Themes for Debian</title>
    <pubDate>Wed, 16 Dec 2009 10:52:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2009/12/16#20091216_syslinux-themes-debian</link>
    <description>
&lt;p&gt;
	10 days ago, I uploaded &lt;a href=&quot;http://archive.debian-maintainers.org/syslinux/packages/syslinux-themes-debian/&quot;&gt;syslinux-themes-debian&lt;/a&gt;. It is sitting in the NEW queue ever since, and aparently I cannot rely on it being accepted anytime soon (it can be installed from the repository mentioned on the &lt;a href=&quot;http://syslinux.debian-maintainers.org/&quot;&gt;maintainers homepage&lt;/a&gt;, though).
&lt;/p&gt;

&lt;p&gt;
	However, while being still a first working version only that needs some improvements (especially until it could be used as a generic ressource for any other tool to make use of it, like &lt;a href=&quot;http://packages.qa.debian.org/live-helper&quot;&gt;live-helper&lt;/a&gt; or &lt;a href=&quot;http://packages.qa.debian.org/debian-cd&quot;&gt;debian-cd&lt;/a&gt;, eventually), here's a screenshot from the squeeze theme, credits and a big thanks for the awesome graphics to Agnieszka Czajkowska.
&lt;/p&gt;

&lt;p&gt;
	&lt;img src=&quot;http://www.daniel-baumann.ch/images/syslinux-themes-debian-squeeze.png&quot; alt=&quot;Syslinux Theme Debian Squeeze&quot;/&gt;
&lt;/p&gt;</description>
  </item>
  <item>
    <title>EXTLINUX as Alternative Bootloader</title>
    <pubDate>Mon, 30 Nov 2009 07:33:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2009/11/30#20091130_extlinux-as-alternative-bootloader</link>
    <description>
&lt;p&gt;
	In September, the Debian GRUB maintainers took &lt;a href=&quot;http://lists.debian.org/debian-devel-announce/2009/09/msg00002.html&quot;&gt;a step&lt;/a&gt; further in the long way of deprecating &lt;a href=&quot;http://packages.qa.debian.org/grub&quot;&gt;grub&lt;/a&gt; in favour of &lt;a href=&quot;http://packages.qa.debian.org/grub2&quot;&gt;grub2&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	From my &lt;b&gt;&lt;i&gt;&lt;u&gt;personal&lt;/u&gt;&lt;/i&gt;&lt;/b&gt; point of view, grub2 is not the way to go. Mostly because of these reasons:
&lt;/p&gt;

&lt;p&gt;
	&lt;ul&gt;
		&lt;li&gt;I don't have systems using a non-ext{3,4} filesystems.&lt;/li&gt;
		&lt;li&gt;I don't have use for any of the grub2 advanced features.&lt;/li&gt;
		&lt;li&gt;I don't want to wait another few seconds until grub2 has been loaded.&lt;/li&gt;
		&lt;li&gt;I don't want to learn yet another theme-ing mechanism for bootloader splashes and menu structures.&lt;/li&gt;
		&lt;li&gt;I don't want to use a different bootloader project, regardless from which media I boot (iso, usb-hdd, netboot).
	&lt;/ul&gt;
&lt;/p&gt;

&lt;p&gt;
	Back in Juli, when I was listening to the talk of &lt;a href=&quot;mailto:cate@debian.org&quot;&gt;Giacomo Catenazzi&lt;/a&gt; at &lt;a href=&quot;http://debconf9.debconf.org/&quot;&gt;DebConf 9&lt;/a&gt; about &lt;a href=&quot;https://penta.debconf.org/dc9_schedule/events/421.en.html&quot;&gt;bootloaders in Debian&lt;/a&gt; (&lt;a href=&quot;http://meetings-archive.debian.net/pub/debian-meetings/2009/debconf9/high/1011_boot_loaders.ogv&quot;&gt;high (618MB)&lt;/a&gt;, &lt;a href=&quot;http://meetings-archive.debian.net/pub/debian-meetings/2009/debconf9/low/1011_boot_loaders.ogv&quot;&gt;low (110MB)&lt;/a&gt;), I was reminded that I really should getting &lt;a href=&quot;http://syslinux.zytor.com/wiki/index.php/EXTLINUX&quot;&gt;EXTLINUX&lt;/a&gt; splittet out of Debians syslinux packaging and made available as an alternative bootloader within Debian.
&lt;/p&gt;

&lt;p&gt;
	Last week I hacked together an initial working version and uploaded it to experimental. Note that the two comands &lt;tt&gt;extlinux-install&lt;/tt&gt; and &lt;tt&gt;update-extlinux&lt;/tt&gt; do not have all the safety belts yet, the theme-ing mechanisms are not integrated yet (I'll upload a syslinux-themes-debian soon), and that the layout of the generation of the config files in &lt;tt&gt;/boot/extlinux&lt;/tt&gt; may could change (debian-wise, not upstream-wise). For me, it works already well though, I'm using it on my main desktop and notebook.
&lt;/p&gt;

&lt;p&gt;
	If you want to help finding bugs or submitting wishlist bugs for additional stuff to be added, and recovering from an unbootable system is not a problem for you, you're welcome to try it out:
&lt;/p&gt;

&lt;pre&gt;
	&lt;code&gt;# apt-get install -t experimental extlinux syslinux-common
	&lt;strike&gt;# sed -i -e 's|^postinst_hook =.*$|postinst_hook = update-extlinux|' \&lt;/strike&gt;
		&lt;strike&gt;-e 's|^postrm_hook =.*$|postrm_hook = update-extlinux|' \&lt;/strike&gt;
		&lt;strike&gt;/etc/kernel-img.conf&lt;/strike&gt;
	&lt;strike&gt;# mkdir -p /boot/extlinux&lt;/strike&gt;
	# update-extlinux
	# extlinux-install &lt;i&gt;DEVICE&lt;/i&gt;&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;
	&lt;b&gt;Update:&lt;/b&gt; Rather than having &lt;tt&gt;/etc/kernel-img.conf&lt;/tt&gt; modified by users, bootloader packages should add symlinks to their update scripts to &lt;tt&gt;/etc/kernel/postinst.d&lt;/tt&gt; and &lt;tt&gt;/etc/kernel/postrm.d&lt;/tt&gt;. Uploaded new version to experimental. Thanks maks for mentioning it.
&lt;/p&gt;

&lt;p&gt;
	&lt;b&gt;Update 2:&lt;/b&gt; Also, grub2 now (through grub-common) unavoidably pulls in libfreetype6 as depends. This is, for me, unacceptable depends to have on a server (OTOH, extlinux has no non-essential depends), YMMV.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>dosfstools 3.0.5</title>
    <pubDate>Mon, 27 Jul 2009 19:06:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2009/07/27#20090727_dosfstools-3.0.5</link>
    <description>
&lt;p&gt;
	Unfortunately, the last release of dosfstools had a stupid bug in dosfsck introduced by the VFAT patent avoidance patch that can cause data loss (see Debian bug &lt;a href=&quot;http://bugs.debian.org/538758&quot;&gt;#538758&lt;/a&gt; for more information). Todays release of version 3.0.5 fixes this.
&lt;/p&gt;

&lt;p&gt;
	Source tarballs can be downloaded as usual from &lt;a href=&quot;http://www.daniel-baumann.ch/software/dosfstools/&quot;&gt;its homepage&lt;/a&gt;.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>dosfstools 3.0.3 and 3.0.4</title>
    <pubDate>Tue, 21 Jul 2009 02:30:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2009/07/21#20090721_dosfstools-3.0.3+4</link>
    <description>
&lt;p&gt;
	In May, I have uploaded dosfstools version &lt;a href=&quot;http://git.debian.net/?p=debian/dosfstools.git;a=commit;h=89566399e407e54eb14d275770106ad42b3ac87c&quot;&gt;3.0.3&lt;/a&gt; that added support for Xilinx's Microblaze processor, which I forgot to blog about.
&lt;/p&gt;

&lt;p&gt;
	Today, I have uploaded version &lt;a href=&quot;http://git.debian.net/?p=debian/dosfstools.git;a=commit;h=6c68b94008157c444954d2f90a7f9ec8ffc2ec87&quot;&gt;3.0.4&lt;/a&gt; that fixes a problem when running on Linux with the &lt;a href=&quot;http://lkml.org/lkml/2009/6/26/313&quot;&gt;VFAT patent avoidance patch&lt;/a&gt; and fixes a bug in dosfsck.
&lt;/p&gt;

&lt;p&gt;
	Source tarballs can be downloaded as usual from &lt;a href=&quot;http://www.daniel-baumann.ch/software/dosfstools/&quot;&gt;its homepage&lt;/a&gt;.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Re: How to not use lintian overrides</title>
    <pubDate>Thu, 09 Jul 2009 08:34:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2009/07/09#20090709_re_how-to-not-use-lintian-overrides</link>
    <description>
&lt;p&gt;
	Dear &lt;a href=&quot;http://blog.technologeek.org/2009/07/09/227&quot;&gt;Julien&lt;/a&gt;, apart from the fact that delivering a message in the way you usually do it with such posts totally sucks, it might not hurt if you think about it first, thanks.
&lt;/p&gt;

&lt;p&gt;
	For those who care about: &lt;a href=&quot;http://qa.debian.org/developer.php?login=forensics-devel@lists.alioth.debian.org&quot;&gt;Debian Forensics&lt;/a&gt; is a packaging &lt;a href=&quot;https://alioth.debian.org/project/memberlist.php?group_id=100088&quot;&gt;team&lt;/a&gt; for forensic related packages in Debian. Although I am part of the team where I do work from time to time on the packages the team maintains, I do not want to be listed in uploaders, as I have already &lt;a href=&quot;http://qa.debian.org/developer.php?login=daniel&quot;&gt;enough packages&lt;/a&gt; to care about on my own. Adding a lintian override is the only workaround to get rid of the annoying lintian warnings. Or well, I could stop doing uploads and ask other people to do the work instead...
&lt;/p&gt;

&lt;p&gt;
	&lt;b&gt;Update:&lt;/b&gt; There is &lt;a href=&quot;http://lists.debian.org/debian-lint-maint/2009/04/msg00043.html&quot; title=&quot;lintian NMU check and teams&quot;&gt;this&lt;/a&gt; and &lt;a href=&quot;http://lists.debian.org/debian-devel/2009/04/msg00198.html&quot; title=&quot;Team uploads&quot;&gt;that&lt;/a&gt; thread where it was discussed some time ago, without solution. Thanks pabs for mentioning them.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>dosfstools 3.0.2</title>
    <pubDate>Sat, 28 Feb 2009 14:37:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2009/02/28#20090228_dosfstools-3.0.2</link>
    <description>
&lt;p&gt;
	I have uploaded dosfstools version &lt;a href=&quot;http://git.debian.net/?p=debian/dosfstools.git;a=commit;h=71ac75353d9158aed663f0a3a9d1a1a67ee4ff4f&quot;&gt;3.0.2&lt;/a&gt; that contains another few fixes. Source tarballs can be downloaded as usual from &lt;a href=&quot;http://www.daniel-baumann.ch/software/dosfstools/&quot;&gt;its homepage&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	The aim for 3.0 was to unify all the patches out there that have been accumulated over the years. As this is mostly completed now, I will soon start doing real work which will lead to dosfstools 3.1 eventually.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>dosfstools 3.0.1</title>
    <pubDate>Sun, 23 Nov 2008 17:11:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2008/11/23#20081123_dosfstools-3.0.1</link>
    <description>
&lt;p&gt;
	I have uploaded dosfstools version &lt;a href=&quot;http://git.debian.net/?p=debian/dosfstools.git;a=commitdiff;h=81882d20ec6bd4bf4914d39636cecc8c8e57dd67&quot;&gt;3.0.1&lt;/a&gt; that contains another few fixes. Source tarballs can be downloaded as usual from &lt;a href=&quot;http://www.daniel-baumann.ch/software/dosfstools/&quot;&gt;its homepage&lt;/a&gt;.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>dosfstools 3.0.0</title>
    <pubDate>Sun, 28 Sep 2008 07:06:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2008/09/28#20080926_dosfstools-3.0.0</link>
    <description>
&lt;p&gt;
	dosfstools is a collection of three utilities for making and checking FAT/MS-DOS filesystems:
&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;b&gt;dosfsck&lt;/b&gt; (aka fsck.msdos and fsck.vfat)&lt;/li&gt;
	&lt;li&gt;&lt;b&gt;dosfslabel&lt;/b&gt;&lt;/li&gt;
	&lt;li&gt;&lt;b&gt;mkdosfs&lt;/b&gt; (aka mkfs.dos and mkfs.vfat)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
	Unfortunately, dosfstools are without an active upstream maintainer for a couple of years. After I took over the package in Debian in June, I'm now also taking over upstream.
&lt;/p&gt;

&lt;p&gt;
	Version &lt;a href=&quot;http://git.debian.net/?p=debian/dosfstools.git;a=commitdiff;h=4df18ad463f41ae368c3c51bfb5a033072605663&quot;&gt;3.0.0&lt;/a&gt; includes all accumulated patches from Debian, Fedora, Gentoo and Suse together with some reordering of the sources. Packages have been uploaded to Debian sid, source tarballs can be downloaded from &lt;a href=&quot;http://www.daniel-baumann.ch/software/dosfstools/&quot;&gt;its new home&lt;/a&gt;.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Re: Debian not complying to licenses</title>
    <pubDate>Thu, 04 Sep 2008 16:12:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2008/09/04#20080904_re_debian-not-complying-to-licenses</link>
    <description>
&lt;p&gt;
	&lt;i&gt;Alexander Reichle-Schmehl &lt;a href=&quot;http://blog.schmehl.info/Debian/embeded-gpl&quot; title=&quot;http://blog.schmehl.info/Debian/embeded-gpl&quot;&gt;has replied&lt;/a&gt; to my blog post about &lt;a href=&quot;http://blog.daniel-baumann.ch/2008/09/01#20080902_debian-not-complying-to-licenses&quot; title=&quot;http://blog.daniel-baumann.ch/2008/09/01#20080902_debian-not-complying-to-licenses&quot;&gt;Debian not complying to licenses&lt;/a&gt;.&lt;/i&gt;
&lt;/p&gt;

&lt;p&gt;
	Dear Alexander, Debian is still not complying to licenses. And please don't cite me without the necessary context, thanks.
&lt;/p&gt;

&lt;p&gt;
	First, &lt;a href=&quot;http://packages.qa.debian.org/debian-cd&quot; title=&quot;http://packages.qa.debian.org/debian-cd&quot;&gt;debian-cd&lt;/a&gt; (and also debimg) must contain the sources for syslinux, not to fulfil the &lt;a href=&quot;http://www.gnu.org/licenses/gpl-2.0.html&quot; title=&quot;http://www.gnu.org/licenses/gpl-2.0.html&quot;&gt;GPL&lt;/a&gt;, but to fulfil the &lt;a href=&quot;http://www.debian.org/doc/debian-policy/&quot; title=&quot;http://www.debian.org/doc/debian-policy/&quot;&gt;Debian policy&lt;/a&gt;. Read what I wrote &lt;a href=&quot;http://lists.debian.org/debian-cd/2008/09/msg00012.html&quot; title=&quot;http://lists.debian.org/debian-cd/2008/09/msg00012.html&quot;&gt;here&lt;/a&gt; and &lt;a href=&quot;http://lists.debian.org/debian-cd/2008/09/msg00016.html&quot; title=&quot;http://lists.debian.org/debian-cd/2008/09/msg00016.html&quot;&gt;here&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	Second, even if debian-cd would go for source distribution under GPL clause 3b), both the current debian-cd version available in unstable (version 3.0.4) and current svn head (revision 1686, dated 2008-09-04) do not contain a written offer to obtain the sources for the embedded syslinux binary and are therefore, still, violating the GNU General Public License.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Debian not complying to licenses</title>
    <pubDate>Mon, 01 Sep 2008 20:19:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2008/09/01#20080902_debian-not-complying-to-licenses</link>
    <description>
&lt;p&gt;
	First of all, I don't want to blame individual persons. This is just a note of how disappointed I'm about some parts of Debian that are not complying to licenses when it comes to distributing software.
&lt;/p&gt;

&lt;p&gt;
	&lt;h2&gt;debian-cd embedds copy of syslinux without source&lt;/h2&gt;
&lt;/p&gt;

&lt;p&gt;
	A couple of years ago, I took over the maintenance of the &lt;a href=&quot;http://packages.qa.debian.org/syslinux&quot; title=&quot;http://packages.qa.debian.org/syslinux&quot;&gt;syslinux&lt;/a&gt; package since its previous maintainer was MIA. The takeover was motivated by to the fact, that having started to take care about live systems, I also started to use syslinux on a daily basis and that the syslinux package in Debian was horribly outdated.
&lt;/p&gt;

&lt;p&gt;
	At that time, I found out that &lt;a href=&quot;http://packages.qa.debian.org/debian-cd/&quot; title=&quot;http://packages.qa.debian.org/debian-cd/&quot;&gt;debian-cd&lt;/a&gt;, the toolkit to build the official Debian Installer images, doesn't take syslinux out of the archive at build-time of the image, but rather embedds a copy of the required binaries inside the package itself. So I asked Steve to update the binary what he did. Before the &lt;a href=&quot;http://www.debian.org/releases/etch/&quot; title=&quot;http://www.debian.org/releases/etch/&quot;&gt;etch release&lt;/a&gt;, I needed to ask the debian-cd team to sync again their embedded syslinux copy to match the one I had uploaded to the archive, as it was again outdated.
&lt;/p&gt;

&lt;p&gt;
	On the other hand, &lt;a href=&quot;http://packages.qa.debian.org/live-helper/&quot; title=&quot;http://packages.qa.debian.org/live-helper/&quot;&gt;live-helper&lt;/a&gt;, the toolkit to build the official Debian Live images, was always using the package out of the archive and did never had that problem.
&lt;/p&gt;

&lt;p&gt;
	After we have released the &lt;a href=&quot;http://lists.debian.org/debian-devel-announce/2008/08/msg00013.html&quot; title=&quot;http://lists.debian.org/debian-devel-announce/2008/08/msg00013.html&quot;&gt;Debian Lenny Live Beta 1&lt;/a&gt; images last week, we got reports from people trying them on Apple MacBooks and failed because syslinux, taken out of the archive (version 3.71), is broken on that hardware. Some people stated that Debian Installer images do work. That is because debian-cd has an embedded copy of syslinux (version 3.63) which doesn't have that regressions.
&lt;/p&gt;

&lt;p&gt;
	Since syslinux version 3.71 is present in testing/lenny as well as unstable/sid, and stable/etch has version 3.31, that means... if debian-cd is embedding a syslinux binary with a different version, it must contain the sources for it (it also needs to contain the sources for it anyway, even if it would embedd binaries of the current version, however, it would be a tiny bit less arguable if its sources would be at least present in the Debian archive). So I checked debian-cd, and surprise, it doesn't contain syslinux sources.
&lt;/p&gt;

&lt;p&gt;
	Syslinux is licensed under the &lt;a href=&quot;http://www.gnu.org/licenses/gpl-2.0.html&quot; title=&quot;http://www.gnu.org/licenses/gpl-2.0.html&quot;&gt;GNU General Public License, version 2&lt;/a&gt; or later. That means, that if you distribute the binaries and sources together, you can remove both at the same time if you decide to no longer distribute the binary (that is what Debian uses to do). This let me to bug &lt;a href=&quot;http://bugs.debian.org/497270&quot; title=&quot;http://bugs.debian.org/497270&quot;&gt;#497270&lt;/a&gt;. The option to distribute the binary with a note on how to get the sources, valid for three years, could theoretically be done, but isn't used so far (since it has pretty bad practical implications of keeping sources arround even after having stopped to distribute the binaries).
&lt;/p&gt;

&lt;p&gt;
	&lt;h2&gt;Debian sarge release has incomplete source images&lt;/h2&gt;
&lt;/p&gt;

&lt;p&gt;
	Checking fo the consequences for embedding bootloader binaries in debian-cd, I just saw that the Debian &lt;a href=&quot;http://www.debian.org/releases/sarge/&quot; title=&quot;http://www.debian.org/releases/sarge/&quot;&gt;sarge release&lt;/a&gt; does ship syslinux version 2.04 in its images, but is shipping syslinux 2.11 in its source images. This is another violation of the GPL and I've filled this as bug &lt;a href=&quot;http://bugs.debian.org/497471&quot; title=&quot;http://bugs.debian.org/497471&quot;&gt;#497471&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	...and syslinux is just one bootloader, only used for i386 and amd64. Someone still needs to check for all the other bootloaders for the other architectures we support (and those also for the etch release).
&lt;/p&gt;

&lt;p&gt;
	&lt;h2&gt;cdimage.debian.org distributes images without sources&lt;/h2&gt;
&lt;/p&gt;

&lt;p&gt;
	While browsing arround on &lt;a href=&quot;http://cdimage.debian.org/&quot; title=&quot;http://cdimage.debian.org/&quot;&gt;cdimage.debian.org&lt;/a&gt;, I also found the &lt;a href=&quot;http://pkg-kde.alioth.debian.org/kde4livecd.html&quot; title=&quot;http://pkg-kde.alioth.debian.org/kde4livecd.html&quot;&gt;kde4beta livecds&lt;/a&gt; made by the Debian KDE team back in November 2007. Although these images are nice, there is no source available for them at all. They use packages that are not available anymore in Debian since a long time. This time, this doesn't only violate the GPL as in the previous two cases, but almost any copyleft license under which we distribute software in main and that is included on these images. I've filled this as bug &lt;a href=&quot;http://bugs.debian.org/497462&quot; title=&quot;http://bugs.debian.org/497462&quot;&gt;#497462&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	Again, this is not about blaming individual persons. But I'm pretty disappointed by these things. In Debian, we spend a big chunk of time checking licenses of packages before we start distributing them. We have our beloved &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot; title=&quot;http://ftp-master.debian.org/new.html&quot;&gt;NEW queue&lt;/a&gt; where, after the Debian Developer who has initial uploaded a package and has checked the sources, also ftp-masters are re-checking each and every package to ensure that our archive is kept legal. The NEW queue is a mesurement that consumes a big deal of our time, making uploading packages new packages slow, but this is the prize we pay for ensuring our freedom. And we do also make a big fuss about cluebating upstreams that don't respect licenses (be it intentionally or by accident). However, it appears that as good as our package checks are, we spend little to no time to check our resulting products made from these packages.
&lt;/p&gt;

&lt;p&gt;
	&lt;b&gt;Update:&lt;/b&gt; kde4beta livecds have been removed now from cdimage.debian.org, see &lt;a href=&quot;http://bugs.debian.org/497462#15&quot; title=&quot;http://bugs.debian.org/497462#15&quot;&gt;#497462&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	&lt;b&gt;Update 2:&lt;/b&gt; &lt;a href=&quot;http://lists.debian.org/debian-cd/2008/08/msg00067.html&quot; title=&quot;http://lists.debian.org/debian-cd/2008/08/msg00067.html&quot;&gt;debimg&lt;/a&gt; does the same &lt;a href=&quot;http://lists.debian.org/debian-cd/2008/09/msg00010.html&quot; title=&quot;http://lists.debian.org/debian-cd/2008/09/msg00010.html&quot;&gt;crap&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	&lt;b&gt;Update 3:&lt;/b&gt; After beeing forced to write again about &lt;a href=&quot;http://lists.debian.org/debian-cd/2008/09/msg00031.html&quot; title=&quot;http://lists.debian.org/debian-cd/2008/09/msg00031.html&quot;&gt;debimg violating GPL&lt;/a&gt;, the offending binaries got finally removed now.&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;
	&lt;b&gt;Update 4:&lt;/b&gt; debian-cd seems to be fixed in SVN by this &lt;a href=&quot;http://svn.debian.org/wsvn/debian-cd?op=comp&amp;compare[]=%2Ftrunk@1696&amp;compare[]=%2Ftrunk@1697&quot;&gt;commit&lt;/a&gt;.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Debian Live Lenny Beta1</title>
    <pubDate>Wed, 27 Aug 2008 06:17:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2008/08/27#20080827_debian-live-lenny-beta1</link>
    <description>
&lt;p&gt;
	&lt;small&gt;&lt;i&gt;This is a post of the original announcement sent to &lt;a href=&quot;http://lists.debian.org/debian-devel-announce/2008/08/msg00013.html&quot;&gt;debian-devel-announce@lists.debian.org&lt;/a&gt;.&lt;/i&gt;&lt;/small&gt;
&lt;/p&gt;

&lt;p&gt;
	The &lt;a href=&quot;http://alioth.debian.org/project/memberlist.php?group_id=30929&quot; title=&quot;http://alioth.debian.org/project/memberlist.php?group_id=30929&quot;&gt;Debian Live team&lt;/a&gt; is pleased &lt;a href=&quot;http://lists.debian.org/debian-devel-announce/2008/08/msg00013.html&quot; title=&quot;http://lists.debian.org/debian-devel-announce/2008/08/msg00013.html&quot;&gt;to announce&lt;/a&gt; the first beta of Debian Lenny's Live images.
&lt;/p&gt;

&lt;p&gt;
	Although we missed releasing images for Etch along with the installer images, we are now prepared to release live images within the regular Lenny release process. This is the first official release of Debian Live and the whole team has been working hard during the &lt;a href=&quot;http://git.debian.net/?p=live-helper.git;a=blob;f=docs/NEWS&quot; title=&quot;http://git.debian.net/?p=live-helper.git;a=blob;f=docs/NEWS&quot;&gt;past 2.5 years&lt;/a&gt; to make &lt;a href=&quot;http://blog.daniel-baumann.ch/2006/02/14#20060214_debian-live-initiative&quot; title=&quot;http://blog.daniel-baumann.ch/2006/02/14#20060214_debian-live-initiative&quot;&gt;Debian's own&lt;/a&gt; live systems become a reality.
&lt;/p&gt;

&lt;p&gt;
	Nevertheless, we do need your help to find more bugs and improve the live systems, so please try them out. The images are available at:
&lt;/p&gt;

&lt;pre&gt;
	&lt;a href=&quot;http://cdimage.debian.org/cdimage/lenny_live_beta1/&quot; title=&quot;http://cdimage.debian.org/cdimage/lenny_live_beta1/&quot;&gt;http://cdimage.debian.org/cdimage/lenny_live_beta1/&lt;/a&gt;
&lt;/pre&gt;

&lt;p&gt;
	Please also have a look at the known issues listed below.
&lt;/p&gt;

&lt;p&gt;
	&lt;h1&gt;Main features&lt;/h1&gt;
&lt;/p&gt;

&lt;p&gt;
	&lt;h2&gt;100% Debian&lt;/h2&gt;
&lt;/p&gt;

&lt;p&gt;
	The build process of Debian Live basically consists of creating a Debian chroot, installing one or more kernels along with &lt;a href=&quot;http://packages.qa.debian.org/live-initramfs&quot; title=&quot;http://packages.qa.debian.org/live-initramfs&quot;&gt;live-initramfs&lt;/a&gt; (a set of hooks into initramfs-tools for handling booting from read-only media) and generating a bootable image from that.
&lt;/p&gt;

&lt;p&gt;
	This process is handled by &lt;a href=&quot;http://packages.qa.debian.org/live-helper&quot; title=&quot;http://packages.qa.debian.org/live-helper&quot;&gt;live-helper&lt;/a&gt;, a collection of shell scripts that allow us to automate and customize this process. &lt;a href=&quot;http://wiki.debian.org/DebianLive/Guidelines&quot; title=&quot;http://wiki.debian.org/DebianLive/Guidelines&quot;&gt;Considerable care&lt;/a&gt; is taken to ensure that the resulting live system is not tainted by the host system and that installed packages are not modified morethan absolutely necessary.
&lt;/p&gt;

&lt;p&gt;
	This ensures that Debian Live really &lt;b&gt;&lt;i&gt;&lt;u&gt;is&lt;/u&gt;&lt;/i&gt;&lt;/b&gt; Debian, and not &quot;just another&quot; a Debian-based live system.
&lt;/p&gt;

&lt;p&gt;
	&lt;h2&gt;Flavours&lt;/h2&gt;
&lt;/p&gt;

&lt;p&gt;
	Although live-helper is a toolkit to produce your very own live systems with only a few steps, we also provide prebuilt images that are meant to be used as reference systems for end-users. Currently, this consists of the three major desktop environments (GNOME, KDE and Xfce), as well as a small 'standard' image without a graphical environment.
&lt;/p&gt;

&lt;p&gt;
	For the desktop environments, package selection is performed by 'tasksel' with the respective desktop task, whilst the 'standard' image contains only packages of &quot;Priority: standard&quot; or greater, notwithstanding a handful of live-specific packages (console-common, eject, file, kbd, live-initramfs, locales, sudo and vim-tiny).
&lt;/p&gt;

&lt;p&gt;
	&lt;h2&gt;Image types&lt;/h2&gt;
&lt;/p&gt;

&lt;p&gt;
	Debian Live offers prebuilt images for CD/DVD discs, USB sticks (or any HD-media-like device), tarballs (for PXE netboot) as well as a bare squashfs image to boot from &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-September/002133.html&quot; title=&quot;http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-September/002133.html&quot;&gt;the web&lt;/a&gt; directly.
&lt;/p&gt;

&lt;p&gt;
	&lt;h2&gt;Live Magic&lt;/h2&gt;
&lt;/p&gt;

&lt;p&gt;
	&lt;a href=&quot;http://packages.qa.debian.org/live-magic&quot; title=&quot;http://packages.qa.debian.org/live-magic&quot;&gt;Live Magic&lt;/a&gt; is an GUI frontend around the live-helper scripts, offering a subset of the features of live-helper in an easy-to-use graphical user interface.
&lt;/p&gt;

&lt;p&gt;
	live-magic 1.0 was recently uploaded to sid and is the recommended version. It currently supports 7 languages.
&lt;/p&gt;

&lt;p&gt;
	&lt;h2&gt;Live Installer&lt;/h2&gt;
&lt;/p&gt;

&lt;p&gt;
	&lt;a href=&quot;http://packages.qa.debian.org/live-installer&quot; title=&quot;http://packages.qa.debian.org/live-installer&quot;&gt;Live Installer&lt;/a&gt; is a special udeb for the Debian Installer that (optionally) replaces a part of d-i in order to install the system from the live image instead of to bootstrapping it from .deb packages. This way, a live system can be easily installed to the harddisk, ensuring that the look and feel of the installation (including preseeding) works the same as the regular installer process.
&lt;/p&gt;

&lt;p&gt;
	Unfortunately, live-installer does still have a few minor bugs left and is thus not included in our builds yet; we hope to be able to include it in the next beta.
&lt;/p&gt;

&lt;p&gt;
	&lt;h1&gt;Known issues in this release&lt;/h1&gt;
&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;The prebuilt images for gnome-desktop and kde-desktop are a bit too big to fit on a CD. Although the automatic installation of Recommends was disabled to build the images, they are still too big. This will need further tweaking as they are supposed to fit with the next beta.
	&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;The rescue flavour, containing system rescue and forensic related packages, is missing in this beta release.
	&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;There will be a DVD image with the next beta that includes all three desktop environments so that you can choose at boot time which system you would like to start.
	&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;Due to time constraints, the prebuilt images for Beta1 are only covering i386 and amd64; with the next beta, powerpc and sparc will follow (if you wish to test these architectures earlier, please build them yourself).
	&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;The new desktop artwork is not yet included.
	&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;The syslinux menu is still the old, prompt-based one. A freshly made new syslinux vgamenu using the official lenny desktop artwork is on the way (the same as d-i media will use in Lenny).
	&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;No live-installer included yet (if you wish to test live-installer earlier, please build it yourself).
	&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;No win32-loader included yet.
	&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;Sid packages used - At the time of building the live images, both live-helper 1.0.0-1 and live-initramfs 1.139.1-1 from sid were used. Since the latter has not yet migrated to testing, it was included manually as a local package. This is undesirable, as the release is supposed to be self-contained - however, it is just a convenient workaround as both were granted freeze exception and will migrate soon.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Plans for next Beta release&lt;/h2&gt;

&lt;p&gt;
	We are looking forward to upload Beta2 in about two weeks from now (maybefollowed by a third beta) with one final RC after that which should be identical to the final release.
&lt;/p&gt;

&lt;p&gt;
	Some more details about the open things we would like to address in Beta2 and later can be found at the &lt;a href=&quot;http://wiki.debian.org/DebianLive/Lenny/Todo#Beta2&quot; title=&quot;http://wiki.debian.org/DebianLive/Lenny/Todo#Beta2&quot;&gt;wiki page&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
	The Debian Live team is still looking for more contributors for new features (post-lenny, though) as well as documentation writers for the manual (always). If you care about live systems, please &lt;a href=&quot;http://wiki.debian.org/DebianLive/Contribute&quot; title=&quot;http://wiki.debian.org/DebianLive/Contribute&quot;&gt;join and help&lt;/a&gt;!
&lt;/p&gt;

&lt;h3&gt;Thanks&lt;/h3&gt;

&lt;p&gt;
	Last but not least, our thanks goes to everyone who &lt;a href=&quot;http://git.debian.net/?p=live-helper.git;a=blob;f=docs/CREDITS&quot; title=&quot;http://git.debian.net/?p=live-helper.git;a=blob;f=docs/CREDITS&quot;&gt;has&lt;/a&gt; &lt;a href=&quot;http://git.debian.net/?p=live-initramfs.git;a=blob;f=docs/CREDITS&quot; title=&quot;http://git.debian.net/?p=live-initramfs.git;a=blob;f=docs/CREDITS&quot;&gt;contributed&lt;/a&gt; and to all maintainers that have kindly fixed live-specific bugs in their packages.
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Hewlett-Packard takes the piss out of their customers</title>
    <pubDate>Fri, 23 May 2008 06:29:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2008/05/23#20080523_hp-rant</link>
    <description>
&lt;p&gt;
	I got a new Hewlett-Packard LaserJet P3005X. I unpacked the device, connected power and ethernet, went to HP support page and downloaded the firmware upgrade for it.
&lt;/p&gt;

&lt;p&gt;
	After carefully reading through the whole readme, I initiated the firmware upload. After successfull flashing cycle, the printer reboots and freezes with this message on the display:
&lt;/p&gt;

&lt;pre&gt;
	&lt;b&gt;Downld file now
	SEND RFU UPGRADE&lt;/b&gt;
&lt;/pre&gt;

&lt;p&gt;
	...and the printer is dead, just after ten minutes of unpacking it.
&lt;/p&gt;

&lt;p&gt;
	How comes? HP equips &lt;b&gt;&lt;i&gt;some&lt;/i&gt;&lt;/b&gt; LaserJet P3005X with a formatter (that is the embedded &quot;computer&quot; inside the printer) that is not upgradeable. Brilliant.
&lt;/p&gt;

&lt;p&gt;
	And that is why Hewlett-Packard sucks beyond belief:
&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;It is not possible to know for the customer that some formatters are not upgradable - there is at no point any documentation of this issue, neither on HPs homepage, nor in the shipped documentation (ironically, HP ships two yellow sheets with errata for the printed manual to correct typos in serial numbers of supplies - warnings to kill your printer with a legitimate firmware upgrade is oviously not considered worth the paper).&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;Once you learned the reason for this mess from searching the Internet, there is no way to avoid it with another P3005 - there is no way to distinguish an upgradable and not upgradable formatter. All P3005 customers thus shall stick with old firmware (and e.g. not getting the fixed power saving mechanism by newer firmware).&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;Dead printers have to be send to a HP Repair Center at your own costs (and the HP support hotline you need to call in order to initiate the resend is expensive as well).&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;Although this happens with a brand new device covered by warranty, HP even charge you to exchange the formatter for fixing their own shortcomming.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;The whole issue is know at least since December 2007 (see &lt;a href=&quot;http://forums12.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=109447627+1211535363125+28353475&amp;threadId=1186108&quot;&gt;HP Forum&lt;/a&gt;).&lt;/li&gt;
&lt;/ol&gt;

Thanks Hewlett-Packard, you definitely did not make my day today.</description>
  </item>
  <item>
    <title>My misc developement news (Januar 2008)</title>
    <pubDate>Mon, 04 Feb 2008 04:46:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2008/02/04#20080204_my-misc-developement-news</link>
    <description>
&lt;p&gt;
	In the past I was not blogging small things if they were not worth a full blog entry on their own (or if I did not have the time to make up a full entry of it :). Inspired by the example of &lt;a href=&quot;mailto:hertzog@debian.org&quot; title=&quot;Rapha&amp;euml;l Hertzog &amp;lt;hertzog@debian.org&amp;gt;&quot;&gt;Rapha&amp;euml;l Hertzog &amp;lt;hertzog@debian.org&amp;gt;&lt;/a&gt; with &lt;a href=&quot;http://wiki.debian.org/DeveloperNews&quot; title=&quot;http://wiki.debian.org/DeveloperNews&quot;&gt;&quot;News for Debian developers&quot;&lt;/a&gt; for &lt;a href=&quot;http://lists.debian.org/debian-devel-announce/&quot; title=&quot;http://lists.debian.org/debian-devel-announce/&quot;&gt;&amp;lt;debian-devel-announce@lists.debian.org&amp;gt;&lt;/a&gt;, I am intending to do the same on a monthly basis about my own Debian related work. I will only list some noteworthy changes and news, though. This first entry about January 2008 also covers a few things from the last month of 2007.
&lt;/p&gt;

&lt;h2&gt;General News&lt;/h2&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;b&gt;Trusted Computing&lt;/b&gt;&lt;br /&gt;
	&lt;br /&gt;
	After having taken over some &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=joshua%40rubixlinux.org&amp;sev-inc=wishlist&quot; title=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=joshua%40rubixlinux.org&amp;sev-inc=wishlist&quot;&gt;rotting ITP bugs&lt;/a&gt;, Debian has now all the important packages to support Trusted Computing on platforms containing a TPM chip. The packages are not in good enough quality for release, but there is still some time left to fix that. Looking forward to make &lt;a href=&quot;http://www.debian.org/releases/lenny&quot; title=&quot;http://www.debian.org/releases/lenny&quot;&gt;lenny&lt;/a&gt; supporting TPM properly out of the box, as well as aiming for making Debian the best TPM enabled distribution available.&lt;br /&gt;
	&lt;br /&gt;
	Currently, the TSS software stack consists of &lt;a href=&quot;http://packages.qa.debian.org/t/trousers.html&quot; title=&quot;http://packages.qa.debian.org/trousers&quot;&gt;trousers&lt;/a&gt;, &lt;a href=&quot;http://packages.qa.debian.org/t/tpm-tools.html&quot; title=&quot;http://packages.qa.debian.org/tpm-tools&quot;&gt;tpm-tools&lt;/a&gt;, &lt;a href=&quot;http://packages.qa.debian.org/o/opencryptoki.html&quot; title=&quot;http://packages.qa.debian.org/opencryptoki&quot;&gt;opencryptoki&lt;/a&gt;, &lt;a href=&quot;http://packages.qa.debian.org/libe/libengine-tpm-openssl.html&quot; title=&quot;http://packages.qa.debian.org/libengine-tpm-openssl&quot;&gt;libengine-tpm-openssl&lt;/a&gt;, and &lt;a href=&quot;http://packages.qa.debian.org/e/ecryptfs-utils.html&quot; title=&quot;http://packages.qa.debian.org/ecryptfs-utils&quot;&gt;ecryptfs-utils&lt;/a&gt;.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;b&gt;Smartcards&lt;/b&gt;&lt;br /&gt;
	&lt;br /&gt;
	I am using smartcards since a while to hold GnuPG, LUKS, and OpenSSL keys/certificates. Thanks to &lt;a href=&quot;mailto:mejo@debian.org&quot; title=&quot;Jonas Meurer &amp;lt;mejo@debian.org&amp;gt;&quot;&gt;Jonas Meurer &amp;lt;mejo@debian.org&amp;gt;&lt;/a&gt; for applying &lt;a href=&quot;http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436434&quot; title=&quot;http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436434&quot;&gt;a fix&lt;/a&gt; and &lt;a href=&quot;http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438473&quot; title=&quot;http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438473&quot;&gt;a patch&lt;/a&gt; of mine to cryptsetup. Together with my uploads of &lt;a href=&quot;http://packages.qa.debian.org/g/gnupg-pkcs11-scd.html&quot; title=&quot;http://packages.qa.debian.org/gnupg-pkcs11-scd&quot;&gt;gnupg-pkcs11-scd&lt;/a&gt;, &lt;a href=&quot;http://packages.qa.debian.org/p/pam-pkcs11.html&quot; title=&quot;http://packages.qa.debian.org/pam-pkcs11&quot;&gt;pam-pkcs11&lt;/a&gt; and &lt;a href=&quot;http://packages.qa.debian.org/p/pcsc-omnikey.html&quot; title=&quot;http://packages.qa.debian.org/pcsc-omnikey&quot;&gt;pcsc-omnikey&lt;/a&gt;, I can now use Debian out of the box with smartcards for authentification, not relaying on patched or private packages anymore.&lt;br /&gt;
	&lt;br /&gt;
	The next aim is to integrate smartcard support into debian-installer. It should be possible to use/store keys or certificates for encrypted filesystems directly from/to a smartcard during installation time.
	&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Package News&lt;/h2&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;http://packages.qa.debian.org/b/botan-devel.html&quot; title=&quot;http://packages.qa.debian.org/botan-devel&quot;&gt;&lt;b&gt;botan-devel&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	The Botan library is maintained upstream in a stable release branch and a development release branch. Before, I was uploading as versioned source packages, botan1.4 and botan1.5. To be a bit more consistent, the two source packages are named &lt;a href=&quot;http://packages.qa.debian.org/b/botan.html&quot; title=&quot;http://packages.qa.debian.org/botan&quot;&gt;botan&lt;/a&gt; and &lt;a href=&quot;http://packages.qa.debian.org/b/botan-devel.html&quot; title=&quot;http://packages.qa.debian.org/botan-devel&quot;&gt;botan-devel&lt;/a&gt; now.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;a href=&quot;http://packages.qa.debian.org/g/gitosis.html&quot; title=&quot;http://packages.qa.debian.org/gitosis&quot;&gt;&lt;b&gt;gitosis&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	&lt;a href=&quot;mailto:tv@eagain.net&quot; title=&quot;Tommi Virtanen &amp;lt;tv@eagain.net&amp;gt;&quot;&gt;Tommi Virtanen &amp;lt;tv@eagain.net&amp;gt;&lt;/a&gt; has written a marvelous tool to securely manage hosted git repositories, named &lt;a href=&quot;http://packages.qa.debian.org/g/gitosis.html&quot; title=&quot;http://packages.qa.debian.org/gitosis&quot;&gt;gitosis&lt;/a&gt;. Having always looked for an elegant sollution to maintain git repositories through push/pull over SSH only, this package made an excellent addition to the Debian archive.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;a href=&quot;http://packages.qa.debian.org/g/gnunet.html&quot; title=&quot;http://packages.qa.debian.org/gnunet&quot;&gt;&lt;b&gt;gnunet&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	GNUnet, more precisely the &lt;a href=&quot;http://packages.qa.debian.org/g/gnunet.html&quot; title=&quot;http://packages.qa.debian.org/gnunet&quot;&gt;gnunet&lt;/a&gt;, &lt;a href=&quot;http://packages.qa.debian.org/g/gnunet-gtk.html&quot; title=&quot;http://packages.qa.debian.org/gnunet-gtk&quot;&gt;gnunet-gtk&lt;/a&gt; and &lt;a href=&quot;http://packages.qa.debian.org/g/gnunet-qt.html&quot; title=&quot;http://packages.qa.debian.org/gnunet-qt&quot;&gt;gnunet-qt&lt;/a&gt; packages where mainly maintained the last years by &lt;a href=&quot;mailto:Arnaud.Kyheng@free.fr&quot; title=&quot;Arnaud Kyheng &amp;lt;Arnaud.Kyheng@free.fr&amp;gt;&quot;&gt;Arnaud Kyheng &amp;lt;Arnaud.Kyheng@free.fr&amp;gt;&lt;/a&gt; with me playing co-maintainer.&lt;br /&gt;
	&lt;br /&gt;
	Arnaud has become busy within the last months, so I took over a more active role on its maintenance. Currently, all gnunet related packages are in sync and in its latest upstream version available in the archive. There is even a new sibling, &lt;a href=&quot;http://packages.qa.debian.org/g/gnunet-fuse.html&quot; title=&quot;http://packages.qa.debian.org/gnunet-fuse&quot;&gt;gnunet-fuse&lt;/a&gt;.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;a href=&quot;http://packages.qa.debian.org/i/icedove-l10n.html&quot; title=&quot;http://packages.qa.debian.org/icedove-l10n&quot;&gt;&lt;b&gt;icedove-l10n&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	After one and a half year of pushing its maintainer without any effect at all, I finally took over the unmaintained &lt;a href=&quot;http://packages.qa.debian.org/i/icedove-locales.html&quot; title=&quot;http://packages.qa.debian.org/icedove-locales&quot;&gt;icedove-locales&lt;/a&gt; package in October 2007. I immediately changed the package to the proper naming scheme (&lt;code&gt;icedove-l10n-*&lt;/code&gt;) which was an outstanding issue since August 2006.&lt;br /&gt;
	&lt;br /&gt;
	In the last weeks, I have added unofficial localizations for Galizian, Nepali and Ukrainian, now supporting 38 localizations in total. Icedove localizations are now in good shape again, always matching the &lt;a href=&quot;http://packages.debian.org/sid/icedove&quot; title=&quot;http://packages.debian.org/icedove&quot;&gt;Icedove&lt;/a&gt; version and no longer lagging behind.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;a href=&quot;http://packages.qa.debian.org/i/iceowl-l10n.html&quot; title=&quot;http://packages.qa.debian.org/iceowl-l10n&quot;&gt;&lt;b&gt;iceowl-l10n&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	Following &lt;a href=&quot;http://packages.qa.debian.org/i/iceweasel-l10n.html&quot; title=&quot;http://packages.qa.debian.org/iceweasel-l10n&quot;&gt;iceweasel-l10n&lt;/a&gt; and &lt;a href=&quot;http://packages.qa.debian.org/i/icedove-l10n.html&quot; title=&quot;http://packages.qa.debian.org/icedove-l10n&quot;&gt;icedove-l10n&lt;/a&gt;, there are finally also localizations for &lt;a href=&quot;http://packages.debian.org/sid/iceowl&quot; title=&quot;http://packages.debian.org/iceowl&quot;&gt;iceowl&lt;/a&gt; (Mozilla Sunbird) available. Populating packages for &lt;a href=&quot;http://packages.debian.org/sid/iceowl-extension&quot; title=&quot;http://packages.debian.org/iceowl-extension&quot;&gt;iceowl-extension&lt;/a&gt; (Mozilla Lightning) from the same source package is a bit trickier package-wise, but will be available soon too.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;a href=&quot;http://packages.qa.debian.org/i/iceweasel-l10n.html&quot; title=&quot;http://packages.qa.debian.org/iceweasel-l10n&quot;&gt;&lt;b&gt;iceweasel-l10n&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	In September 2007, &lt;a href=&quot;mailto:rmh@debian.org&quot; title=&quot;Robert Milan &amp;lt;rmh@debian.org&amp;gt;&quot;&gt;Robert Milan &amp;lt;rmh@debian.org&amp;gt;&lt;/a&gt; on behalf of the Catalan/Valencian Debian translator team asked me to remove the iceweasel-l10n-roa-es-val package. Unfortunately, this localization is related to a long standing cultural and political dispute between the Catalan speaking Spanish people and the City of Valencia. Additionally, the localization itself is of poor quality. Of course, I removed the package in unstable immediately and prepared an upload for stable at the same time.&lt;br /&gt;
	&lt;br /&gt;
	As usual, me &lt;a href=&quot;http://lists.debian.org/debian-release/2007/09/msg00046.html&quot;&gt;asking&lt;/a&gt; something on &lt;a href=&quot;http://lists.debian.org/debian-release/&quot; title=&quot;http://lists.debian.org/debian-release/&quot;&gt;debian-release&lt;/a&gt; results in first beeing &lt;a href=&quot;http://lists.debian.org/debian-release/2007/09/msg00140.html&quot;&gt;ignored&lt;/a&gt;, then &lt;a href=&quot;http://lists.debian.org/debian-release/2007/09/msg00141.html&quot;&gt;denied&lt;/a&gt; and third, two month after my request, beeing privately asked to &lt;a href=&quot;http://lists.debian.org/debian-changes/2007/10/msg00043.html&quot; title=&quot;http://lists.debian.org/debian-changes/2007/10/msg00043.html&quot;&gt;upload&lt;/a&gt; nevertheless. This is one of the reasons I sometimes fully understand fellow maintainers not carring about stable at all anymore, it has become indeed too much of a hassle.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;a href=&quot;http://packages.qa.debian.org/t/traceroute.html&quot; title=&quot;http://packages.qa.debian.org/traceroute&quot;&gt;&lt;b&gt;traceroute&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	For the last decade, Debian was shipping an implementation of traceroute originating from BSD. After I took over the package in late 2006, it became clear to me that Debian should not maintain its very own version of traceroute. Therefore, I replaced traceroute in August 2007 with an implementation from &lt;a href=&quot;mailto:Dimitry@Butskoy.name&quot; title=&quot;Dmitry K. Butskoy &amp;lt;Dmitry@Butskoy.name&amp;gt;&quot;&gt;Dmitry K. Butskoy &amp;lt;Dmitry@Butskoy.name&amp;gt;&lt;/a&gt;. Apart from the fact, that this modern implementation is better in every way (faster, cleaner, less bugs), it has an active upstream maintainer and is used by different other Linux distributions too.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;a href=&quot;http://packages.qa.debian.org/s/syslinux.html&quot; title=&quot;http://packages.qa.debian.org/syslinux&quot;&gt;&lt;b&gt;syslinux&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	Thanks to the work of &lt;a href=&quot;mailto:rmh@debian.org&quot; title=&quot;Robert Milan &amp;lt;rmh@debian.org&amp;gt;&quot;&gt;Robert Milan &amp;lt;rmh@debian.org&amp;gt;&lt;/a&gt;, syslinux has now 64-bit CPU detection in unstable (2:3.55-2) and experimental (2:3.60-2) again.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Team News&lt;/h2&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;http://alioth.debian.org/projects/forensics/&quot; title=&quot;http://alioth.debian.org/projects/forensics/&quot;&gt;&lt;b&gt;Debian Forensics&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	Unfortunately, Debian has at the moment very few forensic related packages in the archive.&lt;br /&gt;
	&lt;br /&gt;
	&lt;a href=&quot;mailto:dfence.242@gmail.com&quot; title=&quot;Christophe Monniez &amp;gt;dfence.242@gmail.com&amp;lt;&quot;&gt;Christophe Monniez &amp;lt;dfence.242@gmail.com&amp;gt;&lt;/a&gt; maintains a lot of forensic related packages on behalf of his &lt;a href=&quot;http://www.lnx4n6.be/&quot; title=&quot;http://www.lnx4n6.be/&quot;&gt;Debian based forensic LiveCD&lt;/a&gt;. Beeing interested to see them in Debian, I am mentoring him now how to merge them properly into Debian where possible, and maintain them in the official archive. We have formed an &lt;a href=&quot;http://alioth.debian.org/projects/forensics/&quot; title=&quot;http://alioth.debian.org/projects/forensics/&quot;&gt;Alioth project&lt;/a&gt; for this purpose. &lt;a href=&quot;http://qa.debian.org/developer.php?login=forensics-devel@lists.alioth.debian.org&quot; title=&quot;http://qa.debian.org/developer.php?login=forensics-devel@lists.alioth.debian.org&quot;&gt;Packages&lt;/a&gt; are maintained in git, everyone is welcome to join.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;&lt;a href=&quot;http://www.debian.org/devel/website/&quot; title=&quot;http://www.debian.org/devel/website/&quot;&gt;&lt;b&gt;Debian Website&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
	&lt;br /&gt;
	After having offered my help to maintain the &lt;a href=&quot;http://www.debian.org/consultants/&quot; title=&quot;http://www.debian.org/consultants/&quot;&gt;Debian Consultants&lt;/a&gt; list, I got added to the webwml team. Doing Debian consultancy myself, this is just another way of helping out Debian from time to time by adding, removing and updating some entries of like-minded people in a list.&lt;br /&gt;
	&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;</description>
  </item>
  <item>
    <title>Debian Live Web Boot</title>
    <pubDate>Fri, 07 Sep 2007 04:58:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2007/09/07#20070907_debian-live-web-boot</link>
    <description>
&lt;p&gt;
	Thanks to a patch from Mathieu Geli, &lt;a href=&quot;http://packages.debian.org/live-initramfs&quot; title=&quot;http://packages.debian.org/live-initramfs&quot;&gt;live-initramfs&lt;/a&gt; as of version 1.99.1-1 supports a boot parameter called fetch.
&lt;/p&gt;

&lt;p&gt;
	That means, that it is enough to have a bootloader (syslinux, grub, whatever) and a kernel with the initrd image on a medium (cdrom, usb-stick, whatever) to boot a Debian Live system directly from the Internet or the local network without needing to setup a netboot environment (as in PXE). Just type:
&lt;/p&gt;

&lt;pre&gt;
	&lt;tt&gt;live fetch=http://example.com/my_image.squashfs&lt;/tt&gt;
&lt;/pre&gt;

&lt;p&gt;
	at the boot prompt. Whithin the boot process of the live system, the squashfs image will be once downloaded into RAM. After that point, no network access is required anymore. This is also the reason why it was invented initially, it is an alternative to the conventional netboot (PXE with tftp for boot and shared root over a network filesystem such as cifs, nfs or smb) where permanent network access is required, not a replacement.
&lt;/p&gt;

&lt;p&gt;
	&lt;b&gt;Temporary limitations&lt;/b&gt;
&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;At the moment, the amount of RAM required to run a web booted live session is equal to the size of the squashfs image. Because &lt;a href=&quot;http://packages.debian.org/squashfs&quot; title=&quot;http://packages.debian.org/squashfs&quot;&gt;squashfs&lt;/a&gt; compression is quite good, this is not so much of a problem on reasonably modern machines (512MB for a complete Xfce Debian desktop, 758MB for a complete GNOME or KDE Debian desktop system). Nevertheless, improvements to use a local swap partition to store the image are on the way (including caching and updating).&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;

	&lt;li&gt;Due to a still &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-September/002136.html&quot; title=&quot;http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-September/002136.html&quot;&gt;pending move&lt;/a&gt; of the machine where &lt;a href=&quot;http://live.debian.net/&quot; title=&quot;http://live.debian.net/&quot;&gt;live.debian.net&lt;/a&gt; is hosted, there are not yet autobuild squashfs images available. Later, you can just boot with something similar as: &lt;tt&gt;live fetch=http://live.debian.net/webboot/etch&lt;/tt&gt;.&lt;/li&gt;
&lt;/ul&gt;</description>
  </item>
  <item>
    <title>Swiss Voting on OOXML</title>
    <pubDate>Tue, 04 Sep 2007 07:54:00 EDT</pubDate>
    <link>http://blog.daniel-baumann.ch/2007/09/04#20070904_swiss-voting-on-ooxml</link>
    <description>
&lt;p&gt;
	This is the result of Swiss voting on ISO/IEC DIS 29500, the fast-tracking of the Microsoft Office Open XML file format.
&lt;/p&gt;

&lt;table&gt;
	&lt;tr&gt;&lt;td&gt;4 screen AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Accenture AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;ADVIS AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;ALTRAN AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Baggenstos Wallisellen&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Bechtle IT-Systemhaus Thalwil&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;CIS-Consulting&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Comsoft Direct AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Coris SA&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Dr. Pascal Sieber &amp;amp; Partners AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;dynawell ag&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Ecma International&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;ELCA Informatik AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;EPFL Lausanne&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;FSFE Free Software Foundation Europe&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;GARAIO AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Gysel Ulrich Emanuel&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;H.R. Thomann Consulting&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;&lt;b&gt;Hewlett-Packard (Schweiz) GmbH&lt;/b&gt;&lt;/td&gt;&lt;td&gt;&lt;b&gt;approval&lt;/b&gt;&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;HSW Luzern, Institut IWI&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;IAMCP Switzerland&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;IBM (Schweiz)&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Informatikstrategieorgan Bund ISB&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;isolutions gmbh&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;itsystems AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Kull AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;&lt;b&gt;leanux.ch AG&lt;/b&gt;&lt;/td&gt;&lt;td&gt;&lt;b&gt;approval&lt;/b&gt;&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Leuchter Informatik AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;MESO Products&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Microsoft Schweiz GmbH&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;MondayCoffee AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Namics AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;NEXPLORE AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;&lt;b&gt;Novell (Schweiz) AG&lt;/b&gt;&lt;/td&gt;&lt;td&gt;&lt;b&gt;approval&lt;/b&gt;&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Online Consulting AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Open Text&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;PageUp Bern&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;PC-WARE Systems (Schweiz) AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Puzzle ITC GmbH&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;SBS Solutions AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Secunet SwissIT AG&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;SIUG Swiss Internet User Group&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;SKSF&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Skybow AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;SoftwareONE&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;SyGroup GmbH&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Sylog Consulting SA&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Syndrega&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;TheAlternative&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Trivadis AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Unic Internet Solutions&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;usedSoft AG&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Verein /ch/open&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;WAGNER AG Kirchberg&lt;/td&gt;&lt;td&gt;approval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Wilhelm Tux (Verein)&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;W&amp;uuml;rgler Consulting&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;Z&amp;uuml;rcher Hochschule der K&amp;uuml;nste&lt;/td&gt;&lt;td&gt;disapproval&lt;/td&gt;&lt;/tr&gt;
	&lt;tr&gt;&lt;td&gt;&lt;b&gt;Total of voting (75% majority)&lt;/b&gt;&lt;/td&gt;&lt;td&gt;&lt;b&gt;43 approval (75.4%); 14 disapproal (24.6%)&lt;/b&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;

&lt;p&gt;
	A majority with 75% has been reached with &lt;b&gt;one&lt;/b&gt; vote.
&lt;/p&gt;

&lt;h4&gt;
	Why do Hewlett-Packard and Novell vote IN FAVOUR for OOXML!?
&lt;/h4&gt;</description>
  </item>
  </channel>
</rss>
