]> pere.pagekite.me Git - homepage.git/blob - blog/index.rss
Generated.
[homepage.git] / 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>Testing if a file system can be used for home directories...</title>
11 <link>http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html</guid>
13 <pubDate>Sun, 8 Aug 2010 21:20:00 +0200</pubDate>
14 <description>
15 &lt;p&gt;A few years ago, I was involved in a project planning to use
16 Windows file servers as home directory servers for Debian
17 Edu/Skolelinux machines. This was thought to be no problem, as the
18 access would be through the SMB network file system protocol, and we
19 knew other sites used SMB with unix and samba as the file server to
20 mount home directories without any problems. But, after months of
21 struggling, we had to conclude that our goal was impossible.&lt;/p&gt;
22
23 &lt;p&gt;The reason is simply that while SMB can be used for home
24 directories when the file server is Samba running on Unix, this only
25 work because of Samba have some extensions and the fact that the
26 underlying file system is a unix file system. When using a Windows
27 file server, the underlying file system do not have POSIX semantics,
28 and several programs will fail if the users home directory where they
29 want to store their configuration lack POSIX semantics.&lt;/p&gt;
30
31 &lt;p&gt;As part of this work, I wrote a small C program I want to share
32 with you all, to replicate a few of the problematic applications (like
33 OpenOffice.org and GCompris) and see if the file system was working as
34 it should. If you find yourself in spooky file system land, it might
35 help you find your way out again. This is the fs-test.c source:&lt;/p&gt;
36
37 &lt;pre&gt;
38 /*
39 * Some tests to check the file system sematics. Used to verify that
40 * CIFS from a windows server do not work properly as a linux home
41 * directory.
42 * License: GPL v2 or later
43 *
44 * needs libsqlite3-dev and build-essential installed
45 * compile with: gcc -Wall -lsqlite3 -DTEST_SQLITE fs-test.c -o fs-test
46 */
47
48 #define _FILE_OFFSET_BITS 64
49 #define _LARGEFILE_SOURCE 1
50 #define _LARGEFILE64_SOURCE 1
51
52 #define _GNU_SOURCE /* for asprintf() */
53
54 #include &lt;errno.h&gt;
55 #include &lt;fcntl.h&gt;
56 #include &lt;stdio.h&gt;
57 #include &lt;string.h&gt;
58 #include &lt;stdlib.h&gt;
59 #include &lt;sys/file.h&gt;
60 #include &lt;sys/stat.h&gt;
61 #include &lt;sys/types.h&gt;
62 #include &lt;unistd.h&gt;
63
64 #ifdef TEST_SQLITE
65 /*
66 * Test sqlite open, as done by gcompris require the libsqlite3-dev
67 * package and linking with -lsqlite3. A more low level test is
68 * below.
69 * See also &lt;URL: http://www.sqlite.org./faq.html#q5 &gt;.
70 */
71 #include &lt;sqlite3.h&gt;
72 #define CREATE_TABLE_USERS \
73 &quot;CREATE TABLE users (user_id INT UNIQUE, login TEXT, lastname TEXT, firstname TEXT, birthdate TEXT, class_id INT ); &quot;
74 int test_sqlite_open(void) {
75 char *zErrMsg;
76 char *name = &quot;testsqlite.db&quot;;
77 sqlite3 *db=NULL;
78 unlink(name);
79 int rc = sqlite3_open(name, &amp;db);
80 if( rc ){
81 printf(&quot;error: sqlite open of %s failed: %s\n&quot;, name, sqlite3_errmsg(db));
82 sqlite3_close(db);
83 return -1;
84 }
85
86 /* create tables */
87 rc = sqlite3_exec(db,CREATE_TABLE_USERS, NULL, 0, &amp;zErrMsg);
88 if( rc != SQLITE_OK ){
89 printf(&quot;error: sqlite table create failed: %s\n&quot;, zErrMsg);
90 sqlite3_close(db);
91 return -1;
92 }
93 printf(&quot;info: sqlite worked\n&quot;);
94 sqlite3_close(db);
95 return 0;
96 }
97 #endif /* TEST_SQLITE */
98
99 /*
100 * Demonstrate locking issue found in gcompris using sqlite3. This
101 * work with ext3, but not with cifs server on Windows 2003. This is
102 * done in the sqlite3 library.
103 * See also
104 * &lt;URL:http://www.cygwin.com/ml/cygwin/2001-08/msg00854.html&gt; and the
105 * POSIX specification
106 * &lt;URL:http://www.opengroup.org/onlinepubs/009695399/functions/fcntl.html&gt;.
107 */
108 int test_gcompris_locking(void) {
109 struct flock fl;
110 char *name = &quot;testsqlite.db&quot;;
111 unlink(name);
112 int fd = open(name, O_RDWR|O_CREAT|O_LARGEFILE, 0644);
113 printf(&quot;info: testing fcntl locking\n&quot;);
114
115 fl.l_whence = SEEK_SET;
116 fl.l_pid = getpid();
117 printf(&quot; Read-locking 1 byte from 1073741824&quot;);
118 fl.l_start = 1073741824;
119 fl.l_len = 1;
120 fl.l_type = F_RDLCK;
121 if (0 != fcntl(fd, F_SETLK, &amp;fl) ) printf(&quot; - error!\n&quot;); else printf(&quot;\n&quot;);
122
123 printf(&quot; Read-locking 510 byte from 1073741826&quot;);
124 fl.l_start = 1073741826;
125 fl.l_len = 510;
126 fl.l_type = F_RDLCK;
127 if (0 != fcntl(fd, F_SETLK, &amp;fl) ) printf(&quot; - error!\n&quot;); else printf(&quot;\n&quot;);
128
129 printf(&quot; Unlocking 1 byte from 1073741824&quot;);
130 fl.l_start = 1073741824;
131 fl.l_len = 1;
132 fl.l_type = F_UNLCK;
133 if (0 != fcntl(fd, F_SETLK, &amp;fl) ) printf(&quot; - error!\n&quot;); else printf(&quot;\n&quot;);
134
135 printf(&quot; Write-locking 1 byte from 1073741824&quot;);
136 fl.l_start = 1073741824;
137 fl.l_len = 1;
138 fl.l_type = F_WRLCK;
139 if (0 != fcntl(fd, F_SETLK, &amp;fl) ) printf(&quot; - error!\n&quot;); else printf(&quot;\n&quot;);
140
141 printf(&quot; Write-locking 510 byte from 1073741826&quot;);
142 fl.l_start = 1073741826;
143 fl.l_len = 510;
144 if (0 != fcntl(fd, F_SETLK, &amp;fl) ) printf(&quot; - error!\n&quot;); else printf(&quot;\n&quot;);
145
146 printf(&quot; Unlocking 2 byte from 1073741824&quot;);
147 fl.l_start = 1073741824;
148 fl.l_len = 2;
149 fl.l_type = F_UNLCK;
150 if (0 != fcntl(fd, F_SETLK, &amp;fl) ) printf(&quot; - error!\n&quot;); else printf(&quot;\n&quot;);
151
152 close(fd);
153 return 0;
154 }
155
156 /*
157 * Test if permissions of freshly created directories allow entries
158 * below them. This was a problem with OpenOffice.org and gcompris.
159 * Mounting with option &#39;sync&#39; seem to solve this problem while
160 * slowing down file operations.
161 */
162 int test_subdirectory_creation(void) {
163 #define LEVELS 5
164 char *path = strdup(&quot;test&quot;);
165 char *dirs[LEVELS];
166 int level;
167 printf(&quot;info: testing subdirectory creation\n&quot;);
168 for (level = 0; level &lt; LEVELS; level++) {
169 char *newpath = NULL;
170 if (-1 == mkdir(path, 0777)) {
171 printf(&quot; error: Unable to create directory &#39;%s&#39;: %s\n&quot;,
172 path, strerror(errno));
173 break;
174 }
175 asprintf(&amp;newpath, &quot;%s/%s&quot;, path, &quot;test&quot;);
176 free(path);
177 path = newpath;
178 }
179 return 0;
180 }
181
182 /*
183 * Test if symlinks can be created. This was a problem detected with
184 * KDE.
185 */
186 int test_symlinks(void) {
187 printf(&quot;info: testing symlink creation\n&quot;);
188 unlink(&quot;symlink&quot;);
189 if (-1 == symlink(&quot;file&quot;, &quot;symlink&quot;))
190 printf(&quot; error: Unable to create symlink\n&quot;);
191 return 0;
192 }
193
194 int main(int argc, char **argv) {
195 printf(&quot;Testing POSIX/Unix sematics on file system\n&quot;);
196 test_symlinks();
197 test_subdirectory_creation();
198 #ifdef TEST_SQLITE
199 test_sqlite_open();
200 #endif /* TEST_SQLITE */
201 test_gcompris_locking();
202 return 0;
203 }
204 &lt;/pre&gt;
205
206 &lt;p&gt;When everything is working, it should print something like
207 this:&lt;/p&gt;
208
209 &lt;pre&gt;
210 Testing POSIX/Unix sematics on file system
211 info: testing symlink creation
212 info: testing subdirectory creation
213 info: sqlite worked
214 info: testing fcntl locking
215 Read-locking 1 byte from 1073741824
216 Read-locking 510 byte from 1073741826
217 Unlocking 1 byte from 1073741824
218 Write-locking 1 byte from 1073741824
219 Write-locking 510 byte from 1073741826
220 Unlocking 2 byte from 1073741824
221 &lt;/pre&gt;
222
223 &lt;p&gt;I do not remember the exact details of the problems we saw, but one
224 of them was with locking, where if I remember correctly, POSIX allow a
225 read-only lock to be upgraded to a read-write lock without unlocking
226 the read-only lock (while Windows do not). Another was a bug in the
227 CIFS/SMB client implementation in the Linux kernel where directory
228 meta information would be wrong for a fraction of a second, making
229 OpenOffice.org fail to create its deep directory tree because it was
230 not allowed to create files in its freshly created directory.&lt;/p&gt;
231
232 &lt;p&gt;Anyway, here is a nice tool for your tool box, might you never need
233 it. :)&lt;/p&gt;
234 </description>
235 </item>
236
237 <item>
238 <title>Autodetecting Client setup for roaming workstations in Debian Edu</title>
239 <link>http://people.skolelinux.org/pere/blog/Autodetecting_Client_setup_for_roaming_workstations_in_Debian_Edu.html</link>
240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Autodetecting_Client_setup_for_roaming_workstations_in_Debian_Edu.html</guid>
241 <pubDate>Sat, 7 Aug 2010 14:45:00 +0200</pubDate>
242 <description>
243 &lt;p&gt;A few days ago, I
244 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Debian_Edu_roaming_workstation___at_the_university_of_Oslo.html&quot;&gt;tried
245 to install&lt;/a&gt; a Roaming workation profile from Debian Edu/Squeeze
246 while on the university network here at the University of Oslo, and
247 noticed how much had to change to get it operational using the
248 university infrastructure. It was fairly easy, but it occured to me
249 that Debian Edu would improve a lot if I could get the client to
250 connect without any changes at all, and thus let the client configure
251 itself during installation and first boot to use the infrastructure
252 around it. Now I am a huge step further along that road.&lt;/p&gt;
253
254 &lt;p&gt;With our current squeeze-test packages, I can select the roaming
255 workstation profile and get a working laptop connecting to the
256 university LDAP server for user and group and our active directory
257 servers for Kerberos authentication. All this without any
258 configuration at all during installation. My users home directory got
259 a bookmark in the KDE menu to mount it via SMB, with the correct URL.
260 In short, openldap and sssd is correctly configured. In addition to
261 this, the client look for http://wpad/wpad.dat to configure a web
262 proxy, and when it fail to find it no proxy settings are stored in
263 /etc/environment and /etc/apt/apt.conf. Iceweasel and KDE is
264 configured to look for the same wpad configuration and also do not use
265 a proxy when at the university network. If the machine is moved to a
266 network with such wpad setup, it would automatically use it when DHCP
267 gave it a IP address.&lt;/p&gt;
268
269 &lt;p&gt;The LDAP server is located using DNS, by first looking for the DNS
270 entry ldap.$domain. If this do not exist, it look for the
271 _ldap._tcp.$domain SRV records and use the first one as the LDAP
272 server. Next, it connects to the LDAP server and search all
273 namingContexts entries for posixAccount or posixGroup objects, and
274 pick the first one as the LDAP base. For Kerberos, a similar
275 algorithm is used to locate the LDAP server, and the realm is the
276 uppercase version of $domain.&lt;/p&gt;
277
278 &lt;p&gt;So, what is not working, you might ask. SMB mounting my home
279 directory do not work. No idea why, but suspected the incorrect
280 Kerberos settings in /etc/krb5.conf and /etc/samba/smb.conf might be
281 the cause. These are not properly configured during installation, and
282 had to be hand-edited to get the correct Kerberos realm and server,
283 but SMB mounting still do not work. :(&lt;/p&gt;
284
285 &lt;p&gt;With this automatic configuration in place, I expect a Debian Edu
286 roaming profile installation would be able to automatically detect and
287 connect to any site using LDAP and Kerberos for NSS directory and PAM
288 authentication. It should also work out of the box in a Active
289 Directory environment providing posixAccount and posixGroup objects
290 with UID and GID values.&lt;/p&gt;
291
292 &lt;p&gt;If you want to help out with implementing these things for Debian
293 Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
294 </description>
295 </item>
296
297 <item>
298 <title>Debian Edu roaming workstation - at the university of Oslo</title>
299 <link>http://people.skolelinux.org/pere/blog/Debian_Edu_roaming_workstation___at_the_university_of_Oslo.html</link>
300 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Edu_roaming_workstation___at_the_university_of_Oslo.html</guid>
301 <pubDate>Tue, 3 Aug 2010 23:30:00 +0200</pubDate>
302 <description>
303 &lt;p&gt;The new roaming workstation profile in Debian Edu/Squeeze is fairly
304 similar to the laptop setup am I working on using Ubuntu for the
305 University of Oslo, and just for the heck of it, I tested today how
306 hard it would be to integrate that profile into the university
307 infrastructure. In this case, it is the university LDAP server,
308 Active Directory Kerberos server and SMB mounting from the Netapp file
309 servers.&lt;/p&gt;
310
311 &lt;p&gt;I was pleasantly surprised that the only three files needed to be
312 changed (/etc/sssd/sssd.conf, /etc/ldap.conf and
313 /etc/mklocaluser.d/20-debian-edu-config) and one file had to be added
314 (/usr/share/perl5/Debian/Edu_Local.pm), to get the client working.
315 Most of the changes were to get the client to use the university LDAP
316 for NSS and Kerberos server for PAM, but one was to change a hard
317 coded DNS domain name in the mklocaluser hook from .intern to
318 .uio.no.&lt;/p&gt;
319
320 &lt;p&gt;This testing was so encouraging, that I went ahead and adjusted the
321 Debian Edu scripts and setup in subversion to centralise the roaming
322 workstation setup a bit more and avoid the hardcoded DNS domain name,
323 so that when I test this tomorrow, I expect to get away with modifying
324 only /etc/sssd/sssd.conf and /etc/ldap.conf to get it to use the
325 university servers.&lt;/p&gt;
326
327 &lt;p&gt;My goal is to get the clients to have no hardcoded settings and
328 fetch all their initial setup during installation and first boot, to
329 allow them to be inserted also into environments where the default
330 setup in Debian Edu has been changed or as with the university, where
331 the environment is different but provides the protocols Debian Edu
332 uses.&lt;/p&gt;
333 </description>
334 </item>
335
336 <item>
337 <title>Circular package dependencies harms apt recovery</title>
338 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
339 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
340 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
341 <description>
342 &lt;p&gt;I discovered this while doing
343 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
344 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
345 in Debian still got circular dependencies, and it is often claimed
346 that apt and aptitude should be able to handle this just fine, but
347 some times these dependency loops causes apt to fail.&lt;/p&gt;
348
349 &lt;p&gt;An example is from todays
350 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
351 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
352 causes perl-modules to fail to upgrade. The cause is simple. If a
353 package fail to unpack, then only part of packages with the circular
354 dependency might end up being unpacked when unpacking aborts, and the
355 ones already unpacked will fail to configure in the recovery phase
356 because its dependencies are unavailable.&lt;/p&gt;
357
358 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
359
360 &lt;blockquote&gt;&lt;pre&gt;
361 dpkg: dependency problems prevent configuration of perl-modules:
362 perl-modules depends on perl (&gt;= 5.10.1-1); however:
363 Version of perl on system is 5.10.0-19lenny2.
364 dpkg: error processing perl-modules (--configure):
365 dependency problems - leaving unconfigured
366 &lt;/pre&gt;&lt;/blockquote&gt;
367
368 &lt;p&gt;The perl/perl-modules circular dependency is already
369 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
370 hopefully be solved as soon as possible, but it is not the only one,
371 and each one of these loops in the dependency tree can cause similar
372 failures. Of course, they only occur when there are bugs in other
373 packages causing the unpacking to fail, but it is rather nasty when
374 the failure of one package causes the problem to become worse because
375 of dependency loops.&lt;/p&gt;
376
377 &lt;p&gt;Thanks to
378 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
379 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
380 dependencies
381 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
382 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
383
384 &lt;p&gt;Todays testing also exposed a bug in
385 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
386 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
387 apt-get and aptitude, the latter possibly caused by some circular
388 dependency. Reported both to BTS to try to get someone to look at
389 it.&lt;/p&gt;
390 </description>
391 </item>
392
393 <item>
394 <title>First Debian Edu test release (alpha0) based on Squeeze is released</title>
395 <link>http://people.skolelinux.org/pere/blog/First_Debian_Edu_test_release__alpha0__based_on_Squeeze_is_released.html</link>
396 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_Debian_Edu_test_release__alpha0__based_on_Squeeze_is_released.html</guid>
397 <pubDate>Tue, 27 Jul 2010 17:45:00 +0200</pubDate>
398 <description>
399 &lt;p&gt;I just posted this announcement culminating several months of work
400 with the next Debian Edu release. Not nearly done, but one major step
401 completed.&lt;/p&gt;
402
403 &lt;blockquote&gt;
404 &lt;p&gt;This is the first test release based on Squeeze. The focus of this
405 release is to test the user application selection. To have a look,
406 install the standalone profile and let the developers know if the set
407 of installed packages i.e. applications should be modified. If some
408 user application is missing, or if there are some applications that no
409 longer make sense to be included in Debian Edu, please let us know.
410 Also, if a useful application is missing the translation for your
411 language of choice, please let us know too.&lt;/p&gt;
412
413 &lt;p&gt;In addition, feedback and help to polish the desktop (menus,
414 artwork, starters, etc.) is appreciated. We would like to ship a nice
415 and handy KDE4 desktop targeted for schools out of the box.&lt;/p&gt;
416
417 &lt;p&gt;The other profiles should be installable, but there is a lot more
418 work left to be done before they are ready, so do not expect to
419 much.&lt;/p&gt;
420
421 &lt;p&gt;Changes compared to the lenny based version&lt;/p&gt;
422
423 &lt;ul&gt;
424 &lt;li&gt;Everything from Debian Squeeze
425 &lt;ul&gt;
426 &lt;li&gt;Desktop environment KDE 4.4 =&gt; the new KDE desktop in
427 combination with some new artwork
428 &lt;li&gt;Web browser Iceweasel 3.5
429 &lt;li&gt;OpenOffice.org 3.2
430 &lt;li&gt;Educational toolbox GCompris 9.3
431 &lt;li&gt;Music creator Rosegarden 10.04.2
432 &lt;li&gt;Image editor Gimp 2.6.10
433 &lt;li&gt;Virtual universe Celestia 1.6.0
434 &lt;li&gt;Virtual stargazer Stellarium 0.10.4
435 &lt;li&gt;3D modeler Blender 2.49.2 (new application)
436 &lt;li&gt;Video editor Kdenlive 0.7.7 (new application)
437 &lt;/ul&gt;&lt;/li&gt;
438 &lt;li&gt;Now using Kerberos for password checking (migration not finished).
439 Enabled for:
440 &lt;ul&gt;
441 &lt;li&gt;PAM
442 &lt;li&gt;LDAP
443 &lt;li&gt;IMAP
444 &lt;li&gt;SMTP (sender verification)
445 &lt;/ul&gt;
446 &lt;/li&gt;
447 &lt;li&gt;New experimental roaming workstation profile for laptops.&lt;/li&gt;
448 &lt;li&gt;Show welcome page to users when they first log in. The URL is
449 fetched from LDAP.&lt;/li&gt;
450 &lt;li&gt;New LXDE desktop option, in addition to KDE (default) and Gnome.&lt;/li&gt;
451 &lt;li&gt;General cleanup (not finished)&lt;/li&gt;
452 &lt;/ul&gt;
453 &lt;p&gt;The following features are not working as they should&lt;/p&gt;
454
455 &lt;ul&gt;
456 &lt;li&gt;No web based administration tool for creating users and groups. The
457 scripts ldap-createuser-krb and ldap-add-user-to-group can be used
458 for testing.&lt;/li&gt;
459 &lt;li&gt;DVD installs are missing debian-installer images for the PXE boot,
460 and do not set up the PXE menu on eth0 because of this. LTSP
461 clients should still boot from eth1 on thin client servers.&lt;/li&gt;
462 &lt;li&gt;The restructured KDE menu is not implemented.&lt;/li&gt;
463 &lt;li&gt;The LDAP server setup need to be reviewed for security.&lt;/li&gt;
464 &lt;li&gt;The LDAP directory structure need to be reworked.&lt;/li&gt;
465 &lt;li&gt;Different sets of packages are installed when using the DVD and the
466 netinst CD. More packages are installed using the netinst CD.&lt;/li&gt;
467 &lt;li&gt;The jackd package fail to install. This is believed to be caused by
468 some ongoing transition, and hopefully should be solved soon. The
469 jackd1 package can be installed manually for those that need it.&lt;/li&gt;
470 &lt;li&gt;Some packages lack translations. See
471 http://wiki.debian.org/DebianEdu/Status/Squeeze for updated status,
472 and help out with translations.&lt;/li&gt;
473 &lt;/ul&gt;
474
475 &lt;p&gt;To download this multiarch netinstall release you can use&lt;/p&gt;
476
477 &lt;ul&gt;
478 &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;
479 &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;
480 &lt;li&gt;rsync -avzP ftp.skolelinux.org::skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-CD.iso&lt;/li&gt;
481 &lt;/ul&gt;
482 &lt;p&gt;To download this multiarch dvd release you can use&lt;/p&gt;
483
484 &lt;ul&gt;
485 &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;
486 &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;
487 &lt;li&gt;rsync -avzP ftp.skolelinux.org::skolelinux-cd/squeeze-alpha/debian-edu-6.0.0+edua0-DVD.iso&lt;/li&gt;
488 &lt;/ul&gt;
489
490 &lt;p&gt;There is no source DVD available yet. It will be prepared when we
491 get closer to the final release.&lt;/p&gt;
492
493 &lt;p&gt;The MD5SUM of these images are&lt;/p&gt;
494
495 &lt;ul&gt;
496 &lt;li&gt;3dbf45d59f42a53518b6e3c9ec3b5eb6 debian-edu-6.0.0+edua0-CD.iso&lt;/li&gt;
497 &lt;li&gt;22f2cbfce281d1c6e478be452638675d debian-edu-6.0.0+edua0-DVD.iso&lt;/li&gt;
498 &lt;/ul&gt;
499
500 &lt;p&gt;The SHA1SUM of these images are&lt;/p&gt;
501 &lt;ul&gt;
502 &lt;li&gt;c53d1b69b40cf37cd27aefaf33f6f6a3821bedf0 debian-edu-6.0.0+edua0-CD.iso&lt;/li&gt;
503 &lt;li&gt;2ec29d7db676d59d32197b05c277ffe16348376c debian-edu-6.0.0+edua0-DVD.iso&lt;/li&gt;
504 &lt;/ul&gt;
505 &lt;p&gt;How to report bugs:
506 http://wiki.debian.org/DebianEdu/HowTo/ReportBugsInBugzilla&lt;/p&gt;
507
508 &lt;p&gt;Please direct replies to debian-edu@lists.debian.org&lt;/p&gt;
509 &lt;/blockquote&gt;
510 </description>
511 </item>
512
513 <item>
514 <title>One step closer to single signon in Debian Edu</title>
515 <link>http://people.skolelinux.org/pere/blog/One_step_closer_to_single_signon_in_Debian_Edu.html</link>
516 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_step_closer_to_single_signon_in_Debian_Edu.html</guid>
517 <pubDate>Sun, 25 Jul 2010 10:00:00 +0200</pubDate>
518 <description>
519 &lt;p&gt;The last few months me and the other Debian Edu developers have
520 been working hard to get the Debian/Squeeze based version of Debian
521 Edu/Skolelinux into shape. This future version will use Kerberos for
522 authentication, and services are slowly migrated to single signon,
523 getting rid of password questions one at the time.&lt;/p&gt;
524
525 &lt;p&gt;It will also feature a roaming workstation profile with local home
526 directory, for laptops that are only some times on the Skolelinux
527 network, and for this profile a shortcut is created in Gnome and KDE
528 to gain access to the users home directory on the file server. This
529 shortcut uses SMB at the moment, and yesterday I had time to test if
530 SMB mounting had started working in KDE after we added the cifs-utils
531 package. I was pleasantly surprised how well it worked.&lt;/p&gt;
532
533 &lt;p&gt;Thanks to the recent changes to our samba configuration to get it
534 to use Kerberos for authentication, there were no question about user
535 password when mounting the SMB volume. A simple click on the shortcut
536 in the KDE menu, and a window with the home directory popped
537 up. :)&lt;/p&gt;
538
539 &lt;p&gt;One step closer to a single signon solution out of the box in
540 Debian Edu. We already had PAM, LDAP, IMAP and SMTP in place, and now
541 also Samba. Next step is Cups and hopefully also NFS.&lt;/p&gt;
542
543 &lt;p&gt;We had planned a alpha0 release of Debian Edu for today, but thanks
544 to the autobuilder administrators for some architectures being slow to
545 sign packages, we are still missing the fixed LTSP package we need for
546 the release. It was uploaded three days ago with urgency=high, and if
547 it had entered testing yesterday we would have been able to test it in
548 time for a alpha0 release today. As the binaries for ia64 and powerpc
549 still not uploaded to the Debian archive, we need to delay the alpha
550 release another day.&lt;/p&gt;
551
552 &lt;p&gt;If you want to help out with implementing Kerberos for Debian Edu,
553 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
554 </description>
555 </item>
556
557 <item>
558 <title>Digitale restriksjonsmekanismer fikk meg til å slutte å kjøpe musikk</title>
559 <link>http://people.skolelinux.org/pere/blog/Digitale_restriksjonsmekanismer_fikk_meg_til____slutte____kj__pe_musikk.html</link>
560 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Digitale_restriksjonsmekanismer_fikk_meg_til____slutte____kj__pe_musikk.html</guid>
561 <pubDate>Thu, 22 Jul 2010 23:50:00 +0200</pubDate>
562 <description>
563 &lt;p&gt;For mange år siden slutte jeg å kjøpe musikk-CDer. Årsaken var at
564 musikkbransjen var godt i gang med å selge platene sine med DRM som
565 gjorde at jeg ikke fikk spilt av musikken jeg kjøpte på utstyret jeg
566 hadde tilgjengelig, dvs. min datamaskin. Det var umulig å se på en
567 plate om den var ødelagt eller ikke, og jeg hadde jo allerede en
568 anseelig samling med plater, så jeg bestemme meg for å slutte å gi
569 penger til en bransje som åpenbart ikke respekterte meg.&lt;/p&gt;
570
571 &lt;p&gt;Jeg har mange titalls dager med musikk på CD i dag. Det meste er
572 lagt i et stort arkiv som kan spilles av fra husets datamaskiner (har
573 ikke rukket rippe alt). Jeg ser dermed ikke behovet for å skaffe mer
574 musikk. De fleste av mine favoritter er i hus, og jeg er dermed godt
575 fornøyd.&lt;/p&gt;
576
577 &lt;p&gt;Hvis musikkbransjen ønsker mine penger, så må de demonstrere at de
578 setter pris på meg som kunde, og ikke skremme meg bort med DRM og
579 antydninger om at kundene er kriminelle.&lt;/p&gt;
580
581 &lt;p&gt;Filmbransjen er like ille, men mens musikk gjerne varer lenge, er
582 filmer mer ferskvare. Har dermed ikke helt sluttet å kjøpe filmer, men
583 holder meg til DVD-filmer som kan spilles av på mine Linuxbokser.
584 Kommer neppe til å ta i bruk Blueray, og ei heller de nye DRM-greiene
585 «Ultraviolet» som be annonsert her om dagen.&lt;/p&gt;
586 </description>
587 </item>
588
589 <item>
590 <title>OpenStreetmap one step closer to having routing on its front page</title>
591 <link>http://people.skolelinux.org/pere/blog/OpenStreetmap_one_step_closer_to_having_routing_on_its_front_page.html</link>
592 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenStreetmap_one_step_closer_to_having_routing_on_its_front_page.html</guid>
593 <pubDate>Sun, 18 Jul 2010 16:45:00 +0200</pubDate>
594 <description>
595 &lt;p&gt;Thanks to
596 &lt;a href=&quot;http://feedproxy.google.com/~r/Opengeodata/~3/wUTCzDZk3lc/project-of-the-week-which-way-home&quot;&gt;todays
597 opengeodata blog entry&lt;/a&gt;, I just discovered that the
598 OpenStreetmap.org site have gotten
599 &lt;a href=&quot;http://nroets.dev.openstreetmap.org/demo/index.html?layers=B000FTFTT&quot;&gt;support
600 for calculating routes&lt;/a&gt;. The support is still experimental and
601 only available from the development server, until more experience is
602 gathered on the user interface and any scalability issues.&lt;/p&gt;
603
604 &lt;p&gt;Earlier, the routing I knew about using the OpenStreetmap.org data
605 was provided by &lt;a href=&quot;http://maps.cloudmade.com/&quot;&gt;Cloudmade&lt;/a&gt;,
606 but having it on the main page is required to make everyone aware of
607 the issue. I&#39;ve had people reject Openstreetmap.org as a viable
608 alternative for them because the front page lacked routing support,
609 and I hope their needs will be catered for when routing show up on the
610 www.openstreetmap.org front page.&lt;/p&gt;
611 </description>
612 </item>
613
614 <item>
615 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
616 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
617 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
618 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
619 <description>
620 &lt;p&gt;This is a
621 &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;
622 on my
623 &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
624 work&lt;/a&gt; on
625 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
626 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
627
628 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
629 LDAP objects, I have had a look at how the packages pdns-backend-ldap
630 and dhcp3-server-ldap in Debian use the LDAP server. The two
631 implementations are quite different in how they use LDAP.&lt;/p&gt;
632
633 To get this information, I started slapd with debugging enabled and
634 dumped the debug output to a file to get the LDAP searches performed
635 on a Debian Edu main-server. Here is a summary.
636
637 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
638
639 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
640 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
641 the web.
642
643 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
644 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
645 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
646 reverse entries are in two different subtrees in LDAP with a structure
647 based on the DNS names, as in tjener.intern and
648 2.2.0.10.in-addr.arpa.&lt;/p&gt;
649
650 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
651 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
652 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
653 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
654 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
655 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
656 forward entries, it is looking for attributes named dnsttl, arecord,
657 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
658 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
659 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
660 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
661 spfrecord and modifytimestamp. For reverse entries it is looking for
662 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
663 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
664 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
665 ldapsearch commands could look like this:&lt;/p&gt;
666
667 &lt;blockquote&gt;&lt;pre&gt;
668 ldapsearch -h ldap \
669 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
670 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
671 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
672 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
673 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
674 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
675
676 ldapsearch -h ldap \
677 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
678 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
679 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
680 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
681 srvrecord naptrrecord modifytimestamp
682 &lt;/pre&gt;&lt;/blockquote&gt;
683
684 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
685 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
686 example LDAP objects used there. In addition to these objects, the
687 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
688 also exist.&lt;/p&gt;
689
690 &lt;blockquote&gt;&lt;pre&gt;
691 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
692 objectclass: top
693 objectclass: dnsdomain
694 objectclass: domainrelatedobject
695 dc: tjener
696 arecord: 10.0.2.2
697 associateddomain: tjener.intern
698
699 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
700 objectclass: top
701 objectclass: dnsdomain2
702 objectclass: domainrelatedobject
703 dc: 2
704 ptrrecord: tjener.intern
705 associateddomain: 2.2.0.10.in-addr.arpa
706 &lt;/pre&gt;&lt;/blockquote&gt;
707
708 &lt;p&gt;In strict mode, the server behaves differently. When looking for
709 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
710 same base as in the tree mode for a object with filter
711 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
712 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
713 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
714 naptrrecord and modifytimestamp. For reverse entires it also do a
715 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
716 and the requested attributes are associateddomain, dnsttl and
717 modifytimestamp. In short, in strict mode the objects with ptrrecord
718 go away, and the arecord attribute in the forward object is used
719 instead.&lt;/p&gt;
720
721 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
722 like this:&lt;/p&gt;
723
724 &lt;blockquote&gt;&lt;pre&gt;
725 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
726 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
727 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
728 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
729 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
730 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
731
732 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
733 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
734 &lt;/pre&gt;&lt;/blockquote&gt;
735
736 &lt;p&gt;In addition to the forward and reverse searches , there is also a
737 search for SOA records, which behave similar to the forward and
738 reverse lookups.&lt;/p&gt;
739
740 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
741 specify any objectclass names, and instead look for the attributes it
742 need to generate a DNS reply. This make it able to work with any
743 objectclass that provide the needed attributes.&lt;/p&gt;
744
745 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
746 dnsdomain2 schemas. The latter is used for reverse entries like
747 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
748
749 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
750 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
751 attributes) and domainrelatedobject (for associatedDomain). The use
752 of structural object classes make it impossible to combine these
753 classes with the object classes used by DHCP.&lt;/p&gt;
754
755 &lt;p&gt;There are other schemas that could be used too, for example the
756 dnszone structural object class used by Gosa and bind-sdb for the DNS
757 attributes combined with the domainrelatedobject object class, but in
758 this case some unused attributes would have to be included as well
759 (zonename and relativedomainname).&lt;/p&gt;
760
761 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
762 mode and not use any of the existing objectclasses (dnsdomain,
763 dnsdomain2 and dnszone) when one want to combine the DNS information
764 with DHCP information, and instead create a auxiliary object class
765 defined something like this (using the attributes defined for
766 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
767
768 &lt;blockquote&gt;&lt;pre&gt;
769 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
770 SUP top
771 AUXILIARY
772 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
773 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
774 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
775 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
776 A6Record $ DNAMERecord
777 ))
778 &lt;/pre&gt;&lt;/blockquote&gt;
779
780 &lt;p&gt;This will allow any object to become a DNS entry when combined with
781 the domainrelatedobject object class, and allow any entity to include
782 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
783 developers asking for their view on this schema and if they are
784 interested in providing such schema with PowerDNS, and I hope my
785 message will be accepted into their mailing list soon.&lt;/p&gt;
786
787 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
788
789 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
790 the object attributes, and then uses the attributes it want. This
791 make it harder to figure out exactly what attributes are used, but
792 thanks to the working example in Debian Edu I can at least get an idea
793 what is needed without having to read the source code.&lt;/p&gt;
794
795 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
796 search filter to use to locate the correct dhcpServer entity is
797 stored. These are the relevant entries from
798 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
799
800 &lt;blockquote&gt;&lt;pre&gt;
801 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
802 ldap-dhcp-server-cn &quot;dhcp&quot;;
803 &lt;/pre&gt;&lt;/blockquote&gt;
804
805 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
806 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
807 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
808 search result is this entry:&lt;/p&gt;
809
810 &lt;blockquote&gt;&lt;pre&gt;
811 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
812 cn: dhcp
813 objectClass: top
814 objectClass: dhcpServer
815 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
816 &lt;/pre&gt;&lt;/blockquote&gt;
817
818 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
819 subtree with DHCP configuration. The DHCP configuration subtree base
820 is located using a base scope search with base &quot;cn=DHCP
821 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
822 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
823 The search result is this entry:&lt;/p&gt;
824
825 &lt;blockquote&gt;&lt;pre&gt;
826 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
827 cn: DHCP Config
828 objectClass: top
829 objectClass: dhcpService
830 objectClass: dhcpOptions
831 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
832 dhcpStatements: ddns-update-style none
833 dhcpStatements: authoritative
834 dhcpOption: smtp-server code 69 = array of ip-address
835 dhcpOption: www-server code 72 = array of ip-address
836 dhcpOption: wpad-url code 252 = text
837 &lt;/pre&gt;&lt;/blockquote&gt;
838
839 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
840 all the DHCP configuration is loaded, it is ready to receive requests.
841 The subtree in Debian Edu contain objects with object classes
842 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
843 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
844 and information about netmasks, dynamic range etc. Leaving out the
845 details here because it is not relevant for the focus of my
846 investigation, which is to see if it is possible to merge dns and dhcp
847 related computer objects.&lt;/p&gt;
848
849 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
850 of the client (00:00:00:00:00:00 in this example), using a subtree
851 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
852 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
853 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
854 like:&lt;/p&gt;
855
856 &lt;blockquote&gt;&lt;pre&gt;
857 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
858 cn: hostname
859 objectClass: top
860 objectClass: dhcpHost
861 dhcpHWAddress: ethernet 00:00:00:00:00:00
862 dhcpStatements: fixed-address hostname
863 &lt;/pre&gt;&lt;/blockquote&gt;
864
865 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
866 The object classes need to have fixed names, and the configuration
867 need to be stored in a fairly specific LDAP structure. On the
868 positive side, the invidiual dhcpHost entires can be anywhere without
869 the DN pointed to by the dhcpServer entries. The latter should make
870 it possible to group all host entries in a subtree next to the
871 configuration entries, and this subtree can also be shared with the
872 DNS server if the schema proposed above is combined with the dhcpHost
873 structural object class.
874
875 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
876
877 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
878 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
879 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
880 allowing DNS objects to be stored anywhere under the base cn specified
881 in the configuration.&lt;/p&gt;
882
883 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
884 regarding which LDAP schemas to use and which LDAP structure to use.
885 I guess one could implement ones own schema, as long as the
886 objectclasses and attributes have the names used, but this do not
887 really help when the DHCP subtree need to have a fairly fixed
888 structure.&lt;/p&gt;
889
890 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
891 this might work for Debian Edu:&lt;/p&gt;
892
893 &lt;blockquote&gt;&lt;pre&gt;
894 ou=services
895 cn=machine-info (dhcpService) - dhcpServiceDN points here
896 cn=dhcp (dhcpServer)
897 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
898 cn=10.0.2.0 (dhcpSubnet)
899 cn=group1 (dhcpGroup/dhcpOptions)
900 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
901 cn=192.168.0.0 (dhcpSubnet)
902 cn=group1 (dhcpGroup/dhcpOptions)
903 ou=machines - PowerDNS base points here
904 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
905 &lt;/pre&gt;&lt;/blockquote&gt;
906
907 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
908 entries to be in the dhcpGroup subtrees, the entries can be stored
909 there instead of a common machines subtree, and the PowerDNS base
910 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
911
912 &lt;p&gt;The combined object under the machines subtree would look something
913 like this:&lt;/p&gt;
914
915 &lt;blockquote&gt;&lt;pre&gt;
916 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
917 dc: hostname
918 objectClass: top
919 objectClass: dhcpHost
920 objectclass: domainrelatedobject
921 objectclass: dnsDomainAux
922 associateddomain: hostname.intern
923 arecord: 10.11.12.13
924 dhcpHWAddress: ethernet 00:00:00:00:00:00
925 dhcpStatements: fixed-address hostname.intern
926 &lt;/pre&gt;&lt;/blockquote&gt;
927
928 &lt;/p&gt;One could even add the LTSP configuration associated with a given
929 machine, as long as the required attributes are available in a
930 auxiliary object class.&lt;/p&gt;
931 </description>
932 </item>
933
934 <item>
935 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
936 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
937 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
938 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
939 <description>
940 &lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
941 DHCP services in Debian Edu to use the same LDAP objects for a given
942 computer, to avoid the possibility of having a inconsistent state for
943 a computer in LDAP (as in DHCP but no DNS entry or the other way
944 around) and make it easier to add computers to LDAP.&lt;/p&gt;
945
946 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
947 information finally found a solution that seem to work.&lt;/p&gt;
948
949 &lt;p&gt;The old setup required three LDAP objects for a given computer.
950 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
951 we switch powerdns to use its strict LDAP method (ldap-method=strict
952 in pdns-debian-edu.conf), the forward and reverse DNS entries are
953 merged into one while making it impossible to transfer the reverse map
954 to a slave DNS server.&lt;/p&gt;
955
956 &lt;p&gt;If we also replace the object class used to get the DNS related
957 attributes to one allowing these attributes to be combined with the
958 dhcphost object class, we can merge the DNS and DHCP entries into one.
959 I&#39;ve written such object class in the dnsdomainaux.schema file (need
960 proper OIDs, but that is a minor issue), and tested the setup. It
961 seem to work.&lt;/p&gt;
962
963 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
964 for both DNS and DHCP, and even the LTSP configuration I suggested in
965 an earlier email. The combined LDAP object will look something like
966 this:&lt;/p&gt;
967
968 &lt;blockquote&gt;&lt;pre&gt;
969 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
970 cn: hostname
971 objectClass: dhcphost
972 objectclass: domainrelatedobject
973 objectclass: dnsdomainaux
974 associateddomain: hostname.intern
975 arecord: 10.11.12.13
976 dhcphwaddress: ethernet 00:00:00:00:00:00
977 dhcpstatements: fixed-address hostname
978 ldapconfigsound: Y
979 &lt;/pre&gt;&lt;/blockquote&gt;
980
981 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
982 the DHCP server uses the dhcphwaddress and dhcpstatements entries
983 before asking DNS to resolve the fixed-adddress. LTSP will use
984 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
985
986 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
987 dhcphost in a different location, to allow us to put the objects
988 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
989 that. If I can&#39;t figure out a way to do that, we can still get rid of
990 the hosts subtree and move all its content into the DHCP Config tree
991 (which probably should be renamed to be more related to the new
992 content. I suspect cn=dnsdhcp,ou=services or something like that
993 might be a good place to put it.&lt;/p&gt;
994
995 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
996 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
997 </description>
998 </item>
999
1000 </channel>
1001 </rss>