blog/index.rss

   1 <?xml version="1.0" encoding="utf-8"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
   3         <channel>
   4                 <title>Petter Reinholdtsen</title>
   5                 <description></description>
   6                 <link>http://people.skolelinux.org/pere/blog/</link>
   7                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
   8
   9         <item>
  10                 <title>First Debian Edu test release (alpha0) based on Squeeze is released</title>
  11                 <link>http://people.skolelinux.org/pere/blog/First_Debian_Edu_test_release__alpha0__based_on_Squeeze_is_released.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_Debian_Edu_test_release__alpha0__based_on_Squeeze_is_released.html</guid>
  13                 <pubDate>Tue, 27 Jul 2010 17:45:00 +0200</pubDate>
  14                 <description>
  15 &lt;p&gt;I just posted this announcement culminating several months of work
  16 with the next Debian Edu release.  Not nearly done, but one major step
  17 completed.&lt;/p&gt;
  18
  19 &lt;blockquote&gt;
  20 &lt;p&gt;This is the first test release based on Squeeze. The focus of this
  21 release is to test the user application selection. To have a look,
  22 install the standalone profile and let the developers know if the set
  23 of installed packages i.e. applications should be modified. If some
  24 user application is missing, or if there are some applications that no
  25 longer make sense to be included in Debian Edu, please let us know.
  26 Also, if a useful application is missing the translation for your
  27 language of choice, please let us know too.&lt;/p&gt;
  28
  29 &lt;p&gt;In addition, feedback and help to polish the desktop (menus,
  30 artwork, starters, etc.) is appreciated. We would like to ship a nice
  31 and handy KDE4 desktop targeted for schools out of the box.&lt;/p&gt;
  32
  33 &lt;p&gt;The other profiles should be installable, but there is a lot more
  34 work left to be done before they are ready, so do not expect to
  35 much.&lt;/p&gt;
  36
  37 &lt;p&gt;Changes compared to the lenny based version&lt;/p&gt;
  38
  39 &lt;ul&gt;
  40 &lt;li&gt;Everything from Debian Squeeze
  41 &lt;ul&gt;
  42   &lt;li&gt;Desktop environment KDE 4.4 =&gt; the new KDE desktop in
  43          combination with some new artwork
  44   &lt;li&gt;Web browser Iceweasel 3.5
  45   &lt;li&gt;OpenOffice.org 3.2
  46   &lt;li&gt;Educational toolbox GCompris 9.3
  47   &lt;li&gt;Music creator Rosegarden 10.04.2
  48   &lt;li&gt;Image editor Gimp 2.6.10
  49   &lt;li&gt;Virtual universe Celestia 1.6.0
  50   &lt;li&gt;Virtual stargazer Stellarium 0.10.4
  51   &lt;li&gt;3D modeler Blender 2.49.2 (new application)
  52   &lt;li&gt;Video editor Kdenlive 0.7.7 (new application)
  53 &lt;/ul&gt;&lt;/li&gt;
  54 &lt;li&gt;Now using Kerberos for password checking (migration not finished).
  55     Enabled for:
  56 &lt;ul&gt;
  57   &lt;li&gt;PAM
  58   &lt;li&gt;LDAP
  59   &lt;li&gt;IMAP
  60   &lt;li&gt;SMTP (sender verification)
  61 &lt;/ul&gt;
  62 &lt;/li&gt;
  63 &lt;li&gt;New experimental roaming workstation profile for laptops.&lt;/li&gt;
  64 &lt;li&gt;Show welcome page to users when they first log in. The URL is
  65     fetched from LDAP.&lt;/li&gt;
  66 &lt;li&gt;New LXDE desktop option, in addition to KDE (default) and Gnome.&lt;/li&gt;
  67 &lt;li&gt;General cleanup (not finished)&lt;/li&gt;
  68 &lt;/ul&gt;
  69 &lt;p&gt;The following features are not working as they should&lt;/p&gt;
  70
  71 &lt;ul&gt;
  72 &lt;li&gt;No web based administration tool for creating users and groups. The
  73     scripts ldap-createuser-krb and ldap-add-user-to-group can be used
  74     for testing.&lt;/li&gt;
  75 &lt;li&gt;DVD installs are missing debian-installer images for the PXE boot,
  76     and do not set up the PXE menu on eth0 because of this. LTSP
  77     clients should still boot from eth1 on thin client servers.&lt;/li&gt;
  78 &lt;li&gt;The restructured KDE menu is not implemented.&lt;/li&gt;
  79 &lt;li&gt;The LDAP server setup need to be reviewed for security.&lt;/li&gt;
  80 &lt;li&gt;The LDAP directory structure need to be reworked.&lt;/li&gt;
  81 &lt;li&gt;Different sets of packages are installed when using the DVD and the
  82     netinst CD. More packages are installed using the netinst CD.&lt;/li&gt;
  83 &lt;li&gt;The jackd package fail to install. This is believed to be caused by
  84     some ongoing transition, and hopefully should be solved soon. The
  85     jackd1 package can be installed manually for those that need it.&lt;/li&gt;
  86 &lt;li&gt;Some packages lack translations. See
  87     http://wiki.debian.org/DebianEdu/Status/Squeeze for updated status,
  88     and help out with translations.&lt;/li&gt;
  89 &lt;/ul&gt;
  90
  91 &lt;p&gt;To download this multiarch netinstall release you can use&lt;/p&gt;
  92
  93 &lt;ul&gt;
  94 &lt;li&gt;&lt;a href=&quot;ftp://ftp.skolelinux.org/skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-CD.iso&quot;&gt;ftp://ftp.skolelinux.org/skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-CD.iso&lt;/a&gt;&lt;/li&gt;
  95 &lt;li&gt;&lt;a href=&quot;http://ftp.skolelinux.org/skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-CD.iso&quot;&gt;http://ftp.skolelinux.org/skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-CD.iso&lt;/a&gt;&lt;/li&gt;
  96 &lt;li&gt;rsync -avzP ftp.skolelinux.org::skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-CD.iso&lt;/li&gt;
  97 &lt;/ul&gt;
  98 &lt;p&gt;To download this multiarch dvd release you can use&lt;/p&gt;
  99
 100 &lt;ul&gt;
 101 &lt;li&gt;&lt;a href=&quot;ftp://ftp.skolelinux.org/skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-DVD.iso&quot;&gt;ftp://ftp.skolelinux.org/skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-DVD.iso&lt;/a&gt;&lt;/li&gt;
 102 &lt;li&gt;&lt;a href=&quot;http://ftp.skolelinux.org/skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-DVD.iso&quot;&gt;http://ftp.skolelinux.org/skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-DVD.iso&lt;/a&gt;&lt;/li&gt;
 103 &lt;li&gt;rsync -avzP ftp.skolelinux.org::skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-DVD.iso&lt;/li&gt;
 104 &lt;/ul&gt;
 105
 106 &lt;p&gt;There is no source DVD available yet. It will be prepared when we
 107 get closer to the final release.&lt;/p&gt;
 108
 109 &lt;p&gt;The MD5SUM of these images are&lt;/p&gt;
 110
 111 &lt;ul&gt;
 112 &lt;li&gt;3dbf45d59f42a53518b6e3c9ec3b5eb6 debian-edu-6.0.0+edua0-CD.iso&lt;/li&gt;
 113 &lt;li&gt;22f2cbfce281d1c6e478be452638675d debian-edu-6.0.0+edua0-DVD.iso&lt;/li&gt;
 114 &lt;/ul&gt;
 115
 116 &lt;p&gt;The SHA1SUM of these images are&lt;/p&gt;
 117 &lt;ul&gt;
 118 &lt;li&gt;c53d1b69b40cf37cd27aefaf33f6f6a3821bedf0 debian-edu-6.0.0+edua0-CD.iso&lt;/li&gt;
 119 &lt;li&gt;2ec29d7db676d59d32197b05c277ffe16348376c debian-edu-6.0.0+edua0-DVD.iso&lt;/li&gt;
 120 &lt;/ul&gt;
 121 &lt;p&gt;How to report bugs:
 122 http://wiki.debian.org/DebianEdu/HowTo/ReportBugsInBugzilla&lt;/p&gt;
 123
 124 &lt;p&gt;Please direct replies to debian-edu@lists.debian.org&lt;/p&gt;
 125 &lt;/blockquote&gt;
 126 </description>
 127         </item>
 128
 129         <item>
 130                 <title>One step closer to single signon in Debian Edu</title>
 131                 <link>http://people.skolelinux.org/pere/blog/One_step_closer_to_single_signon_in_Debian_Edu.html</link>
 132                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_step_closer_to_single_signon_in_Debian_Edu.html</guid>
 133                 <pubDate>Sun, 25 Jul 2010 10:00:00 +0200</pubDate>
 134                 <description>
 135 &lt;p&gt;The last few months me and the other Debian Edu developers have
 136 been working hard to get the Debian/Squeeze based version of Debian
 137 Edu/Skolelinux into shape.  This future version will use Kerberos for
 138 authentication, and services are slowly migrated to single signon,
 139 getting rid of password questions one at the time.&lt;/p&gt;
 140
 141 &lt;p&gt;It will also feature a roaming workstation profile with local home
 142 directory, for laptops that are only some times on the Skolelinux
 143 network, and for this profile a shortcut is created in Gnome and KDE
 144 to gain access to the users home directory on the file server.  This
 145 shortcut uses SMB at the moment, and yesterday I had time to test if
 146 SMB mounting had started working in KDE after we added the cifs-utils
 147 package.  I was pleasantly surprised how well it worked.&lt;/p&gt;
 148
 149 &lt;p&gt;Thanks to the recent changes to our samba configuration to get it
 150 to use Kerberos for authentication, there were no question about user
 151 password when mounting the SMB volume.  A simple click on the shortcut
 152 in the KDE menu, and a window with the home directory popped
 153 up. :)&lt;/p&gt;
 154
 155 &lt;p&gt;One step closer to a single signon solution out of the box in
 156 Debian Edu.  We already had PAM, LDAP, IMAP and SMTP in place, and now
 157 also Samba.  Next step is Cups and hopefully also NFS.&lt;/p&gt;
 158
 159 &lt;p&gt;We had planned a alpha0 release of Debian Edu for today, but thanks
 160 to the autobuilder administrators for some architectures being slow to
 161 sign packages, we are still missing the fixed LTSP package we need for
 162 the release.  It was uploaded three days ago with urgency=high, and if
 163 it had entered testing yesterday we would have been able to test it in
 164 time for a alpha0 release today.  As the binaries for ia64 and powerpc
 165 still not uploaded to the Debian archive, we need to delay the alpha
 166 release another day.&lt;/p&gt;
 167
 168 &lt;p&gt;If you want to help out with implementing Kerberos for Debian Edu,
 169 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
 170 </description>
 171         </item>
 172
 173         <item>
 174                 <title>Digitale restriksjonsmekanismer fikk meg til å slutte å kjøpe musikk</title>
 175                 <link>http://people.skolelinux.org/pere/blog/Digitale_restriksjonsmekanismer_fikk_meg_til____slutte____kj__pe_musikk.html</link>
 176                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Digitale_restriksjonsmekanismer_fikk_meg_til____slutte____kj__pe_musikk.html</guid>
 177                 <pubDate>Thu, 22 Jul 2010 23:50:00 +0200</pubDate>
 178                 <description>
 179 &lt;p&gt;For mange år siden slutte jeg å kjøpe musikk-CDer. Årsaken var at
 180 musikkbransjen var godt i gang med å selge platene sine med DRM som
 181 gjorde at jeg ikke fikk spilt av musikken jeg kjøpte på utstyret jeg
 182 hadde tilgjengelig, dvs. min datamaskin. Det var umulig å se på en
 183 plate om den var ødelagt eller ikke, og jeg hadde jo allerede en
 184 anseelig samling med plater, så jeg bestemme meg for å slutte å gi
 185 penger til en bransje som åpenbart ikke respekterte meg.&lt;/p&gt;
 186
 187 &lt;p&gt;Jeg har mange titalls dager med musikk på CD i dag. Det meste er
 188 lagt i et stort arkiv som kan spilles av fra husets datamaskiner (har
 189 ikke rukket rippe alt). Jeg ser dermed ikke behovet for å skaffe mer
 190 musikk. De fleste av mine favoritter er i hus, og jeg er dermed godt
 191 fornøyd.&lt;/p&gt;
 192
 193 &lt;p&gt;Hvis musikkbransjen ønsker mine penger, så må de demonstrere at de
 194 setter pris på meg som kunde, og ikke skremme meg bort med DRM og
 195 antydninger om at kundene er kriminelle.&lt;/p&gt;
 196
 197 &lt;p&gt;Filmbransjen er like ille, men mens musikk gjerne varer lenge, er
 198 filmer mer ferskvare. Har dermed ikke helt sluttet å kjøpe filmer, men
 199 holder meg til DVD-filmer som kan spilles av på mine Linuxbokser.
 200 Kommer neppe til å ta i bruk Blueray, og ei heller de nye DRM-greiene
 201 «Ultraviolet» som be annonsert her om dagen.&lt;/p&gt;
 202 </description>
 203         </item>
 204
 205         <item>
 206                 <title>OpenStreetmap one step closer to having routing on its front page</title>
 207                 <link>http://people.skolelinux.org/pere/blog/OpenStreetmap_one_step_closer_to_having_routing_on_its_front_page.html</link>
 208                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenStreetmap_one_step_closer_to_having_routing_on_its_front_page.html</guid>
 209                 <pubDate>Sun, 18 Jul 2010 16:45:00 +0200</pubDate>
 210                 <description>
 211 &lt;p&gt;Thanks to
 212 &lt;a href=&quot;http://feedproxy.google.com/~r/Opengeodata/~3/wUTCzDZk3lc/project-of-the-week-which-way-home&quot;&gt;todays
 213 opengeodata blog entry&lt;/a&gt;, I just discovered that the
 214 OpenStreetmap.org site have gotten
 215 &lt;a href=&quot;http://nroets.dev.openstreetmap.org/demo/index.html?layers=B000FTFTT&quot;&gt;support
 216 for calculating routes&lt;/a&gt;.  The support is still experimental and
 217 only available from the development server, until more experience is
 218 gathered on the user interface and any scalability issues.&lt;/p&gt;
 219
 220 &lt;p&gt;Earlier, the routing I knew about using the OpenStreetmap.org data
 221 was provided by &lt;a href=&quot;http://maps.cloudmade.com/&quot;&gt;Cloudmade&lt;/a&gt;,
 222 but having it on the main page is required to make everyone aware of
 223 the issue.  I&#39;ve had people reject Openstreetmap.org as a viable
 224 alternative for them because the front page lacked routing support,
 225 and I hope their needs will be catered for when routing show up on the
 226 www.openstreetmap.org front page.&lt;/p&gt;
 227 </description>
 228         </item>
 229
 230         <item>
 231                 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
 232                 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
 233                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
 234                 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
 235                 <description>
 236 &lt;p&gt;This is a
 237 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;followup&lt;/a&gt;
 238 on my
 239 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html&quot;&gt;previous
 240 work&lt;/a&gt; on
 241 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
 242 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
 243
 244 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
 245 LDAP objects, I have had a look at how the packages pdns-backend-ldap
 246 and dhcp3-server-ldap in Debian use the LDAP server.  The two
 247 implementations are quite different in how they use LDAP.&lt;/p&gt;
 248
 249 To get this information, I started slapd with debugging enabled and
 250 dumped the debug output to a file to get the LDAP searches performed
 251 on a Debian Edu main-server.  Here is a summary.
 252
 253 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
 254
 255 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
 256 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
 257 the web.
 258
 259 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
 260 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
 261 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
 262 reverse entries are in two different subtrees in LDAP with a structure
 263 based on the DNS names, as in tjener.intern and
 264 2.2.0.10.in-addr.arpa.&lt;/p&gt;
 265
 266 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
 267 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
 268 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
 269 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
 270 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
 271 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry.  For
 272 forward entries, it is looking for attributes named dnsttl, arecord,
 273 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
 274 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
 275 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
 276 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
 277 spfrecord and modifytimestamp.  For reverse entries it is looking for
 278 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
 279 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
 280 locrecord, srvrecord, naptrrecord and modifytimestamp.  The equivalent
 281 ldapsearch commands could look like this:&lt;/p&gt;
 282
 283 &lt;blockquote&gt;&lt;pre&gt;
 284 ldapsearch -h ldap \
 285   -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
 286   -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
 287   cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
 288   rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
 289   nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
 290   rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
 291
 292 ldapsearch -h ldap \
 293   -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
 294   -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
 295   dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
 296   hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
 297   srvrecord naptrrecord modifytimestamp
 298 &lt;/pre&gt;&lt;/blockquote&gt;
 299
 300 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
 301 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
 302 example LDAP objects used there.  In addition to these objects, the
 303 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
 304 also exist.&lt;/p&gt;
 305
 306 &lt;blockquote&gt;&lt;pre&gt;
 307 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
 308 objectclass: top
 309 objectclass: dnsdomain
 310 objectclass: domainrelatedobject
 311 dc: tjener
 312 arecord: 10.0.2.2
 313 associateddomain: tjener.intern
 314
 315 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
 316 objectclass: top
 317 objectclass: dnsdomain2
 318 objectclass: domainrelatedobject
 319 dc: 2
 320 ptrrecord: tjener.intern
 321 associateddomain: 2.2.0.10.in-addr.arpa
 322 &lt;/pre&gt;&lt;/blockquote&gt;
 323
 324 &lt;p&gt;In strict mode, the server behaves differently.  When looking for
 325 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
 326 same base as in the tree mode for a object with filter
 327 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
 328 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
 329 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
 330 naptrrecord and modifytimestamp.  For reverse entires it also do a
 331 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
 332 and the requested attributes are associateddomain, dnsttl and
 333 modifytimestamp.  In short, in strict mode the objects with ptrrecord
 334 go away, and the arecord attribute in the forward object is used
 335 instead.&lt;/p&gt;
 336
 337 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
 338 like this:&lt;/p&gt;
 339
 340 &lt;blockquote&gt;&lt;pre&gt;
 341 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
 342   &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
 343   cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
 344   rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
 345   nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
 346   rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
 347
 348 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
 349   &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
 350 &lt;/pre&gt;&lt;/blockquote&gt;
 351
 352 &lt;p&gt;In addition to the forward and reverse searches , there is also a
 353 search for SOA records, which behave similar to the forward and
 354 reverse lookups.&lt;/p&gt;
 355
 356 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
 357 specify any objectclass names, and instead look for the attributes it
 358 need to generate a DNS reply.  This make it able to work with any
 359 objectclass that provide the needed attributes.&lt;/p&gt;
 360
 361 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
 362 dnsdomain2 schemas.  The latter is used for reverse entries like
 363 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
 364
 365 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
 366 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
 367 attributes) and domainrelatedobject (for associatedDomain).  The use
 368 of structural object classes make it impossible to combine these
 369 classes with the object classes used by DHCP.&lt;/p&gt;
 370
 371 &lt;p&gt;There are other schemas that could be used too, for example the
 372 dnszone structural object class used by Gosa and bind-sdb for the DNS
 373 attributes combined with the domainrelatedobject object class, but in
 374 this case some unused attributes would have to be included as well
 375 (zonename and relativedomainname).&lt;/p&gt;
 376
 377 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
 378 mode and not use any of the existing objectclasses (dnsdomain,
 379 dnsdomain2 and dnszone) when one want to combine the DNS information
 380 with DHCP information, and instead create a auxiliary object class
 381 defined something like this (using the attributes defined for
 382 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
 383
 384 &lt;blockquote&gt;&lt;pre&gt;
 385 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
 386     SUP top
 387     AUXILIARY
 388     MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
 389           DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
 390           TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
 391           NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
 392           A6Record $ DNAMERecord
 393     ))
 394 &lt;/pre&gt;&lt;/blockquote&gt;
 395
 396 &lt;p&gt;This will allow any object to become a DNS entry when combined with
 397 the domainrelatedobject object class, and allow any entity to include
 398 all the attributes PowerDNS wants.  I&#39;ve sent an email to the PowerDNS
 399 developers asking for their view on this schema and if they are
 400 interested in providing such schema with PowerDNS, and I hope my
 401 message will be accepted into their mailing list soon.&lt;/p&gt;
 402
 403 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
 404
 405 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
 406 the object attributes, and then uses the attributes it want.  This
 407 make it harder to figure out exactly what attributes are used, but
 408 thanks to the working example in Debian Edu I can at least get an idea
 409 what is needed without having to read the source code.&lt;/p&gt;
 410
 411 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
 412 search filter to use to locate the correct dhcpServer entity is
 413 stored.  These are the relevant entries from
 414 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
 415
 416 &lt;blockquote&gt;&lt;pre&gt;
 417 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
 418 ldap-dhcp-server-cn &quot;dhcp&quot;;
 419 &lt;/pre&gt;&lt;/blockquote&gt;
 420
 421 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
 422 configuration it need.  The cn &quot;dhcp&quot; is located using the given LDAP
 423 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;.  The
 424 search result is this entry:&lt;/p&gt;
 425
 426 &lt;blockquote&gt;&lt;pre&gt;
 427 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
 428 cn: dhcp
 429 objectClass: top
 430 objectClass: dhcpServer
 431 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
 432 &lt;/pre&gt;&lt;/blockquote&gt;
 433
 434 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
 435 subtree with DHCP configuration.  The DHCP configuration subtree base
 436 is located using a base scope search with base &quot;cn=DHCP
 437 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
 438 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
 439 The search result is this entry:&lt;/p&gt;
 440
 441 &lt;blockquote&gt;&lt;pre&gt;
 442 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
 443 cn: DHCP Config
 444 objectClass: top
 445 objectClass: dhcpService
 446 objectClass: dhcpOptions
 447 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
 448 dhcpStatements: ddns-update-style none
 449 dhcpStatements: authoritative
 450 dhcpOption: smtp-server code 69 = array of ip-address
 451 dhcpOption: www-server code 72 = array of ip-address
 452 dhcpOption: wpad-url code 252 = text
 453 &lt;/pre&gt;&lt;/blockquote&gt;
 454
 455 &lt;p&gt;Next, the entire subtree is processed, one level at the time.  When
 456 all the DHCP configuration is loaded, it is ready to receive requests.
 457 The subtree in Debian Edu contain objects with object classes
 458 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
 459 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost.  These provide options
 460 and information about netmasks, dynamic range etc.  Leaving out the
 461 details here because it is not relevant for the focus of my
 462 investigation, which is to see if it is possible to merge dns and dhcp
 463 related computer objects.&lt;/p&gt;
 464
 465 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
 466 of the client (00:00:00:00:00:00 in this example), using a subtree
 467 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
 468 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
 469 00:00:00:00:00:00))&quot; as the filter.  This is what a host object look
 470 like:&lt;/p&gt;
 471
 472 &lt;blockquote&gt;&lt;pre&gt;
 473 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
 474 cn: hostname
 475 objectClass: top
 476 objectClass: dhcpHost
 477 dhcpHWAddress: ethernet 00:00:00:00:00:00
 478 dhcpStatements: fixed-address hostname
 479 &lt;/pre&gt;&lt;/blockquote&gt;
 480
 481 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
 482 The object classes need to have fixed names, and the configuration
 483 need to be stored in a fairly specific LDAP structure.  On the
 484 positive side, the invidiual dhcpHost entires can be anywhere without
 485 the DN pointed to by the dhcpServer entries.  The latter should make
 486 it possible to group all host entries in a subtree next to the
 487 configuration entries, and this subtree can also be shared with the
 488 DNS server if the schema proposed above is combined with the dhcpHost
 489 structural object class.
 490
 491 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
 492
 493 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
 494 to which LDAP schemas to use.  While its &quot;tree&quot; mode is rigid when it
 495 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
 496 allowing DNS objects to be stored anywhere under the base cn specified
 497 in the configuration.&lt;/p&gt;
 498
 499 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
 500 regarding which LDAP schemas to use and which LDAP structure to use.
 501 I guess one could implement ones own schema, as long as the
 502 objectclasses and attributes have the names used, but this do not
 503 really help when the DHCP subtree need to have a fairly fixed
 504 structure.&lt;/p&gt;
 505
 506 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
 507 this might work for Debian Edu:&lt;/p&gt;
 508
 509 &lt;blockquote&gt;&lt;pre&gt;
 510 ou=services
 511   cn=machine-info (dhcpService) - dhcpServiceDN points here
 512     cn=dhcp (dhcpServer)
 513     cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
 514       cn=10.0.2.0 (dhcpSubnet)
 515         cn=group1 (dhcpGroup/dhcpOptions)
 516     cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
 517       cn=192.168.0.0 (dhcpSubnet)
 518         cn=group1 (dhcpGroup/dhcpOptions)
 519     ou=machines - PowerDNS base points here
 520       cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
 521 &lt;/pre&gt;&lt;/blockquote&gt;
 522
 523 &lt;P&gt;This is not tested yet.  If the DHCP server require the dhcpHost
 524 entries to be in the dhcpGroup subtrees, the entries can be stored
 525 there instead of a common machines subtree, and the PowerDNS base
 526 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
 527
 528 &lt;p&gt;The combined object under the machines subtree would look something
 529 like this:&lt;/p&gt;
 530
 531 &lt;blockquote&gt;&lt;pre&gt;
 532 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
 533 dc: hostname
 534 objectClass: top
 535 objectClass: dhcpHost
 536 objectclass: domainrelatedobject
 537 objectclass: dnsDomainAux
 538 associateddomain: hostname.intern
 539 arecord: 10.11.12.13
 540 dhcpHWAddress: ethernet 00:00:00:00:00:00
 541 dhcpStatements: fixed-address hostname.intern
 542 &lt;/pre&gt;&lt;/blockquote&gt;
 543
 544 &lt;/p&gt;One could even add the LTSP configuration associated with a given
 545 machine, as long as the required attributes are available in a
 546 auxiliary object class.&lt;/p&gt;
 547 </description>
 548         </item>
 549
 550         <item>
 551                 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
 552                 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
 553                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
 554                 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
 555                 <description>
 556 &lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
 557 DHCP services in Debian Edu to use the same LDAP objects for a given
 558 computer, to avoid the possibility of having a inconsistent state for
 559 a computer in LDAP (as in DHCP but no DNS entry or the other way
 560 around) and make it easier to add computers to LDAP.&lt;/p&gt;
 561
 562 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
 563 information finally found a solution that seem to work.&lt;/p&gt;
 564
 565 &lt;p&gt;The old setup required three LDAP objects for a given computer.
 566 One forward DNS entry, one reverse DNS entry and one DHCP entry.  If
 567 we switch powerdns to use its strict LDAP method (ldap-method=strict
 568 in pdns-debian-edu.conf), the forward and reverse DNS entries are
 569 merged into one while making it impossible to transfer the reverse map
 570 to a slave DNS server.&lt;/p&gt;
 571
 572 &lt;p&gt;If we also replace the object class used to get the DNS related
 573 attributes to one allowing these attributes to be combined with the
 574 dhcphost object class, we can merge the DNS and DHCP entries into one.
 575 I&#39;ve written such object class in the dnsdomainaux.schema file (need
 576 proper OIDs, but that is a minor issue), and tested the setup.  It
 577 seem to work.&lt;/p&gt;
 578
 579 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
 580 for both DNS and DHCP, and even the LTSP configuration I suggested in
 581 an earlier email.  The combined LDAP object will look something like
 582 this:&lt;/p&gt;
 583
 584 &lt;blockquote&gt;&lt;pre&gt;
 585   dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
 586   cn: hostname
 587   objectClass: dhcphost
 588   objectclass: domainrelatedobject
 589   objectclass: dnsdomainaux
 590   associateddomain: hostname.intern
 591   arecord: 10.11.12.13
 592   dhcphwaddress: ethernet 00:00:00:00:00:00
 593   dhcpstatements: fixed-address hostname
 594   ldapconfigsound: Y
 595 &lt;/pre&gt;&lt;/blockquote&gt;
 596
 597 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
 598 the DHCP server uses the dhcphwaddress and dhcpstatements entries
 599 before asking DNS to resolve the fixed-adddress.  LTSP will use
 600 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
 601
 602 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
 603 dhcphost in a different location, to allow us to put the objects
 604 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
 605 that.  If I can&#39;t figure out a way to do that, we can still get rid of
 606 the hosts subtree and move all its content into the DHCP Config tree
 607 (which probably should be renamed to be more related to the new
 608 content.  I suspect cn=dnsdhcp,ou=services or something like that
 609 might be a good place to put it.&lt;/p&gt;
 610
 611 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
 612 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
 613 </description>
 614         </item>
 615
 616         <item>
 617                 <title>Idea for storing LTSP configuration in LDAP</title>
 618                 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
 619                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
 620                 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
 621                 <description>
 622 &lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
 623 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
 624 clients, and that this can be used to fetch configuration from LDAP if
 625 Debian Edu choose to store configuration there.&lt;/p&gt;
 626
 627 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
 628 to get configuration from LDAP.  The idea is to look up the MAC
 629 address of the client in LDAP, and look for attributes on the form
 630 ltspconfigsetting=value, and use this to export SETTING=value to the
 631 LTSP clients.&lt;/p&gt;
 632
 633 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
 634 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
 635 allowing us to store all information about a computer in one place.&lt;/p&gt;
 636
 637 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
 638 this approach.  A real LDAP schema for the ltspClientAux objectclass
 639 need to be written.  Comments, suggestions, etc?&lt;/p&gt;
 640
 641 &lt;blockquote&gt;&lt;pre&gt;
 642 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
 643 #
 644 # Fetch LTSP client settings from LDAP based on MAC address
 645 #
 646 # Uses ethernet address as stored in the dhcpHost objectclass using
 647 # the dhcpHWAddress attribute or ethernet address stored in the
 648 # ieee802Device objectclass with the macAddress attribute.
 649 #
 650 # This module is written to be schema agnostic, and only depend on the
 651 # existence of attribute names.
 652 #
 653 # The LTSP configuration variables are saved directly using a
 654 # ltspConfig prefix and uppercasing the rest of the attribute name.
 655 # To set the SERVER variable, set the ltspConfigServer attribute.
 656 #
 657 # Some LDAP schema should be created with all the relevant
 658 # configuration settings.  Something like this should work:
 659 #
 660 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
 661 #     SUP top
 662 #     AUXILIARY
 663 #     MAY ( ltspConfigServer $ ltsConfigSound $ ... )
 664
 665 LDAPSERVER=$(debian-edu-ldapserver)
 666 if [ &quot;$LDAPSERVER&quot; ] ; then
 667     LDAPBASE=$(debian-edu-ldapserver -b)
 668     for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
 669         filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
 670         ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
 671             grep &#39;^ltspConfig&#39; | while read attr value ; do
 672             # Remove prefix and convert to upper case
 673             attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
 674             # bass value on to clients
 675             eval &quot;$attr=$value; export $attr&quot;
 676         done
 677     done
 678 fi
 679 &lt;/pre&gt;&lt;/blockquote&gt;
 680
 681 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
 682 the while block might end up in a subshell causing the variables set
 683 there to not show up in ltsp-config, but if that is the case I am sure
 684 the code can be restructured to make sure the variables are passed on.
 685 I expect that can be solved with some testing. :)&lt;/p&gt;
 686
 687 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
 688 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
 689
 690 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
 691 configuration in LDAP that was created around year 2000 by
 692 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
 693 Xperience, Inc., 2000&lt;/a&gt;.  I found its
 694 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
 695 personal home page over at redhat.com.&lt;/p&gt;
 696 </description>
 697         </item>
 698
 699         <item>
 700                 <title>jXplorer, a very nice LDAP GUI</title>
 701                 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
 702                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
 703                 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
 704                 <description>
 705 &lt;p&gt;Since
 706 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
 707 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
 708 LDAP GUI that is even better than luma.  The java application
 709 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
 710 moving LDAP objects and subtrees using drag-and-drop, and can
 711 authenticate using Kerberos.  I have only tested the Kerberos
 712 authentication, but do not have a LDAP setup allowing me to rewrite
 713 LDAP with my test user yet.  It is
 714 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
 715 Debian&lt;/a&gt; testing and unstable at the moment.  The only problem I
 716 have with it is how it handle errors.  If something go wrong, its
 717 non-intuitive behaviour require me to go through some query work list
 718 and remove the failing query.  Nothing big, but very annoying.&lt;/p&gt;
 719 </description>
 720         </item>
 721
 722         <item>
 723                 <title>MS Word krøller det til for politiet?</title>
 724                 <link>http://people.skolelinux.org/pere/blog/MS_Word_kr__ller_det_til_for_politiet_.html</link>
 725                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MS_Word_kr__ller_det_til_for_politiet_.html</guid>
 726                 <pubDate>Thu, 8 Jul 2010 14:00:00 +0200</pubDate>
 727                 <description>
 728 &lt;p&gt;De siste dagene har Aftenposten
 729 &lt;a href=&quot;http://www.aftenposten.no/nyheter/iriks/article3718597.ece&quot;&gt;fortalt&lt;/a&gt;
 730 &lt;a href=&quot;http://www.aftenposten.no/nyheter/iriks/article3724249.ece&quot;&gt;hvordan&lt;/a&gt;
 731 politet har brukt skriveverktøy som ikke håndterer arabisk tekst og
 732 tekst som skal skrives fra høyre mot venstre når de har laget
 733 løpeseddel for å be om informasjon fra publikum.  Resultatet har vært
 734 en uleselig arabisk-bit på løpeseddelen.  Feilen har oppstått når
 735 teksten har blitt &quot;kopiert inn i programvare som ikke har støtte for
 736 språk som skrives fra høyre mot venstre&quot;, og jeg er ganske sikker på
 737 at det er snakk om Microsoft Office i dette tilfellet.  Er det slik at
 738 MS Office i norsk språkdrakt ikke har støtte for tekst som skal
 739 skrives fra høyre mot venstre?  Jeg tror alle utgaver av
 740 OpenOffice.org har slik støtte, og det er jo ikke veldig vanskelig å
 741 la slik støtte finnes i alle utgaver av et program hvis støtten først
 742 er utviklet.  Aftenpostens melding får meg til å undre om problemet
 743 ville vært unngått hvis politiet brukte OpenOffice.org i stedet for MS
 744 Office.&lt;/p&gt;
 745
 746 &lt;p&gt;Mon tro om det er flere eksempler på at MS Office har ødelagt for
 747 offentlig myndighet?&lt;/p&gt;
 748 </description>
 749         </item>
 750
 751         <item>
 752                 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
 753                 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
 754                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
 755                 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
 756                 <description>
 757 &lt;p&gt;Here is a short update on my &lt;a
 758 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
 759 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;.  Here is a summary of the
 760 difference for Gnome when it is upgraded by apt-get and aptitude.  I&#39;m
 761 not reporting the status for KDE, because the upgrade crashes when
 762 aptitude try because of missing conflicts
 763 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
 764 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
 765
 766 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
 767 complete list of the installed packages.  Based on this I see these
 768 differences when I did a test run today.  As usual, I do not really
 769 know what the correct set of packages would be, but thought it best to
 770 publish the difference.&lt;/p&gt;
 771
 772 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
 773
 774 &lt;blockquote&gt;&lt;p&gt;
 775   at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
 776   libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
 777   libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
 778   libgtksourceview-common libpt-1.10.10-plugins-alsa
 779   libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
 780   libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
 781   python-4suite-xml python-eggtrayicon python-gtkhtml2
 782   python-gtkmozembed svgalibg1 xserver-xephyr zip
 783 &lt;/p&gt;&lt;/blockquote&gt;
 784
 785 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
 786
 787 &lt;blockquote&gt;&lt;p&gt;
 788   bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
 789   gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
 790   libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
 791   libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
 792   libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
 793   libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
 794   libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
 795   libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
 796   libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
 797   libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
 798   libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
 799   libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
 800   libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
 801   libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
 802   libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
 803   libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
 804   libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
 805   libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
 806   libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
 807   mysql-common swfdec-gnome totem-gstreamer wodim
 808 &lt;/p&gt;&lt;/blockquote&gt;
 809
 810 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
 811
 812 &lt;blockquote&gt;&lt;p&gt;
 813   gnome gnome-desktop-environment hamster-applet python-gnomeapplet
 814   python-gnomekeyring python-wnck rhythmbox-plugins xorg
 815   xserver-xorg-input-all xserver-xorg-input-evdev
 816   xserver-xorg-input-kbd xserver-xorg-input-mouse
 817   xserver-xorg-input-synaptics xserver-xorg-video-all
 818   xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
 819   xserver-xorg-video-chips xserver-xorg-video-cirrus
 820   xserver-xorg-video-dummy xserver-xorg-video-fbdev
 821   xserver-xorg-video-glint xserver-xorg-video-i128
 822   xserver-xorg-video-i740 xserver-xorg-video-mach64
 823   xserver-xorg-video-mga xserver-xorg-video-neomagic
 824   xserver-xorg-video-nouveau xserver-xorg-video-nv
 825   xserver-xorg-video-r128 xserver-xorg-video-radeon
 826   xserver-xorg-video-radeonhd xserver-xorg-video-rendition
 827   xserver-xorg-video-s3 xserver-xorg-video-s3virge
 828   xserver-xorg-video-savage xserver-xorg-video-siliconmotion
 829   xserver-xorg-video-sis xserver-xorg-video-sisusb
 830   xserver-xorg-video-tdfx xserver-xorg-video-tga
 831   xserver-xorg-video-trident xserver-xorg-video-tseng
 832   xserver-xorg-video-vesa xserver-xorg-video-vmware
 833   xserver-xorg-video-voodoo
 834 &lt;/p&gt;&lt;/blockquote&gt;
 835
 836 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
 837
 838 &lt;blockquote&gt;&lt;p&gt;
 839   deskbar-applet xserver-xorg xserver-xorg-core
 840   xserver-xorg-input-wacom xserver-xorg-video-intel
 841   xserver-xorg-video-openchrome
 842 &lt;/p&gt;&lt;/blockquote&gt;
 843
 844 &lt;p&gt;I was told on IRC that the xorg-xserver package was
 845 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
 846 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
 847 No idea when it hits Squeeze, but when it does I hope it will reduce
 848 the difference somewhat.
 849 </description>
 850         </item>
 851
 852         </channel>
 853 </rss>