blog/index.html

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