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