X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/c75c99e3db61c669fcd48cf13fbe1b7e812e5b8a..105f9e180ef3a74846475820bfcd7a63a4061808:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index 5e33e0e4a5..09c9ccd44f 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,493 @@ http://people.skolelinux.org/pere/blog/ + + Debian init.d boot script example for rsyslog + http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html + http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html + Sat, 2 Nov 2013 22:40:00 +0100 + <p>If one of the points of switching to a new init system in Debian is +<a href="http://thomas.goirand.fr/blog/?p=147">to get rid of huge +init.d scripts</a>, I doubt we need to switch away from sysvinit and +init.d scripts at all. Here is an example init.d script, ie a rewrite +of /etc/init.d/rsyslog:</p> + +<p><pre> +#!/lib/init/init-d-script +### BEGIN INIT INFO +# Provides: rsyslog +# Required-Start: $remote_fs $time +# Required-Stop: umountnfs $time +# X-Stop-After: sendsigs +# Default-Start: 2 3 4 5 +# Default-Stop: 0 1 6 +# Short-Description: enhanced syslogd +# Description: Rsyslog is an enhanced multi-threaded syslogd. +# It is quite compatible to stock sysklogd and can be +# used as a drop-in replacement. +### END INIT INFO +DESC="enhanced syslogd" +DAEMON=/usr/sbin/rsyslogd +</pre></p> + +<p>Pretty minimalistic to me... For the record, the original sysv-rc +script was 137 lines, and the above is just 15 lines, most of it meta +info/comments.</p> + +<p>How to do this, you ask? Well, one create a new script +/lib/init/init-d-script looking something like this: + +<p><pre> +#!/bin/sh + +# Define LSB log_* functions. +# Depend on lsb-base (>= 3.2-14) to ensure that this file is present +# and status_of_proc is working. +. /lib/lsb/init-functions + +# +# Function that starts the daemon/service + +# +do_start() +{ + # Return + # 0 if daemon has been started + # 1 if daemon was already running + # 2 if daemon could not be started + start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \ + || return 1 + start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \ + $DAEMON_ARGS \ + || return 2 + # Add code here, if necessary, that waits for the process to be ready + # to handle requests from services started subsequently which depend + # on this one. As a last resort, sleep for some time. +} + +# +# Function that stops the daemon/service +# +do_stop() +{ + # Return + # 0 if daemon has been stopped + # 1 if daemon was already stopped + # 2 if daemon could not be stopped + # other if a failure occurred + start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME + RETVAL="$?" + [ "$RETVAL" = 2 ] && return 2 + # Wait for children to finish too if this is a daemon that forks + # and if the daemon is only ever run from this initscript. + # If the above conditions are not satisfied then add some other code + # that waits for the process to drop all resources that could be + # needed by services started subsequently. A last resort is to + # sleep for some time. + start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON + [ "$?" = 2 ] && return 2 + # Many daemons don't delete their pidfiles when they exit. + rm -f $PIDFILE + return "$RETVAL" +} + +# +# Function that sends a SIGHUP to the daemon/service +# +do_reload() { + # + # If the daemon can reload its configuration without + # restarting (for example, when it is sent a SIGHUP), + # then implement that here. + # + start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME + return 0 +} + +SCRIPTNAME=$1 +scriptbasename="$(basename $1)" +echo "SN: $scriptbasename" +if [ "$scriptbasename" != "init-d-library" ] ; then + script="$1" + shift + . $script +else + exit 0 +fi + +NAME=$(basename $DAEMON) +PIDFILE=/var/run/$NAME.pid + +# Exit if the package is not installed +#[ -x "$DAEMON" ] || exit 0 + +# Read configuration variable file if it is present +[ -r /etc/default/$NAME ] && . /etc/default/$NAME + +# Load the VERBOSE setting and other rcS variables +. /lib/init/vars.sh + +case "$1" in + start) + [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME" + do_start + case "$?" in + 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; + 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; + esac + ;; + stop) + [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME" + do_stop + case "$?" in + 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; + 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; + esac + ;; + status) + status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $? + ;; + #reload|force-reload) + # + # If do_reload() is not implemented then leave this commented out + # and leave 'force-reload' as an alias for 'restart'. + # + #log_daemon_msg "Reloading $DESC" "$NAME" + #do_reload + #log_end_msg $? + #;; + restart|force-reload) + # + # If the "reload" option is implemented then remove the + # 'force-reload' alias + # + log_daemon_msg "Restarting $DESC" "$NAME" + do_stop + case "$?" in + 0|1) + do_start + case "$?" in + 0) log_end_msg 0 ;; + 1) log_end_msg 1 ;; # Old process is still running + *) log_end_msg 1 ;; # Failed to start + esac + ;; + *) + # Failed to stop + log_end_msg 1 + ;; + esac + ;; + *) + echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2 + exit 3 + ;; +esac + +: +</pre></p> + +<p>It is based on /etc/init.d/skeleton, and could be improved quite a +lot. I did not really polish the approach, so it might not always +work out of the box, but you get the idea. I did not try very hard to +optimize it nor make it more robust either.</p> + +<p>A better argument for switching init system in Debian than reducing +the size of init scripts (which is a good thing to do anyway), is to +get boot system that is able to handle the kernel events sensibly and +robustly, and do not depend on the boot to run sequentially. The boot +and the kernel have not behaved sequentially in years.</p> + + + + + Browser plugin for SPICE (spice-xpi) uploaded to Debian + http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html + http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html + Fri, 1 Nov 2013 11:00:00 +0100 + <p><a href="http://www.spice-space.org/">The SPICE protocol</a> for +remote display access is the preferred solution with oVirt and RedHat +Enterprise Virtualization, and I was sad to discover the other day +that the browser plugin needed to use these systems seamlessly was +missing in Debian. The <a href="http://bugs.debian.org/668284">request +for a package</a> was from 2012-04-10 with no progress since +2013-04-01, so I decided to wrap up a package based on the great work +from Cajus Pollmeier and put it in a collab-maint maintained git +repository to get a package I could use. I would very much like +others to help me maintain the package (or just take over, I do not +mind), but as no-one had volunteered so far, I just uploaded it to +NEW. I hope it will be available in Debian in a few days.</p> + +<p>The source is now available from +<a href="http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary">http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary</a>.</p> + + + + + Teaching vmdebootstrap to create Raspberry Pi SD card images + http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html + http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html + Sun, 27 Oct 2013 17:00:00 +0100 + <p>The +<a href="http://packages.qa.debian.org/v/vmdebootstrap.html">vmdebootstrap</a> +program is a a very nice system to create virtual machine images. It +create a image file, add a partition table, mount it and run +debootstrap in the mounted directory to create a Debian system on a +stick. Yesterday, I decided to try to teach it how to make images for +<a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi</a>, as part +of a plan to simplify the build system for +<a href="https://wiki.debian.org/FreedomBox">the FreedomBox +project</a>. The FreedomBox project already uses vmdebootstrap for +the virtualbox images, but its current build system made multistrap +based system for Dreamplug images, and it is lacking support for +Raspberry Pi.</p> + +<p>Armed with the knowledge on how to build "foreign" (aka non-native +architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap +code and adjusted it to be able to build armel images on my amd64 +Debian laptop. I ended up giving vmdebootstrap five new options, +allowing me to replicate the image creation process I use to make +<a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian +Jessie based mesh node images for the Raspberry Pi</a>. First, the +<tt>--foreign /path/to/binfm_handler</tt> option tell vmdebootstrap to +call debootstrap with --foreign and to copy the handler into the +generated chroot before running the second stage. This allow +vmdebootstrap to create armel images on an amd64 host. Next I added +two new options <tt>--bootsize size</tt> and <tt>--boottype +fstype</tt> to teach it to create a separate /boot/ partition with the +given file system type, allowing me to create an image with a vfat +partition for the /boot/ stuff. I also added a <tt>--variant +variant</tt> option to allow me to create smaller images without the +Debian base system packages installed. Finally, I added an option +<tt>--no-extlinux</tt> to tell vmdebootstrap to not install extlinux +as a boot loader. It is not needed on the Raspberry Pi and probably +most other non-x86 architectures. The changes were accepted by the +upstream author of vmdebootstrap yesterday and today, and is now +available from +<a href="http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/">the +upstream project page</a>.</p> + +<p>To use it to build a Raspberry Pi image using Debian Jessie, first +create a small script (the customize script) to add the non-free +binary blob needed to boot the Raspberry Pi and the APT source +list:</p> + +<p><pre> +#!/bin/sh +set -e # Exit on first error +rootdir="$1" +cd "$rootdir" +cat &lt;&lt;EOF > etc/apt/sources.list +deb http://http.debian.net/debian/ jessie main contrib non-free +EOF +# Install non-free binary blob needed to boot Raspberry Pi. This +# install a kernel somewhere too. +wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \ + -O $rootdir/usr/bin/rpi-update +chmod a+x $rootdir/usr/bin/rpi-update +mkdir -p $rootdir/lib/modules +touch $rootdir/boot/start.elf +chroot $rootdir rpi-update +</pre></p> + +<p>Next, fetch the latest vmdebootstrap script and call it like this +to build the image:</p> + +<pre> +sudo ./vmdebootstrap \ + --variant minbase \ + --arch armel \ + --distribution jessie \ + --mirror http://http.debian.net/debian \ + --image test.img \ + --size 600M \ + --bootsize 64M \ + --boottype vfat \ + --log-level debug \ + --verbose \ + --no-kernel \ + --no-extlinux \ + --root-password raspberry \ + --hostname raspberrypi \ + --foreign /usr/bin/qemu-arm-static \ + --customize `pwd`/customize \ + --package netbase \ + --package git-core \ + --package binutils \ + --package ca-certificates \ + --package wget \ + --package kmod +</pre></p> + +<p>The list of packages being installed are the ones needed by +rpi-update to make the image bootable on the Raspberry Pi, with the +exception of netbase, which is needed by debootstrap to find +/etc/hosts with the minbase variant. I really wish there was a way to +set up an Raspberry Pi using only packages in the Debian archive, but +that is not possible as far as I know, because it boots from the GPU +using a non-free binary blob.</p> + +<p>The build host need debootstrap, kpartx and qemu-user-static and +probably a few others installed. I have not checked the complete +build dependency list.</p> + +<p>The resulting image will not use the hardware floating point unit +on the Raspberry PI, because the armel architecture in Debian is not +optimized for that use. So the images created will be a bit slower +than <a href="http://www.raspbian.org/">Raspbian</a> based images.</p> + + + + + Det er jo makta som er mest sårbar ved massiv overvåkning av Internett + http://people.skolelinux.org/pere/blog/Det_er_jo_makta_som_er_mest_s_rbar_ved_massiv_overv_kning_av_Internett.html + http://people.skolelinux.org/pere/blog/Det_er_jo_makta_som_er_mest_s_rbar_ved_massiv_overv_kning_av_Internett.html + Sat, 26 Oct 2013 20:30:00 +0200 + <p>De siste måneders eksponering av +<a href="http://www.aftenposten.no/nyheter/uriks/Her-er-Edvard-Snowdens-mest-omtalte-avsloringer-7351734.html">den +totale overvåkningen som foregår i den vestlige verden dokumenterer +hvor sårbare vi er</a>. Men det slår meg at de som er mest sårbare +for dette, myndighetspersoner på alle nivåer, neppe har innsett at de +selv er de mest interessante personene å lage profiler på, for å kunne +påvirke dem.</p> + +<p>For å ta et lite eksempel: Stortingets nettsted, +<a href="http://www.stortinget.no/">www.stortinget.no</a> (og +forsåvidt også +<a href="http://data.stortinget.no/">data.stortinget.no</a>), +inneholder informasjon om det som foregår på Stortinget, og jeg antar +de største brukerne av informasjonen der er representanter og +rådgivere på Stortinget. Intet overraskende med det. Det som derimot +er mer skjult er at Stortingets nettsted bruker +<a href="http://en.wikipedia.org/wiki/Google_Analytics">Google +Analytics</a>, hvilket gjør at enhver som besøker nettsidene der også +rapporterer om besøket via Internett-linjer som passerer Sverige, +England og videre til USA. Det betyr at informasjon om ethvert besøk +på stortingets nettsider kan snappes opp av svensk, britisk og USAs +etterretningsvesen. De kan dermed holde et øye med hvilke +Stortingssaker stortingsrepresentantene synes er interessante å sjekke +ut, og hvilke sider rådgivere og andre på stortinget synes er +interessant å besøke, når de gjør det og hvilke andre representanter +som sjekker de samme sidene omtrent samtidig. Stortingets bruk av +Google Analytics gjør det dermed enkelt for utenlands etteretning å +spore representantenes aktivitet og interesse. Hvis noen av +representantene bruker Google Mail eller noen andre tjenestene som +krever innlogging, så vil det være enda enklere å finne ut nøyaktig +hvilke personer som bruker hvilke nettlesere og dermed knytte +informasjonen opp til enkeltpersoner på Stortinget.</p> + +<p>Og jo flere nettsteder som bruker Google Analytics, jo bedre +oversikt over stortingsrepresentantenes lesevaner og interesse blir +tilgjengelig for svensk, britisk og USAs etterretning. Hva de kan +bruke den informasjonen til overlater jeg til leseren å undres +over.</p> + + + + + A Raspberry Pi based batman-adv Mesh network node + http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html + http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html + Mon, 21 Oct 2013 11:40:00 +0200 + <p>The last few days I have been experimenting with +<a href="http://www.open-mesh.org/projects/batman-adv/wiki">the +batman-adv mesh technology</a>. I want to gain some experience to see +if it will fit <a href="https://wiki.debian.org/FreedomBox">the +Freedombox project</a>, and together with my neighbors try to build a +mesh network around the park where I live. Batman-adv is a layer 2 +mesh system ("ethernet" in other words), where the mesh network appear +as if all the mesh clients are connected to the same switch.</p> + +<p>My hardware of choice was the Linksys WRT54GL routers I had lying +around, but I've been unable to get them working with batman-adv. So +instead, I started playing with a +<a href="http://www.raspberrypi.org/">Raspberry Pi</a>, and tried to +get it working as a mesh node. My idea is to use it to create a mesh +node which function as a switch port, where everything connected to +the Raspberry Pi ethernet plug is connected (bridged) to the mesh +network. This allow me to hook a wifi base station like the Linksys +WRT54GL to the mesh by plugging it into a Raspberry Pi, and allow +non-mesh clients to hook up to the mesh. This in turn is useful for +Android phones using <a href="http://servalproject.org/">the Serval +Project</a> voip client, allowing every one around the playground to +phone and message each other for free. The reason is that Android +phones do not see ad-hoc wifi networks (they are filtered away from +the GUI view), and can not join the mesh without being rooted. But if +they are connected using a normal wifi base station, they can talk to +every client on the local network.</p> + +<p>To get this working, I've created a debian package +<a href="https://github.com/petterreinholdtsen/meshfx-node">meshfx-node</a> +and a script +<a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/build-rpi-mesh-node">build-rpi-mesh-node</a> +to create the Raspberry Pi boot image. I'm using Debian Jessie (and +not Raspbian), to get more control over the packages available. +Unfortunately a huge binary blob need to be inserted into the boot +image to get it booting, but I'll ignore that for now. Also, as +Debian lack support for the CPU features available in the Raspberry +Pi, the system do not use the hardware floating point unit. I hope +the routing performance isn't affected by the lack of hardware FPU +support.</p> + +<p>To create an image, run the following with a sudo enabled user +after inserting the target SD card into the build machine:</p> + +<p><pre> +% wget -O build-rpi-mesh-node \ + https://raw.github.com/petterreinholdtsen/meshfx-node/master/build-rpi-mesh-node +% sudo bash -x ./build-rpi-mesh-node > build.log 2>&1 +% dd if=/root/rpi/rpi_basic_jessie_$(date +%Y%m%d).img of=/dev/mmcblk0 bs=1M +% +</pre></p> + +<p>Booting with the resulting SD card on a Raspberry PI with a USB +wifi card inserted should give you a mesh node. At least it does for +me with a the wifi card I am using. The default mesh settings are the +ones used by the Oslo mesh project at Hackeriet, as I mentioned in +<a href="http://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">an +earlier blog post about this mesh testing</a>.</p> + +<p>The mesh node was not horribly expensive either. I bought +everything over the counter in shops nearby. If I had ordered online +from the lowest bidder, the price should be significantly lower:</p> + +<p><table> + +<tr><th>Supplier</th><th>Model</th><th>NOK</th></tr> +<tr><td>Teknikkmagasinet</td><td>Raspberry Pi model B</td><td>349.90</td></tr> +<tr><td>Teknikkmagasinet</td><td>Raspberry Pi type B case</td><td>99.90</td></tr> +<tr><td>Lefdal</td><td>Jensen Air:Link 25150</td><td>295.-</td></tr> +<tr><td>Clas Ohlson</td><td>Kingston 16 GB SD card</td><td>199.-</td></tr> +<tr><td>Total cost</td><td></td><td>943.80</td></tr> + +</table></p> + +<p>Now my mesh network at home consist of one laptop in the basement +connected to my production network, one Raspberry Pi node on the 1th +floor that can be seen by my neighbor across the park, and one +play-node I use to develop the image building script. And some times +I hook up my work horse laptop to the mesh to test it. I look forward +to figuring out what kind of latency the batman-adv setup will give, +and how much packet loss we will experience around the park. :)</p> + + + + + Perl library to control the Spykee robot moved to github + http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html + http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html + Sat, 19 Oct 2013 10:20:00 +0200 + <p>Back in 2010, I created a Perl library to talk to +<a href="http://en.wikipedia.org/wiki/Spykee">the Spykee robot</a> +(with two belts, wifi, USB and Linux) and made it available from my +web page. Today I concluded that it should move to a site that is +easier to use to cooperate with others, and moved it to github. If +you got a Spykee robot, you might want to check out +<a href="https://github.com/petterreinholdtsen/libspykee-perl">the +libspykee-perl github repository</a>.</p> + + + Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html @@ -226,756 +713,5 @@ lvresize + resize2fs in tty 2 while installing).</p> - - Videos about the Freedombox project - for inspiration and learning - http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html - http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html - Fri, 27 Sep 2013 14:10:00 +0200 - <p>The <a href="http://www.freedomboxfoundation.org/">Freedombox -project</a> have been going on for a while, and have presented the -vision, ideas and solution several places. Here is a little -collection of videos of talks and presentation of the project.</p> - -<ul> - -<li><a href="http://www.youtube.com/watch?v=ukvUz5taxvA">FreedomBox - -2,5 minute marketing film</a> (Youtube)</li> - -<li><a href="http://www.youtube.com/watch?v=SzW25QTVWsE">Eben Moglen -discusses the Freedombox on CBS news 2011</a> (Youtube)</li> - -<li><a href="http://www.youtube.com/watch?v=Ae8SZbxfE0g">Eben Moglen - -Freedom in the Cloud - Software Freedom, Privacy and and Security for -Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010</a> -(Youtube)</li> - -<li><a href="http://www.youtube.com/watch?v=vNaIji_3xBE">Fosdem 2011 -Keynote by Eben Moglen presenting the Freedombox</a> (Youtube)</li> - -<li><a href="http://www.youtube.com/watch?v=9bDDUyJSQ9s">Presentation of -the Freedombox by James Vasile at Elevate in Gratz 2011</a> (Youtube)</li> - -<li><a href="http://www.youtube.com/watch?v=zQTmnk27g9s"> Freedombox - -Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New -York City in 2012</a> (Youtube)</li> - -<li><a href="http://www.youtube.com/watch?v=tkbSB4Ba7Ck">Introduction -to the Freedombox at Freedombox Hackfest New York City in 2012</a> -(Youtube)</li> - -<li><a href="http://www.youtube.com/watch?v=z-P2Jaeg0aQ">Freedom, Out -of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012</a> (Youtube) </li> - -<li><a href="https://archive.fosdem.org/2013/schedule/event/freedombox/">Freedombox -1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013</a> (FOSDEM) </li> - -<li><a href="http://www.youtube.com/watch?v=e1LpYX2zVYg">What is the -FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus -2013</a> (Youtube)</li> - -</ul> - -<p>A larger list is available from -<a href="https://wiki.debian.org/FreedomBox/TalksAndPresentations">the -Freedombox Wiki</a>.</p> - -<p>On other news, I am happy to report that Freedombox based on Debian -Jessie is coming along quite well, and soon both Owncloud and using -Tor should be available for testers of the Freedombox solution. :) In -a few weeks I hope everything needed to test it is included in Debian. -The withsqlite package is already in Debian, and the plinth package is -pending in NEW. The third and vital part of that puzzle is the -metapackage/setup framework, which is still pending an upload. 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> - - - - - Third and probably last beta release of Debian Edu Wheezy - http://people.skolelinux.org/pere/blog/Third_and_probably_last_beta_release_of_Debian_Edu_Wheezy.html - http://people.skolelinux.org/pere/blog/Third_and_probably_last_beta_release_of_Debian_Edu_Wheezy.html - Mon, 16 Sep 2013 21:30:00 +0200 - <p>The third wheezy based beta release of Debian Edu was wrapped up -today. This is the release announcement from Holger Levsen:</p> - -<blockquote> -<p>Hi,</p> - -<p>it is my pleasure to announce the third beta release (beta 2 for -short) of <a href="http://www.skolelinux.org/">Debian Edu / -Skolelinux</a> based on Debian Wheezy!</p> - -<p>Please test these images extensivly, if no new problems are found -we plan to do this final Debian Edu Wheezy release this coming -weekend. We are not aware of any major problems or blockers in beta2, -if you find something, please notify us immediately!</p> - -<p>(More about the remaining steps for the Edu Wheezy release in -another mail to the edu list tonight or tomorrow...)</p> - -<p>Noteworthy changes and software updates for Debian Edu 7.1+edu0~b2 -compared to beta1:</p> - -<ul> - -<li>The KDE proxy setup has been adjusted to use the provided wpad.dat. This -also gets Chromium to use this proxy.</li> -<li>Install kdepim-groupware with KDE desktops to make sure korganizer -understand ical/dav sources.</li> -<li>Increased default maximum size of /var/spool/squid and /skole/backup on the -main server.</li> -<li>A source DVD image containing all source packages is now available as well.</li> -<li>Updates for chromium (29.0.1547.57-1~deb7u1), imagemagick -(6.7.7.10-5+deb7u2), php5 (5.4.4-14+deb7u4), libmodplug -(0.8.8.4-3+deb7u1+git20130828), tiff (4.0.2-6+deb7u2), linux-image -(3.2.0-4-486_3.2.46-1+deb7u1).</li> - -</ul> - -<p>Where to get it:</p> - -<p>To download the multiarch netinstall CD release you can use</p> - -<ul> -<li><a href="ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-CD.iso">ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-CD.iso</a></li> -<li><a href="http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-CD.iso">http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-CD.iso</a></li> -<li>rsync -avzP ftp.skolelinux.org::skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-CD.iso .</li> -</ul> - -<p>The SHA1SUM of this image is: 3a1c89f4666df80eebcd46c5bf5fedb866f9472f</p> - -<p>To download the multiarch USB stick ISO release you can use -<ul> -<li><a href="ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-USB.iso">ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-USB.iso</a></li> -<li><a href="http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-USB.iso">http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-USB.iso</a></li> -<li>rsync -avzP ftp.skolelinux.org::skolelinux-cd/wheezy/debian-edu-7.1+edu0~b2-USB.iso .</li> -</ul> - -<p>The SHA1SUM of this image is: 702d1718548f401c74bfa6df9f032cc3ee16597e</p> - -<p>The Source DVD image has the filename -debian-edu-7.1+edu0~b2-source-DVD.iso and the SHA1SUM -089eed8b3f962db47aae1f6a9685e9bb2fa30ca5 and is available the same way -as the other isos.</p> - -<p>How to report bugs</p> - -<p>For information how to report bugs please see -<br><a href="http://wiki.debian.org/DebianEdu/HowTo/ReportBugs">http://wiki.debian.org/DebianEdu/HowTo/ReportBugs</a></p> - - -<p>About Debian Edu and Skolelinux</p> - -<p>Debian Edu, also known as Skolelinux, is a Linux distribution based -on Debian providing an out-of-the box environment of a completely -configured school network. Immediately after installation a school -server running all services needed for a school network is set up just -waiting for users and machines being added via GOsa², a comfortable -Web-UI. A netbooting environment is prepared using PXE, so after -initial installation of the main server from CD or USB stick all other -machines can be installed via the network. The provided school server -provides LDAP database and Kerberos authentication service, -centralized home directories, DHCP server, web proxy and many other -services. The desktop contains more than 60 educational software -packages and more are available from the Debian archive, and schools -can choose between KDE, Gnome, LXDE and Xfce desktop environment.</p> - -<p>This is the seventh test release based on Debian Wheezy. Basically -this is an updated and slightly improved version compared to the -Squeeze release.</p> - -<p>Notes for upgrades from Alpha Prereleases</p> - -<p>Alpha based installations should reinstall or downgrade the -versions of gosa and libpam-mklocaluser to the ones used in this beta -release. Both alpha and beta0 based installations should reinstall or -deal with gosa.conf manually; there are two options: (1) Keep -gosa.conf and edit this file as outlined on the mailing list. (2) -Accept the new version of gosa.conf and replace both contained admin -password placeholders with the password hashes found in the old one -(backup copy!). In both cases all users need to change their password -to make sure a password is set for CIFS access to their home -directory.</p> - - -<p>cheers, -<br> Holger</p> -</blockquote> - - - - - Recipe to test the Freedombox project on amd64 or Raspberry Pi - http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html - http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html - Tue, 10 Sep 2013 14:20:00 +0200 - <p>I was introduced to the -<a href="http://www.freedomboxfoundation.org/">Freedombox project</a> -in 2010, when Eben Moglen presented his vision about serving the need -of non-technical people to keep their personal information private and -within the legal protection of their own homes. The idea is to give -people back the power over their network and machines, and return -Internet back to its intended peer-to-peer architecture. Instead of -depending on a central service, the Freedombox will give everyone -control over their own basic infrastructure.</p> - -<p>I've intended to join the effort since then, but other tasks have -taken priority. But this summers nasty news about the misuse of trust -and privilege exercised by the "western" intelligence gathering -communities increased my eagerness to contribute to a point where I -actually started working on the project a while back.</p> - -<p>The <a href="https://alioth.debian.org/projects/freedombox/">initial -Debian initiative</a> based on the vision from Eben Moglen, is to -create a simple and cheap Debian based appliance that anyone can hook -up in their home and get access to secure and private services and -communication. The initial deployment platform have been the -<a href="http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx">Dreamplug</a>, -which is a piece of hardware I do not own. So to be able to test what -the current Freedombox setup look like, I had to come up with a way to install -it on some hardware I do have access to. I have rewritten the -<a href="https://github.com/NickDaly/freedom-maker">freedom-maker</a> -image build framework to use .deb packages instead of only copying -setup into the boot images, and thanks to this rewrite I am able to -set up any machine supported by Debian Wheezy as a Freedombox, using -the previously mentioned deb (and a few support debs for packages -missing in Debian).</p> - -<p>The current Freedombox setup consist of a set of bootstrapping -scripts -(<a href="https://github.com/petterreinholdtsen/freedombox-setup">freedombox-setup</a>), -and a administrative web interface -(<a href="https://github.com/NickDaly/Plinth">plinth</a> + exmachina + -withsqlite), as well as a privacy enhancing proxy based on -<a href="http://packages.qa.debian.org/privoxy">privoxy</a> -(freedombox-privoxy). There is also a web/javascript based XMPP -client (<a href="http://packages.qa.debian.org/jwchat">jwchat</a>) -trying (unsuccessfully so far) to talk to the XMPP server -(<a href="http://packages.qa.debian.org/ejabberd">ejabberd</a>). The -web interface is pluggable, and the goal is to use it to enable OpenID -services, mesh network connectivity, use of TOR, etc, etc. Not much of -this is really working yet, see -<a href="https://github.com/NickDaly/freedombox-todos/blob/master/TODO">the -project TODO</a> for links to GIT repositories. Most of the code is -on github at the moment. The HTTP proxy is operational out of the -box, and the admin web interface can be used to add/remove plinth -users. I've not been able to do anything else with it so far, but -know there are several branches spread around github and other places -with lots of half baked features.</p> - -<p>Anyway, if you want to have a look at the current state, the -following recipes should work to give you a test machine to poke -at.</p> - -<p><strong>Debian Wheezy amd64</strong></p> - -<ol> - -<li>Fetch normal Debian Wheezy installation ISO.</li> -<li>Boot from it, either as CD or USB stick.</li> -<li><p>Press [tab] on the boot prompt and add this as a boot argument -to the Debian installer:<p> -<pre>url=<a href="http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat</a></pre></li> - -<li>Answer the few language/region/password questions and pick disk to -install on.</li> - -<li>When the installation is finished and the machine have rebooted a -few times, your Freedombox is ready for testing.</li> - -</ol> - -<p><strong>Raspberry Pi Raspbian</strong></p> - -<ol> - -<li>Fetch a Raspbian SD card image, create SD card.</li> -<li>Boot from SD card, extend file system to fill the card completely.</li> -<li><p>Log in and add this to /etc/sources.list:</p> -<pre> -deb <a href="http://www.reinholdtsen.name/freedombox/">http://www.reinholdtsen.name/freedombox</a> wheezy main -</pre></li> -<li><p>Run this as root:</p> -<pre> -wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \ - apt-key add - -apt-get update -apt-get install freedombox-setup -/usr/lib/freedombox/setup -</pre></li> -<li>Reboot into your freshly created Freedombox.</li> - -</ol> - -<p>You can test it on other architectures too, but because the -freedombox-privoxy package is binary, it will only work as intended on -the architectures where I have had time to build the binary and put it -in my APT repository. But do not let this stop you. It is only a -short "<tt>apt-get source -b freedombox-privoxy</tt>" away. :)</p> - -<p>Note that by default Freedombox is a DHCP server on the -192.168.1.0/24 subnet, so if this is your subnet be careful and turn -off the DHCP server by running "<tt>update-rc.d isc-dhcp-server -disable</tt>" as root.</p> - -<p>Please let me know if this works for you, or if you have any -problems. We gather on the IRC channel -<a href="irc://irc.debian.org:6667/%23freedombox">#freedombox</a> on -irc.debian.org and the -<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss">project -mailing list</a>.</p> - -<p>Once you get your freedombox operational, you can visit -<tt>http://your-host-name:8001/</tt> to see the state of the plint -welcome screen (dead end - do not be surprised if you are unable to -get past it), and next visit <tt>http://your-host-name:8001/help/</tt> -to look at the rest of plinth. The default user is 'admin' and the -default password is 'secret'.</p> - - - - - Datalagringsdirektivet gjør at Oslo Høyre og Arbeiderparti ikke får min stemme i år - http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_gj_r_at_Oslo_H_yre_og_Arbeiderparti_ikke_f_r_min_stemme_i__r.html - http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_gj_r_at_Oslo_H_yre_og_Arbeiderparti_ikke_f_r_min_stemme_i__r.html - Sun, 8 Sep 2013 20:40:00 +0200 - <p>I 2011 raderte et stortingsflertall bestående av Høyre og -Arbeiderpartiet vekk en betydelig del av privatsfæren til det norske -folk. Det ble vedtatt at det skulle registreres og lagres i et halvt -år hvor alle som bærer på en mobiltelefon befinner seg, hvem de -snakker med og hvor lenge de snakket sammen. Det skal også -registreres hvem de sendte SMS-meldinger til, hvem en har sendt epost -til, og hvilke nett-tjenere en besøkte. Saken er kjent som -<a href="http://beta.holderdeord.no/issues/innfore-datalagringsdirektivet">Datalagringsdirektivet -(DLD)</a>, og innebærer at alle innbyggerne og andre innenfor Norges -grenser overvåkes døgnet rundt. Det ble i praksis innført brev og -besøkskontroll av hele befolkningen. Rapporter fra de landene som -allerede har innført slik total lagring av borgernes -kommunikasjonsmønstre forteller at det ikke hjelper i -kriminalitetsbekjempelsen. Den norske prislappen blir mange hundre -millioner, uten at det ser ut til å bidra positivt til politiets -arbeide. Jeg synes flere hundre millioner i stedet burde vært brukt -på noe som kan dokumenteres å ha effekt i kriminalitetsbekjempelsen. -Se mer på -<a href="http://no.wikipedia.org/wiki/Datalagringsdirektivet">Wikipedia</a> -og <a href="http://www.uhuru.biz/?cat=84">Jon Wessel-Aas</a>.</p> - -<p>Hva er problemet, tenkter du kanskje? Et åpenbart problem er at -medienes kildevern i praksis blir radert ut. Den innsamlede -informasjonen gjør det mulig å finne ut hvem som har snakket med -journalister på telefon, SMS og epost, og hvem som har vært i nærheten -av journalister så sant begge bar med seg en telefon. Et annet er at -advokatvernet blir sterkt redusert, der politiet kan finne ut hvem -som har snakket med en advokat når, eller vært i møter en med advokat. -Et tredje er at svært personlig informasjon kan avledes fra hvilke -nettsteder en har besøkt. Har en besøkt hivnorge.no, -swingersnorge.com eller andre sider som kan brukes til avlede -interesser som hører til privatsfæren, vil denne informasjonen være -tilgjengelig takket være datalagringsdirektivet.</p> - -<p>De fleste partiene var mot, kun to partier stemte for. Høyre og -Arbeiderpartiet. Og både Høyre og Arbeiderpartiet i Oslo har -DLD-forkjempere på toppen av sine lister (har ikke sjekket de andre -fylkene). Det er dermed helt uaktuelt for meg å stemme på disse -partiene. Her er oversikten over partienes valglister i Oslo, med -informasjon om hvem som stemte hva i første DLD-votering i Stortinget, -basert på informasjon fra mine venner i -<a href="http://beta.holderdeord.no/votes/1301946411e">Holder de -Ord</a> samt <a href="http://data.stortinget.no/">data.stortinget.no</a>. -Først ut er stortingslista fra Høyre for Oslo:</p> - -<style type="text/css"> -.for {background-color:#F5A9A9;} -.mot {background-color:#A9F5BC;} -.ukjent { } -</style> - -<table> -<tr><th>#</th><th>Navn, fødselsår og valgkrets</th><th>Stemme/kommentar</th></tr> - -<tr class="for"><td>1.</td> -<td>Ine Marie Eriksen Søreide (1976), Gamle Oslo</td> -<td>Stemte for DLD</td></tr> - -<tr class="mot"><td>2.</td> -<td>Nikolai Astrup (1978), Frogner</td> -<td>Stemte mot DLD</td></tr> - -<tr class="mot"><td>3.</td> -<td>Michael Tetzschner (1954), Vestre Aker</td> -<td>Stemte mot DLD</td> - -<tr class="ukjent"><td>4.</td> -<td>Kristin Vinje (1963), Nordre Aker</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>5.</td> -<td>Mudassar Hussain Kapur (1976), Nordstrand</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>6.</td> -<td>Stefan Magnus B. Heggelund (1984), Grünerløkka</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>7.</td> -<td>Heidi Nordby Lunde (1973), Grünerløkka</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>8.</td> -<td>Frode Helgerud (1950), Frogner</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>9.</td> -<td>Afshan Rafiq (1975), Stovner</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>10.</td> -<td>Astrid Nøklebye Heiberg (1936), Frogner</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>11.</td> -<td>Camilla Strandskog (1984) St.Hanshaugen</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>12.</td> -<td>John Christian Elden (1967), Ullern</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>13.</td> -<td>Berit Solli (1972), Alna</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>14.</td> -<td>Ola Kvisgaard (1963), Frogner</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>15.</td> -<td>James Stove Lorentzen (1957), Vestre Aker</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>16.</td> -<td>Gülsüm Koc (1987), Stovner</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>17.</td> -<td>Jon Ole Whist (1976), Grünerløkka</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>18.</td> -<td>Maren Eline Malthe-Sørenssen (1971), Vestre Aker</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>19.</td> -<td>Ståle Hagen (1968), Søndre Nordstrand</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>20.</td> -<td>Kjell Omdal Erichsen (1978), Sagene</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>21.</td> -<td>Saida R. Begum (1987), Grünerløkka</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>22.</td> -<td>Torkel Brekke (1970), Nordre Aker</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>23.</td> -<td>Sverre K. Seeberg (1950), Vestre Aker</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>24.</td> -<td>Julie Margrethe Brodtkorb (1974), Ullern</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td>25.</td> -<td>Fabian Stang (1955), Frogner</td> -<td>Ikke til stede</td></tr> - -</table> - -<p>Deretter har vi stortingslista fra Arbeiderpartiet for Oslo:</p> - -<table> - -<tr><th>#</th><th>Navn, fødselsår og valgkrets</th><th>Stemme/kommentar</th></tr> - -<tr class="for"><td>1.</td> -<td>Jens Stoltenberg (1959), Frogner</td> -<td>Ikke til stede i Stortinget, leder av regjeringen som fremmet forslaget</td></tr> - -<tr class="for"><td>2.</td> -<td>Hadia Tajik (1983), Grünerløkka</td> -<td>Stemte for DLD</td></tr> - -<tr class="for"><td> 3.</td> -<td>Jonas Gahr Støre (1960), Vestre Aker</td> -<td>Ikke til stede i Stortinget, medlem av regjeringen som fremmet forslaget</td></tr> - -<tr class="for"><td> 4.</td> -<td>Marianne Marthinsen (1980), Grünerløkka</td> -<td>Stemte for DLD</td></tr> - -<tr class="for"><td> 5.</td> -<td>Jan Bøhler (1952), Alna</td> -<td>Stemte for DLD</td></tr> - -<tr class="for"><td> 6.</td> -<td>Marit Nybakk (1947), Frogner</td> -<td>Stemte for DLD</td></tr> - -<tr class="for"><td> 7.</td> -<td>Truls Wickholm (1978), Sagene</td> -<td>Stemte for DLD</td></tr> - -<tr class="ukjent"><td> 8.</td> -<td>Prableen Kaur (1993), Grorud</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 9.</td> -<td>Vegard Grøslie Wennesland (1983), St.Hanshaugen</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 10.</td> -<td>Inger Helene Vaaten (1975), Grorud</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 11.</td> -<td>Ivar Leveraas (1939), Alna</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 12.</td> -<td>Grete Haugdal (1971), Gamle Oslo</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 13.</td> -<td>Olav Tønsberg (1948), Alna</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 14.</td> -<td>Khamshajiny Gunaratnam (1988), Grorud</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 15.</td> -<td>Fredrik Mellem (1969), Sagene</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 16.</td> -<td>Brit Axelsen (1945), Stovner</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 17.</td> -<td>Dag Bayegan-Harlem (1977), Ullern</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 18.</td> -<td>Kristin Sandaker (1963), Østeinsjø</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 19.</td> -<td>Bashe Musse (1965), Grünerløkka</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 20.</td> -<td>Torunn Kanutte Husvik (1983), St. Hanshaugen</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 21.</td> -<td>Steinar Andersen (1947), Nordstrand</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 22.</td> -<td>Anne Cathrine Berger (1972), Sagene</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 23.</td> -<td>Khalid Mahmood (1959), Østensjø</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 24.</td> -<td>Munir Jaber (1990), Alna</td> -<td>Ikke til stede</td></tr> - -<tr class="ukjent"><td> 25.</td> -<td>Libe Solberg Rieber-Mohn (1965), Frogner</td> -<td>Ikke til stede</td></tr> - -</table> - -<p>Hvilket parti får så min stemme i år. Jeg tror det blir -<a href="http://piratpartiet.no/">Piratpartiet</a>. Hvis de kan bidra -til at det kommer noen inn på Stortinget med teknisk peiling, så får -kanskje ikke overvåkningsgalskapen like fritt spillerom som det har -hatt så langt.</p> - - - - - - Second beta release (beta 1) of Debian Edu/Skolelinux based on Debian Wheezy - http://people.skolelinux.org/pere/blog/Second_beta_release__beta_1__of_Debian_Edu_Skolelinux_based_on_Debian_Wheezy.html - http://people.skolelinux.org/pere/blog/Second_beta_release__beta_1__of_Debian_Edu_Skolelinux_based_on_Debian_Wheezy.html - Thu, 22 Aug 2013 09:30:00 +0200 - <p>The second wheezy based beta release of Debian Edu was wrapped up -today, slightly delayed because of some bugs in the initial Windows -integration fixes . This is the release announcement:</p> - -<p><strong>New features for Debian Edu 7.1+edu0~b1 released 2013-08-22</strong></p> - -<p>These are the release notes for Debian Edu / Skolelinux -7.1+edu0~b1, based on Debian with codename "Wheezy".</p> - -<p><strong>About Debian Edu and Skolelinux</strong></p> - -<p><a href="http://www.skolelinux.org/">Debian Edu, also known as -Skolelinux</a>, is a Linux distribution based on Debian providing an -out-of-the box environment of a completely configured school -network. Immediately after installation a school server running all -services needed for a school network is set up just waiting for users -and machines being added via GOsa², a comfortable Web-UI. A netbooting -environment is prepared using PXE, so after initial installation of -the main server from CD or USB stick all other machines can be -installed via the network. The provided school server provides LDAP -database and Kerberos authentication service, centralized home -directories, DHCP server, web proxy and many other services. The -desktop contains -<a href="http://people.skolelinux.org/pere/blog/Educational_applications_included_in_Debian_Edu___Skolelinux__the_screenshot_collection____.html">more -than 60 educational software packages</a> and more are available from -the Debian archive, and schools can choose between KDE, Gnome, LXDE -and Xfce desktop environment.</p> - -<p>This is the sixth test release based on Debian Wheezy. Basically this -is an updated and slightly improved version compared to the Squeeze -release.</p> - -<p>ALERT: Alpha based installations should reinstall or downgrade the -versions of gosa and libpam-mklocaluser to the ones used in this beta -release. Both alpha and beta0 based installations should reinstall or -deal with gosa.conf manually; there are two options: (1) Keep -gosa.conf and edit this file as outlined -<a href="http://lists.debian.org/debian-edu/2013/08/msg00127.html">on -the mailing list</a>. (2) Accept the new version of gosa.conf and -replace both contained admin password placeholders with the password -hashes found in the old one (backup copy!). In both cases every user -need to change their their password to make sure a password is set for -CIFS access to their home directory.</p> - -<p><strong>Software updates</strong></p> - -<ul> - -<li>Added ssh askpass packages to default installation, to ensure ssh - work also without a attached tty.</li> -<li>Add the command-not-found package to the default installation to - make it easier to figure out where to find missing command line - tools. Please note, that the command 'update-command-not-found' - has to be run as root to actually make it useful (internet access - required).</li> - -</ul> - -<p><strong>Other changes</strong></p> - -<ul> - -<li>Adjusted the USB stick ISO image build to include every tool -needed for desktop=xfce installations.</li> -<li>Adjust thin-client-server task to work when installing from USB -stick ISO image.</li> -<li>Made new grub artwork (changed png from indexed to RGB format).</li> -<li>Minor cleanup in the CUPS setup.</li> -<li>Make sure that bootstrapping of the Samba domain really happens - during installation of the main server and adjust SID handling to - cope with this.</li> -<li>Make Samba passwords changeable (again) via GOsa².</li> -<li>Fix generation of LM and NT password hashes via GOsa² to avoid - empty password hashes.</li> -<li>Adapted Samba machine domain joining to latest change in the - smbldap-tools Perl package, fixing bugs blocking Windows machines - from joining the Samba domain.</li> - -</ul> - -<p><strong>Known issues</strong></p> - -<ul> - -<li>KDE fails to understand the wpad.dat file provided, causing it to - not use the http proxy as it should.</li> -<li>Chromium also fails to use the proxy when using the KDE desktop - (using the KDE configuration).</li> - -</ul> - -<p><strong>Where to get it</strong></p> - -<p>To download the multiarch netinstall CD release you can use</p> - -<ul> - -<li><a href="ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-CD.iso">ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-CD.iso</a></li> - -<li><a href="http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-CD.iso">http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-CD.iso</a></li> - -<li>rsync -avzP ftp.skolelinux.org::skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-CD.iso .</li> - -</ul> - -<p>The MD5SUM of this image is: 1e357f80b55e703523f2254adde6d78b -<br>The SHA1SUM of this image is: 7157f9be5fd27c7694d713c6ecfed61c3edda3b2</p> - -<p>To download the multiarch USB stick ISO release you can use</p> - -<ul> - -<li><a href="ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-USB.iso">ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-USB.iso</a></li> -<li><a href="http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-USB.iso">http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-USB.iso</a></li> -<li>rsync -avzP ftp.skolelinux.org::skolelinux-cd/wheezy/debian-edu-7.1+edu0~b1-USB.iso .</li> - -</ul> - -<p>The MD5SUM of this image is: 7a8408ead59cf7e3cef25afb6e91590b -<br>The SHA1SUM of this image is: f1817c031f02790d5edb3bfa0dcf8451088ad119</p> - - -<p><strong>How to report bugs</strong></p> - -<p><a href="http://wiki.debian.org/DebianEdu/HowTo/ReportBugs">http://wiki.debian.org/DebianEdu/HowTo/ReportBugs</a> - - - - - Intel 180 SSD disk with Lenovo firmware can not use Intel firmware - http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html - http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html - Sun, 18 Aug 2013 14:00:00 +0200 - <p>Earlier, I reported about -<a href="http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html">my -problems using an Intel SSD 520 Series 180 GB disk</a>. Friday I was -told by IBM that the original disk should be thrown away. And as -there no longer was a problem if I bricked the firmware, I decided -today to try to install Intel firmware to replace the Lenovo firmware -currently on the disk.</p> - -<p>I searched the Intel site for firmware, and found -<a href="https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3472&DwnldID=18363&ProductFamily=Solid-State+Drives+and+Caching&ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive&ProductProduct=Intel%c2%ae+SSD+520+Series+(180GB%2c+2.5in+SATA+6Gb%2fs%2c+25nm%2c+MLC)&lang=eng">issdfut_2.0.4.iso</a> -(aka Intel SATA Solid-State Drive Firmware Update Tool) which -according to the site should contain the latest firmware for SSD -disks. I inserted the broken disk in one of my spare laptops and -booted the ISO from a USB stick. The disk was recognized, but the -program claimed the newest firmware already were installed and refused -to insert any Intel firmware. So no change, and the disk is still -unable to handle write load. :( I guess the only way to get them -working would be if Lenovo releases new firmware. No idea how likely -that is. Anyway, just blogging about this test for completeness. I -got a working Samsung disk, and see no point in spending more time on -the broken disks.</p> - - -