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