X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/63fb8c9ab3a0fa5cbeb921777b89ae7461dec6eb..d5419a21235ed29b12c81efeac4ade8ec1cc1a98:/blog/archive/2014/03/03.rss diff --git a/blog/archive/2014/03/03.rss b/blog/archive/2014/03/03.rss index 13925eaf74..4a4a8a03d4 100644 --- a/blog/archive/2014/03/03.rss +++ b/blog/archive/2014/03/03.rss @@ -6,6 +6,160 @@ http://people.skolelinux.org/pere/blog/ + + Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine + http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html + http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html + Fri, 14 Mar 2014 11:00:00 +0100 + <p>The <a href="https://wiki.debian.org/FreedomBox">Freedombox +project</a> is working on providing the software and hardware for +making it easy for non-technical people to host their data and +communication at home, and being able to communicate with their +friends and family encrypted and away from prying eyes. It has been +going on for a while, and is slowly progressing towards a new test +release (0.2).</p> + +<p>And what day could be better than the Pi day to announce that the +new version will provide "hard drive" / SD card / USB stick images for +Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization +system), and can also be installed using a Debian installer preseed +file. The Debian based Freedombox is now based on Debian Jessie, +where most of the needed packages used are already present. Only one, +the freedombox-setup package, is missing. To try to build your own +boot image to test the current status, fetch the freedom-maker scripts +and build using +<a href="http://packages.qa.debian.org/vmdebootstrap">vmdebootstrap</a> +with a user with sudo access to become root: + +<pre> +git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \ + freedom-maker +sudo apt-get install git vmdebootstrap mercurial python-docutils \ + mktorrent extlinux virtualbox qemu-user-static binfmt-support \ + u-boot-tools +make -C freedom-maker dreamplug-image raspberry-image virtualbox-image +</pre> + +<p>Root access is needed to run debootstrap and mount loopback +devices. See the README for more details on the build. If you do not +want all three images, trim the make line. But note that thanks to <a +href="https://bugs.debian.org/741407">a race condition in +vmdebootstrap</a>, the build might fail without the patch to the +kpartx call.</p> + +<p>If you instead want to install using a Debian CD and the preseed +method, boot a Debian Wheezy ISO and use this boot argument to load +the preseed values:</p> + +<pre> +url=<a href="http://www.reinholdtsen.name/freedombox/preseed-jessie.dat">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat</a> +</pre> + +<p>But note that due to <a href="https://bugs.debian.org/740673">a +recently introduced bug in apt in Jessie</a>, the installer will +currently hang while setting up APT sources. Killing the +'<tt>apt-cdrom ident</tt>' process when it hang a few times during the +installation will get the installation going. This affect all +installations in Jessie, and I expect it will be fixed soon.</p> + +Give it a go and let us know how it goes on the mailing list, and help +us get the new release published. :) Please join us on +<a href="irc://irc.debian.org:6667/%23freedombox">IRC (#freedombox on +irc.debian.org)</a> and +<a href="http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss">the +mailing list</a> if you want to help make this vision come true.</p> + + + + + How to add extra storage servers in Debian Edu / Skolelinux + http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html + http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html + Wed, 12 Mar 2014 12:50:00 +0100 + <p>On larger sites, it is useful to use a dedicated storage server for +storing user home directories and data. The design for handling this +in <a href="http://www.skolelinux.org/">Debian Edu / Skolelinux</a>, is +to update the automount rules in LDAP and let the automount daemon on +the clients take care of the rest. I was reminded about the need to +document this better when one of the customers of +<a href="http://www.slxdrift.no/">Skolelinux Drift AS</a>, where I am +on the board of directors, asked about how to do this. The steps to +get this working are the following:</p> + +<p><ol> + +<li>Add new storage server in DNS. I use nas-server.intern as the +example host here.</li> + +<li>Add automoun LDAP information about this server in LDAP, to allow +all clients to automatically mount it on reqeust.</li> + +<li>Add the relevant entries in tjener.intern:/etc/fstab, because +tjener.intern do not use automount to avoid mounting loops.</li> + +</ol></p> + +<p>DNS entries are added in GOsa², and not described here. Follow the +<a href="https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted">instructions +in the manual</a> (Machine Management with GOsa² in section Getting +started).</p> + +<p>Ensure that the NFS export points on the server are exported to the +relevant subnets or machines:</p> + +<p><blockquote><pre> +root@tjener:~# showmount -e nas-server +Export list for nas-server: +/storage 10.0.0.0/8 +root@tjener:~# +</pre></blockquote></p> + +<p>Here everything on the backbone network is granted access to the +/storage export. With NFSv3 it is slightly better to limit it to +netgroup membership or single IP addresses to have some limits on the +NFS access.</p> + +<p>The next step is to update LDAP. This can not be done using GOsa², +because it lack a module for automount. Instead, use ldapvi and add +the required LDAP objects using an editor.</p> + +<p><blockquote><pre> +ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no +</pre></blockquote></p> + +<p>When the editor show up, add the following LDAP objects at the +bottom of the document. The "/&" part in the last LDAP object is a +wild card matching everything the nas-server exports, removing the +need to list individual mount points in LDAP.</p> + +<p><blockquote><pre> +add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no +objectClass: automount +cn: nas-server +automountInformation: -fstype=autofs --timeout=60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no + +add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no +objectClass: top +objectClass: automountMap +ou: auto.nas-server + +add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no +objectClass: automount +cn: / +automountInformation: -fstype=nfs,tcp,rsize=32768,wsize=32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/& +</pre></blockquote></p> + +<p>The last step to remember is to mount the relevant mount points in +tjener.intern by adding them to /etc/fstab, creating the mount +directories using mkdir and running "mount -a" to mount them.</p> + +<p>When this is done, your users should be able to access the files on +the storage server directly by just visiting the +/tjener/nas-server/storage/ directory using any application on any +workstation, LTSP client or LTSP server.</p> + + + Hvordan bør RFC 822-formattert epost lagres i en NOARK5-database? http://people.skolelinux.org/pere/blog/Hvordan_b_r_RFC_822_formattert_epost_lagres_i_en_NOARK5_database_.html @@ -75,7 +229,7 @@ av obligatoriske krav.</p> <p>Det ser dermed ut for meg som om det er et lite behov for å standardisere XML-lagring av RFC-822-formatterte meldinger. Noen som vet om god spesifikasjon i så måte? I tillegg til den omtalt over, -har jeg kommte over flere aktuelle beskrivelser (søk på "rfc 822 +har jeg kommet over flere aktuelle beskrivelser (søk på "rfc 822 xml", så finner du aktuelle alternativer).</p> <ul>