From: Petter Reinholdtsen Date: Tue, 3 Aug 2010 21:23:53 +0000 (+0000) Subject: Improve text. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/410dbeb96671ffb325c485c562a829dec4704a69 Improve text. --- diff --git a/blog/data/2010-08-03-edu-roaming.txt b/blog/data/2010-08-03-edu-roaming.txt index c86f01e56e..210031ad77 100644 --- a/blog/data/2010-08-03-edu-roaming.txt +++ b/blog/data/2010-08-03-edu-roaming.txt @@ -3,7 +3,7 @@ Tags: english, nuug, debian edu Date: 2010-08-03 23:30

The new roaming workstation profile in Debian Edu/Squeeze is fairly -similar to the laptop setup am I working using Ubuntu for the +similar to the laptop setup am I working on using Ubuntu for the University of Oslo, and just for the heck of it, I tested today how hard it would be to integrate that profile into the university infrastructure. In this case, it is the university LDAP server, @@ -15,17 +15,20 @@ changed (/etc/sssd/sssd.conf, /etc/ldap.conf and /etc/mklocaluser.d/20-debian-edu-config) and one file had to be added (/usr/share/perl5/Debian/Edu_Local.pm), to get the client working. Most of the changes were to get the client to use the university LDAP -and Kerberos server, but one was to change a hard coded DNS domain -name in the mklocaluser hook.

+for NSS and Kerberos server for PAM, but one was to change a hard +coded DNS domain name in the mklocaluser hook from .intern to +.uio.no.

This testing was so encouraging, that I went ahead and adjusted the -Debian Edu scripts and setup in svn to centralise the roaming +Debian Edu scripts and setup in subversion to centralise the roaming workstation setup a bit more and avoid the hardcoded DNS domain name, so that when I test this tomorrow, I expect to get away with modifying -only /etc/sssd/sssd.conf and /etc/ldap.conf to get it to use a -different set of servers. The goal is to get the clients to have no -hardcoded settings and fetch all their initial setup during -installation and first boot, to allow them to be inserted also into -environments where the default setup in Debian Edu has been changed or -as with the university, where the environment is different but -provides the protocols Debian Edu uses.

+only /etc/sssd/sssd.conf and /etc/ldap.conf to get it to use the +university servers.

+ +

My goal is to get the clients to have no hardcoded settings and +fetch all their initial setup during installation and first boot, to +allow them to be inserted also into environments where the default +setup in Debian Edu has been changed or as with the university, where +the environment is different but provides the protocols Debian Edu +uses.