SiteMap
-
-
-
-
-
-
The annual Debian developer's conference, this year hosted near Helsinki.
-
"The Debian System" will be on sale at the LinuxTag 2005.
-
Come celebrate the release of Debian GNU/Linux 3.1 "sarge" and the Debian Book with us!
-
The wait has been long; the book is going to be in stores Real Soon Now.
-
No news is good news, so allow me to at least wish you all the best for the new year!
-
Europe's largest event about Free Software, Linux and Open Source.
-
Due to a number of reasons, there will not be an updated edition of the book for etch. I am working on a version for Lenny though.
-
-
-
<p>The "Development and improvement" subsection of section 2.5.1 talks about the need of an improved boot initialisation sequence. The <a href="http://alioth.debian.org/projects/initscripts-ng/ target="_blank">initscripts-ng</a> project has been started with the goal to create a better init system.</p>
-
<p>The integration of the <span class="Code">amd64</span> architecture into the official archive <a href="http://lists.debian.org/debian-devel-announce/2006/02/msg00007.html" target="_blank">is underway as part of the mirror split</a>, and <a href="http://lists.debian.org/debian-devel-announce/2006/03/msg00014.html" target="_blank">the first package has been uploaded</a>. Within the next few weeks, <span class="Code">amd64</span> will thus become an official Debian architecture, and it shall be released as part of Debian <span class="Code">etch</span>, the next stable release.</p>
-
<p>The <span class="Code">debedit</span> tool referenced in the second to last paragraph of section 5.9.2 has been added to the <span class="Code">devscripts</span> package in version 2.9.3 (i.e. in <span style="font-style: italic;">etch</span>). It is called <span class="Code">deb-reversion</span>, not <span class="Code">debedit</span>, however. <br/> </p>
-
<p>Even though <span class="Code">amd64</span> is not (yet) an official architecture, the Debian security team <a href="http://www.debian.org/News/2005/20050811" target="_blank">has declared</a> <span style="text-decoration: underline;"></span>that it will support <a href="http://lists.debian.org/debian-devel-announce/2005/06/msg00005.html" target="_blank">the <span style="font-style: italic;">sarge</span> release of the Debian AMD64 port</a>, which was released shortly after the official <span style="font-style: italic;">sarge</span> release.</p> <p> </p>
-
<p>Joey Hess <a target="_blank" href="http://lists.debian.org/debian-devel-announce/2005/09/msg00006.html">announced</a> the full security support for the Debian <span style="font-style: italic;">testing</span> release. Even though still inofficial, this makes Debian <span style="font-style: italic;">testing</span> a viable alternative to the <span style="font-style: italic;">stable</span> release, for those with needs for greater currency of software. </p>
-
<p>Jaldhar H. Vyas is the third author of <span style="text-decoration: underline;">Debian GNU/Linux 3.1 Bible</span>. He joined the other two towards the end of their book release cycle.</p>
-
<p>The official title of the book written by David B. Harris, Benjamin Mako Hill <a href="520-jaldhar">and Jaldhar H. Vyas</a> is <span style="text-decoration: underline;">Debian GNU/Linux 3.1 Bible</span>, not 3.X as I wrote in my book. At the time of writing, the authors had not settled for a title.</p>
-
<p>The <span class="Code">debbugs</span> maintainers are on a roll and have added the ability to block bugs with other bugs. "Blocking" is the official term, though the concept may also be described as "bug dependencies." More information is available in <a target="_blank" href="http://azure.humbug.org.au/~aj/blog/2005/08/12#2005-08-12-postdc5">this blog entry by Anthony Towns</a>, and <a href="http://kitenet.net/~joey/blog/entry/bts_blockers_support-2005-08-12-15-43.html" target="_blank">this one by Joey Hess</a>.</p>
-
<p>The Debian bug tracking system now allows users to attach their own tags to bug reports. You can find the juicy details in the <a target="_blank" href="http://lists.debian.org/debian-devel-announce/2005/09/msg00002.html">announcement mail</a>.</p>
-
<p>Jurij Smakov <span style="font-style: italic;">et al.</span> have published the <a onclick="window.open(this.href, '_blank'); return false;" href="http://kernel-handbook.alioth.debian.org/">Debian Linux Kernel Handbook,</a> which documentswill help in documenting the internals of the Debian Linux Kernel build process. The document is still work in progress.</p> <p>Even though the kernel team does not use kernel-package, the document surely contains a great amount of useful or interesting information.<br /></p>
-
<p><a href="/readers/changes/netcraft.com" target="_blank">Netcraft</a> has determined Debian again to be <a href="http://news.netcraft.com/archives/2005/12/05/strong_growth_for_debian.html" target="_blank">the fastest growing Linux distribution</a> (on web servers) in 2005.</p>
-
<p>Biella Coleman, a Ph.D. from Chicago University (see <a href="http://www.onlinepolicy.org/about/bio/coleman.shtml" target="_blank">a short biography</a>), has the <a href="http://lists.debian.org/debian-project/2005/08/msg00206.html" target="_blank">announced the release</a> of a chapter from her <a target="_blank" href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=805287">dissertation on the ethics and politics of the free software movement</a>. The chapter, titled "Three ethical moments in Debian: the making of an ethical hacker part III", is the result of years of research with and within the Debian project. It is a recommended read for anyone interested in the inner workings of the Debian community, and complements the description of the community in chapter 2.4 on pages 46ff. You can download the chapter from <a target="_blank" href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=805287">this page</a>. </p>
-
Steve Kemp has documented <a target="_blank" href="http://people.debian.org/~skx/team.html">the workings of the Debian security team</a> online for public consumption.<br/>
-
<p>In section 5.11.10, the <span class="Code">popularity-contest</span> package is introduced as a programme sending email to a central server that aggregates the data and generates statistics. Future versions of popularity-contest can optionally use the HTTP protocol as well and thus do not require a mail transport agent (such as <span class="Code">exim4</span>) to be installed on every system that gathers statistics.</p>
-
<p>The first item in the list on page 260 in section 5.12.2 speaks of a change in the naming scheme of the Debian kernel packages. Starting with the 2.6.12 kernel packages, the Debian Kernel Team has started using <span class="Code">linux-*</span> for the packages containing Linux kernel files.</p>
-
<p>Chapter 9.2.1 discusses the structure of Debian source packages. Following the release of Debian <span style="font-style: italic;">sarge</span>, a new package format will replace the current one. The new format, dubbed "Wig and Pen" (version 2.0) is fully compatible with the current format (1.0), but adds the ability for multiple tarballs to encapsulate different aspects of the package (feature branches). In particular, it is now possible to distribute the Debian-specific files in a separate tarball rather than encapsulating them in a patch.</p> <p> More information about the new source package format may be found on the <a target="_blank" href="http://www.dpkg.org/NewSourceFormat">dpkg.org website</a>.</p>
-
<p>On 3 January 2006, a new archive signing key for the main Debian archive was put in place. The following are the relevant data to help you verify it.</p> <pre> URL: http://ftp-master.debian.org/ziyi_key_2006.asc<br /> ID: 2d230c5f<br /> Date: 2003-01-03<br />Fingerprint: 0847 50fc 01a6 d388 a643 d869 0109 0831 2d23 0c5f<br /> Creator: Anthony Towns (key 0x2a4e3eaa) </pre> <p>As in the book, <span style="font-weight: bold;">this information comes without any warranty</span>.<br /></p>
-
<p>Joey Hess added <a target="_blank" href="http://wiki.debian.org/SecureApt">a page</a> to the <a href="http://wiki.debian.org">Debian Wiki</a> with the goal to better document APT 0.6, aka. Secure APT. This should augment the information you can find in section 7.5.2.<br /></p>
-
<p>The semi-official Debian Wiki at <a target="_blank" href="http://wiki.debian.net">http://wiki.debian.net</a> now has a successor over at <a target="_blank" href="http://wiki.debian.org">http://wiki.debian.org</a>, which would finally make the Debian Wiki an official resource.</p>
-
<p>In chapter 5.7.2, <span class="Code">postfix-tls</span> is used in an example to show how diverted files work. The package is also used in various other parts of the book. While the package exists in <span style="font-style: italic;">sarge</span>, it has been removed from the archive for <span style="font-style: italic;">etch</span>. Its functionality has been integrated into the <span class="Code">postfix</span> package. The theory of diverted files continues to hold.</p>
-
<p>Chapter 5.4 introduces APT, and the Debian way of installing, removing, and upgrading packages. The traditional front-end to APT, <span class="Code">apt-get</span>, may in the future be replaced by <span class="Code">aptitude</span>, which implements most of the command-line options of <span class="Code">apt-get</span> (see p. 195f) and is thus a viable drop-in replacement. The sarge release notes recommend using <span class="Code">aptitude</span> instead of <span class="Code">apt-get</span>, as it "makes safer decisions about package installations than running <span class="Code">apt-get</span> directly."
-
<p>Section 10.6.9 states that single bug subscriptions are not yet possible and promises for this (frequently requested) feature to be available soon. Thanks to the work of Joachim Breitner, Don Armstrong, Pascal Hakim, Anthony Towns, and Colin Watson (hope I have not left anyone out), it is now possible to subscribe to single bug reports. Please see the <a target="_blank" href="http://lists.debian.org/debian-devel-announce/2005/07/msg00014.html">developer announcement</a> and the <a href="http://www.debian.org/Bugs/Developer#subscribe" target="_blank">documentation</a> for more information.</p>
-
<p>Following the release of <span style="font-style: italic;">sarge</span>, the Debian debbugs team has added the ability to track package versions instead of just single packages with the Debian bug tracking system. This has been a feature much requested, which should greatly facilitate the period leading up to an official Debian release.<br/> </p> <p>Details of the added and changed features and commands can be found in <a href="http://lists.debian.org/debian-devel-announce/2005/07/msg00010.html" target="_blank">the announcement</a>.<br/> </p>
-
-
-
<p>Item 3 in section 3.3.4 states: "If the file [.xsession] is present, ./.Xsession is tried."<br/> This should be: "If the file [.xsession] is <span style="font-style: italic;">not</span> present, ./.Xsession is tried."</p>
-
<p>The first text paragraph on page 373 in section 7.5.1 talks about the archive key, which was signed by one of the FTP masters, Anthony Towns. Later in the paragraph, Anthony suddenly becomes James. It should just say Anthony all along</p>
-
<p>The versioning scheme for pre-release upstream versions proposed in section 5.7.5 is not desirable: encoding the pre-release version in the Debian revision prevents a new orig.tar.gz file from being uploaded when the final release is uploaded.</p> <p>The following rewrite should make the situation clear. It replaces the second half of the middle paragraphon page 218, starting at "Within the Debian archive, it is customary...":</p> <p style="margin-left: 40px;">One scheme could be to release <span class="Code">1.0-rc1</span> as <span class="Code">1.0-0+1.0rc1+1,</span> followed by <span class="Code">1.0-0+1.0rc1+2,</span> and then <span class="Code">1.0-1</span> when the final gets released. However, this approach has an inherent problem: for each upstream version, an <span class="Code">orig.tar.gz</span> file exists in the Debian archive; Debian revisions are released as <span class="Code">diff.gz</span> files against the <span class="Code">orig.tar.gz</span> file (see chapter 9.2.12). In the proposed scheme, the <span class="Code">orig.tar.gz</span> file will contain the <span class="Code">1.0-rc1</span> upstream release, and when the final <span class="Code">1.0</span> release is to be packaged, the <span class="Code">diff.gz</span> file for the <span class="Code">1.0-1</span> Debian release will have to encompass all upstream changes between <span class="Code">1.0-rc1</span> and <span class="Code">1.0</span> as well, which is undesirable.</p> <p style="margin-left: 40px;">Thus, a better approach is to encode the pre-release version as part of the upstream vesion. This can be done in one of two ways: using the previous upstream version as base (let's assume <span class="Code">0.90</span>), or an obviously fake upstream version that sorts before the final release: <span class="Code">0.90+1.0rc1-1</span> or <span class="Code">0.999+1.0rc1-1</span>. Now, upon release of <span class="Code">1.0</span>, a new <span class="Code">orig.tar.gz</span> file can be uploaded to replace the previous one. With that in mind, it should be easy to infer the upstream version number from the Debian version, even in complex cases.<br /></p>
-
<p>Section 1.4.2 talks about anticipated changes to the Debian project and system. As should become apparent when reading section 4.3.3, such changes are <span style="font-style: italic;">not</span> to be expected in the <span style="font-style: italic;">stable</span> release of the operating system, which is one of its main selling points. Thus, if you only track <span style="font-style: italic;">stable</span> and have no interest in the surrounding project or new developments, you need not be concerned with these changes.<br/> </p> <p>I keep a <a href="/readers/changes">list of changes</a> online to make it easier for you to track developments since the book's release.</p>
-
<p>The first example on page 278 in section 6.1.4 contains a repeated instruction. You can ignore all code after the second command, <span class="Code">update-alternatives --display editor</span>, and its output.<br /></p>
-
<p>In the second sentence of the first item of the list on page 471 in section 9.2, the command should have been <span class="Code">dh_install</span>, not <span class="Code">dg_install</span>.</p>
-
<p>The command referenced in the third row of table 6.1 should be <span class="Code">adduser</span>, not <span class="Code">aduser</span>.</p>
-
<p>The item on components on the top of page 166 states that components "also specify when <span class="Code">non-US</span> software is to be used."</p> <p>This should say "non-free software" instead. Components cannot be used to select <span class="Code">non-US</span> software.<br /></p>
-
<p>The fourth paragraph of the subsection entitled "The early days" in "A history lesson" states that Debian <span style="font-style: italic;">rex</span> was released in December "of the same year". This refers to the release of <span style="font-style: italic;">buzz</span> in June 1996, not the release of the Debian botch in December 1995. <span style="font-style: italic;">rex</span> was released in December 1996.</p>
-
<p>Deborphaner is not iterative (or recursive, depending on how you look at it). In one run it may suggest to remove a set of packages, but it fails to identify packages that would be obsolete if the user removed the packages suggested in the first run.</p>
-
<p>The <span class="Code">apt.conf</span> examples on page 169, which illustrate the two different syntax styles, list <span class="Code">Default-Release</span> under the wrong namespace. Instead of <span class="Code">APT::Get</span>, it should just be <span class="Code">APT</span>:</p> <pre>APT::Default-Release "sarge";<br />[...]<br /></pre> <p>and:</p> <pre>APT {<br /> [...]<br /> Default-Release "sarge";<br /> [...]<br />}<br /></pre>
-
<p>In the first paragraph of the subsection titled "Obtaining source package" talks about the two types of source packages in the Debian archive: packages requiring modifications prior to their inclusion in Debian, and packages included directly. The text calls the former the class of "native packages" and terms the latter as "normal packages." It should be the other way around.</p>
-
<p>In chapter 5.3.7, I state:</p> <blockquote>Since <span class="Code">dpkg</span> remembers the administrators request to install <span class="Code">postfix</span>, it will retry and automatically complete the installation as soon as the dependencies are fulfilled.</blockquote> <p>This is not correct. dpkg sets the desired state of the <span class="Code">postfix</span> package to "install", but it does not automatically configure it when <span class="Code">netbase</span> is installed.<br/> </p>
-
<p>At the end of section 5.3.2, I claim that <span class="Code">dpkg</span> does not report an error when asked to configure an already configured package. In fact, <span class="Code">dpkg</span> does report an error:</p> <pre>~# dpkg --configure postfix [300]<br />dpkg: error processing postfix (--configure):<br /> package postfix is already installed and configured<br />Errors were encountered while processing:<br /> postfix<br /></pre>
-
<p>The example displaying the use of the <span class="Code">--showformat</span> option to <span class="Code">dpkg-query</span> should obviously be:<br/> </p> <pre># dpkg-query --show --showformat='${Package}\t${Status}\n' postfix postfix install ok installed</pre> <p>In the book, it unfortunately specifies <span class="Code">mc</span> as the last argument in the command line. I had previously used <span class="Code">mc</span> as an example, but switched almost all examples over to <span class="Code">postfix</span> as a tribute to my <a href="http://postfix.org" target="_blank">favourite mail server</a>, and its author, Wietse Venema.</p>
-
<p>The dwarfs-debian-guide package no longer exists in the <span style="font-style: italic;">sarge</span> archive. It has been removed in December 2003 by reason of being out of date (according to <a target="_blank" href="http://ftp-master.debian.org/removals.txt">removals.txt</a>).</p>
-
The last sentence of the "Into the next millenium" subsection should not be there. It was overlooked during the time we were waiting for <span style="font-style: italic;">sarge</span> to release.<br/>
-
<p>In chapter 6.3.1, I suggest to add <span class="Code">sshd</span> to the <span class="Code">/etc/inittab</span> file to be able to login to a remote system even in single-user mode:</p> <pre># sed -i -e "/^~~/ish:S:respawn:sshd -Do 'AllowUsers=root'" /etc/inittab</pre> <p>Unfortunately, there are two errors with this: first, <span class="Code">sshd</span> must be called with the complete path (to guard against trojans), and <span class="Code">init</span> must be told to reload the configuration file after the change.</p> <p>The following corrects both problems:<br /></p> <pre># sed -i -e "/^~~/ish:S:respawn:/usr/sbin/sshd -Do 'AllowUsers=root'" /etc/inittab<br /># telinit q</pre>
-
<p>In chapter 2.2.2, Free Software is incorrectly described as a subset of Open Source: while it is true that there are there Open Source licenses which are not FSF-Free or not approved by Debian, that is a matter of interpretation, not of principles, as the <a href="http://www.opensource.org/docs/definition.php" target="_blank">Open Source Definition</a> and the <a href="http://www.debian.org/social_contract#guidelines" target="_blank">Debian Free Software Guidelines</a> match almost word for word.</p>
-
<p>The last sentence of A.2.3 states that Gnoppix is the basis for the Ubuntu Live CD. This is not accurate. Andreas Müller, the developer of Gnoppix, actually developed the Ubuntu Live CD first, and then reused this work for Gnoppix. Thus, Gnoppix is based on the Ubuntu Live CD, not <span style="font-style: italic;">vice versa</span>.</p>
-
-