It has been a while since my last update. Since last summer, I -have worked on a Norwegian -docbook version of the 2004 book -Free Culture by Lawrence Lessig, -to get a Norwegian text explaining the problems with the copyright -law. Yesterday, I finally broken the 90% mark, when counting the -number of strings to translate. Due to real life constraints, I have -not had time to work on it since March, but when the summer broke out, -I found time to work on it again. Still lots of work left, but the -first draft is nearing completion. I created a graph to show the -progress of the translation:
- -When the first draft is done, the translated text need to be -proof read, and the remaining formatting problems with images and SVG -drawings need to be fixed. There are probably also some index entries -missing that need to be added. This can be done by comparing the -index entries listed in the SiSU version of the book, or comparing the -English docbook version with the paper version. Last, the colophon -page with ISBN numbers etc need to be wrapped up before the release is -done. I should also figure out how to get correct Norwegian sorting -of the index pages. All docbook tools I have tried so far (xmlto, -docbook-xsl, dblatex) get the order of symbols and the special -Norwegian letters ÃÃÃ wrong.
- -There is still need for translators and people with docbook -knowledge, to be able to get a good looking book (I still struggle -with dblatex, xmlto and docbook-xsl) as well as to do the draft -translation and proof reading. And I would like the figures to be -redrawn as SVGs to make it easy to translate them. Any SVG master -around? There are also some legal terms that are unfamiliar to me. -If you want to help, please get in touch with me, and check out the -project files currently available from -github.
- -If you are curious what the translated book currently look like, -the updated -PDF -and -EPUB -are published on github. The HTML version is published as well, but -github hand it out with MIME type text/plain, confusing browsers, so I -saw no point in linking to that version.
+ +The Freedombox +project 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).
+ +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 +vmdebootstrap +with a user with sudo access to become root: + +
+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 ++ +
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 race condition in +vmdebootstrap, the build might fail without the patch to the +kpartx call.
+ +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:
+ ++url=http://www.reinholdtsen.name/freedombox/preseed-jessie.dat ++ +
But note that due to a +recently introduced bug in apt in Jessie, the installer will +currently hang while setting up APT sources. Killing the +'apt-cdrom ident' 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.
+ +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 +IRC (#freedombox on +irc.debian.org) and +the +mailing list if you want to help make this vision come true.The first wheezy based beta release of Debian Edu was wrapped up -today. This is the release announcement:
- -New features for Debian Edu 7.1+edu0~b0 released -2013-07-27
- -These are the release notes for for Debian Edu / Skolelinux -7.1+edu0~b0, based on Debian with codename "Wheezy".
- -About Debian Edu and Skolelinux
- -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, DVD 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.
- -This is the fifth test release based on Debian Wheezy. Basically -this is an updated and slightly improved version compared to the -Squeeze release.
- -ALERT: Alpha based installations should reinstall or downgrade the -versions of gosa and libpam-mklocaluser to the ones used in this beta -release.
- -Software updates
+ +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 Debian Edu / Skolelinux, 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 +Skolelinux Drift AS, where I am +on the board of directors, asked about how to do this. The steps to +get this working are the following:
+ +-
+
+
- Add new storage server in DNS. I use nas-server.intern as the +example host here. + +
- Add automoun LDAP information about this server in LDAP, to allow +all clients to automatically mount it on reqeust. + +
- Add the relevant entries in tjener.intern:/etc/fstab, because +tjener.intern do not use automount to avoid mounting loops. + +
DNS entries are added in GOsa², and not described here. Follow the +instructions +in the manual (Machine Management with GOsa² in section Getting +started).
+ +Ensure that the NFS export points on the server are exported to the +relevant subnets or machines:
+ ++ ++root@tjener:~# showmount -e nas-server +Export list for nas-server: +/storage 10.0.0.0/8 +root@tjener:~# +
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.
+ +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.
+ ++ ++ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no +
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.
+ ++ ++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:/& +
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.
+ +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.
+For noen uker siden ble NXCs fri programvarelisenserte +NOARK5-løsning +presentert hos +NUUG (video +på youtube +foreløbig), og det fikk meg til å titte litt mer på NOARK5, +standarden for arkivhåndtering i det offentlige Norge. Jeg lurer på +om denne kjernen kan være nyttig i et par av mine prosjekter, og for ett +av dem er det mest aktuelt å lagre epost. Jeg klarte ikke finne noen +anbefaling om hvordan RFC 822-formattert epost (aka Internett-epost) +burde lagres i NOARK5, selv om jeg vet at noen arkiver tar +PDF-utskrift av eposten med sitt epostprogram og så arkiverer PDF-en +(eller enda værre, tar papirutskrift og lagrer bildet av eposten som +PDF i arkivet).
+ +Det er ikke så mange formater som er akseptert av riksarkivet til +langtidsoppbevaring av offentlige arkiver, og PDF og XML er de mest +aktuelle i så måte. Det slo meg at det måtte da finnes en eller annen +egnet XML-representasjon og at det kanskje var enighet om hvilken som +burde brukes, så jeg tok mot til meg og spurte +SAMDOK, en gruppe tilknyttet +arkivverket som ser ut til å jobbe med NOARK-samhandling, om de hadde +noen anbefalinger: + +
++ +Hei.
+ +Usikker på om dette er riktig forum å ta opp mitt spørsmål, men jeg +lurer på om det er definert en anbefaling om hvordan RFC +822-formatterte epost (aka vanlig Internet-epost) bør lages håndteres +i NOARK5, slik at en bevarer all informasjon i eposten +(f.eks. Received-linjer). Finnes det en anbefalt XML-mapping ala den +som beskrives på +<URL: https://www.informit.com/articles/article.aspx?p=32074 >? Mitt +mål er at det skal være mulig å lagre eposten i en NOARK5-kjerne og +kunne få ut en identisk formattert kopi av opprinnelig epost ved +behov.
+
Postmottaker hos SAMDOK mente spørsmålet heller burde stilles +direkte til riksarkivet, og jeg fikk i dag svar derfra formulert av +seniorrådgiver Geir Ivar Tungesvik:
+ +++ +Riksarkivet har ingen anbefalinger når det gjelder konvertering fra +e-post til XML. Det står arkivskaper fritt å eventuelt definere/bruke +eget format. Inklusive da - som det spørres om - et format der det er +mulig å re-etablere e-post format ut fra XML-en. XML (e-post) +dokumenter må være referert i arkivstrukturen, og det må vedlegges et +gyldig XML skjema (.xsd) for XML-filene. Arkivskaper står altså fritt +til å gjøre hva de vil, bare det dokumenteres og det kan dannes et +utrekk ved avlevering til depot.
+ +De obligatoriske kravene i Noark 5 standarden må altså oppfylles - +etter dialog med Riksarkivet i forbindelse med godkjenning. For +offentlige arkiv er det særlig viktig med filene loependeJournal.xml +og offentligJournal.xml. Private arkiv som vil forholde seg til Noark +5 standarden er selvsagt frie til å bruke det som er relevant for dem +av obligatoriske krav.
+
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 kommet over flere aktuelle beskrivelser (søk på "rfc 822 +xml", så finner du aktuelle alternativer).
-
-
- Switched roaming workstation profiles from wicd to network-manager - for network configuration, as wicd didn't work any more. -
- Changed version numbers of patched gosa and libpam-mklocaluser - packages to make sure our locally patched versions will be replaced - by the official packages when they are released from Debian. Those - installing alpha version need to reinstall or manually downgrade gosa - and libpam-mklocaluser. -
- Added bluetooth tools to the default desktop (bluedevil, blueman). -
- Added tools for sharing the desktop on KDE (krdc, krfb). -
- Added valgrind to the default installation for easier debugging of - crash bugs. - -
Other changes
+-
+
- An +XML format for mail and other messages utkast fra IETF datert +2001. -
- Fixed artwork package to work with gnome, no longer break - desktop=gnome installations. -
- Adjusted installer to now work when forced to use a proxy with the - netinst CD. -
- Fixed code detecting and setting/loading hardware specific - setup/firmware to work more robust out of the box. -
- Adjusted Kerberos setup to detect realm and server settings at - install time instead of dynamically at run time. This avoid a crash - with krb5-auth-dialog on diskless workstations without a DNS name. -
- Worked around misfeature in network-manager not calling the dhclient - exit hooks, causing automatic proxy configuration and automatic host - name setting at run time to work again. -
- Fixed feature setting the default Iceweasel start page from URL - fetched from LDAP, to allow schools to set the global default by - updating the dc=skole,dc=skolelinux,dc=no LDAP object. -
- Changed default host name on all networked machines to be unique - (generated from MAC or reverse DNS) after boot. -
- Adjusted partition sizes to make sure they are big enough. +
- xMail: +E-mail as XML en artikkel fra 2003 som beskriver python-modulen +rfc822 som gir ut XML-representasjon av en RFC 822-formattert epost.
Known issues
+Finnes det andre og bedre spesifikasjoner for slik lagring? Send +meg en epost hvis du har innspill.
+Her er noen lenker til tekster jeg har satt pris på å lese de siste +månedene. Det er mye om varsleren Edward Snowden, som burde få all +hjelp, støtte og beskyttelse Norge kan stille opp med for å ha satt +totalitær overvåkning på sakskartet, men også endel annet +tankevekkende og interessant.
-
-
- Grub is missing the new artwork. -
- KDE fail to understand the wpad.dat file provided, causing it to - not use the http proxy as it should. -
- Chromium also fail to use the proxy. - -
Where to get it
- -To download the multiarch netinstall CD release you can use
+-
+
- 2013-12-19 - +Staten har ikke rett til å vite alt om deg - DN.no -
- ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b0-CD.iso +
- 2013-12-21 +Nye +mål for NSAs spionasje avslørt - Dagbladet.no -
- http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b0-CD.iso +
- 2013-12-19 +«NSA +bør fjernes fra sin makt til å samle inn metadata fra amerikanske +telefonsamtaler» - Dagbladet.no -
- rsync -avzP ftp.skolelinux.org::skolelinux-cd/wheezy/debian-edu-7.1+edu0~b0-CD.iso . +
- 2013-12-18 +Etterretning, +overvåking, frihet og sikkerhet - Dagbladet.no -
The MD5SUM of this image is: 55d5de9765b6dccd5d9ec33cf1a07109
-
The SHA1SUM of this image is: 996a1d9517740e4d627d100de2d12b23dd545a3f
To download the multiarch USB stick ISO release you can use
+-
+
- 2013-12-20 +Matematikk +og forståelse - aftenposten.no -
- ftp://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b0-USB.iso -
- http://ftp.skolelinux.org/skolelinux-cd/wheezy/debian-edu-7.1+edu0~b0-USB.iso -
- rsync -avzP ftp.skolelinux.org::skolelinux-cd/wheezy/debian-edu-7.1+edu0~b0-USB.iso . +
- 2013-10-20 +Vi +søv for å reinse hjernen vår, ifølgje ny studie - nrk.no -
The MD5SUM of this image is: d8f0818c51a78d357de794066f289f69
-
The SHA1SUM of this image is: 49185ca354e8d0543240423746924f76a6cee733
How to report bugs
+Today I switched to -my -new laptop. I've previously written about the problems I had with -my new Thinkpad X230, which was delivered with an -180 -GB Intel SSD disk with Lenovo firmware that did not handle -sustained writes. My hardware supplier have been very forthcoming in -trying to find a solution, and after first trying with another -identical 180 GB disks they decided to send me a 256 GB Samsung SSD -disk instead to fix it once and for all. The Samsung disk survived -the installation of Debian with encrypted disks (filling the disk with -random data during installation killed the first two), and I thus -decided to trust it with my data. I have installed it as a Debian Edu -Wheezy roaming workstation hooked up with my Debian Edu Squeeze main -server at home using Kerberos and LDAP, and will use it as my work -station from now on.
- -As this is a solid state disk with no moving parts, I believe the -Debian Wheezy default installation need to be tuned a bit to increase -performance and increase life time of the disk. The Linux kernel and -user space applications do not yet adjust automatically to such -environment. To make it easier for my self, I created a draft Debian -package ssd-setup to handle this tuning. The -source -for the ssd-setup package is available from collab-maint, and it -is set up to adjust the setup of the machine by just installing the -package. If there is any non-SSD disk in the machine, the package -will refuse to install, as I did not try to write any logic to sort -file systems in SSD and non-SSD file systems.
- -I consider the package a draft, as I am a bit unsure how to best -set up Debian Wheezy with an SSD. It is adjusted to my use case, -where I set up the machine with one large encrypted partition (in -addition to /boot), put LVM on top of this and set up partitions on -top of this again. See the README file in the package source for the -references I used to pick the settings. At the moment these -parameters are tuned:
- --
+
- 2013-10-23 Professor Jan Arild Audestad +Advarer +mot konspirasjonsteori i digi.no og sier han ikke tror NSA kan +avlytte mobiltelefoner, mens han noen måneder senere forteller: -
- Set up cryptsetup to pass TRIM commands to the physical disk - (adding discard to /etc/crypttab) +
- 2014-01-09 +- +Vi ble presset til å svekke mobilsikkerheten på 80-tallet - +aftenposten.no -
- Set up LVM to pass on TRIM commands to the underlying device (in - this case a cryptsetup partition) by changing issue_discards from - 0 to 1 in /etc/lvm/lvm.conf. +
- 2014-02-12 +Et +møte med Edward Snowden - intervju sendt av nrk, tilgjengelig til +2015-01-31 -
- Set relatime as a file system option for ext3 and ext4 file - systems. +
- 2014-02-17 +Litteraturredaktøren: +Helle Thornings tavshed om Snowden er en skandale - +politiken.dk -
- Tell swap to use TRIM commands by adding 'discard' to - /etc/fstab. +
- 2014-02-21 +Bra å ha en «Storebror» - aftenposten.no -
- Change I/O scheduler from cfq to deadline using a udev rule. +
- 2014-02-28 +"Narkotikasiktet +Stortingsmann" - Spillet bak kulissene - John Christian Eldens +blogg -
- Run fstrim on every ext3 and ext4 file system every night (from - cron.daily). - -
- Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure - to 50 to reduce the kernel eagerness to swap out processes. +
- 2014-02-28 +Heksejakt +på hasjbrukere - aftenposten.no
During installation, I cancelled the part where the installer fill -the disk with random data, as this would kill the SSD performance for -little gain. My goal with the encrypted file system is to ensure -those stealing my laptop end up with a brick and not a working -computer. I have no hope in keeping the really resourceful people -from getting the data on the disk (see -XKCD #538 for an explanation why). -Thus I concluded that adding the discard option to crypttab is the -right thing to do.
- -I considered using the noop I/O scheduler, as several recommended -it for SSD, but others recommended deadline and a benchmark I found -indicated that deadline might be better for interactive use.
- -I also considered using the 'discard' file system option for ext3 -and ext4, but read that it would give a performance hit ever time a -file is removed, and thought it best to that that slowdown once a day -instead of during my work.
- -My package do not set up tmpfs on /var/run, /var/lock and /tmp, as -this is already done by Debian Edu.
- -I have not yet started on the user space tuning. I expect -iceweasel need some tuning, and perhaps other applications too, but -have not yet had time to investigate those parts.
- -The package should work on Ubuntu too, but I have not yet tested it -there.
- -As for the answer to the question in the title of this blog post, -as far as I know, the only solution I know about is to replace the -disk. It might be possible to flash it with Intel firmware instead of -the Lenovo firmware. But I have not tried and did not want to do so -without approval from Lenovo as I wanted to keep the warranty on the -disk until a solution was found and they wanted the broken disks -back.
A few days ago, I wrote about -the -problems I experienced with my new X230 and its SSD disk, which -was dying during installation because it is unable to cope with -sustained write. My supplier is in contact with -Lenovo, and they wanted to send a -replacement disk to try to fix the problem. They decided to send an -identical model, so my hopes for a permanent fix was slim.
- -Anyway, today I got the replacement disk and tried to install -Debian Edu Wheezy with encrypted disk on it. The new disk have the -same firmware version as the original. This time my hope raised -slightly as the installation progressed, as the original disk used to -die after 4-7% of the disk was written to, while this time it kept -going past 10%, 20%, 40% and even past 50%. But around 60%, the disk -died again and I was back on square one. I still do not have a new -laptop with a disk I can trust. I can not live with a disk that might -lock up when I download a new -Debian Edu / Skolelinux ISO or -other large files. I look forward to hearing from my supplier with -the next proposal from Lenovo.
- -The original disk is marked Intel SSD 520 Series 180 GB, -11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW: -LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722, -Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model: -SSDSC2BW180A3L 2.5" 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU -P/N 45N8295, P0C38732.
- -The replacement disk is marked Intel SSD 520 Series 180 GB, -11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW: -LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722, -Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model: -SSDSC2BW180A3L 2.5" 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU -P/N 45N8295, P0C38732.
- -The only difference is in the first number (serial number?), ISN, -SA, date and WNPP values. Mentioning all the details here in case -someone is able to use the information to find a way to identify the -failing disk among working ones (if any such working disk actually -exist).
+ +Many years ago, I wrote a GPL licensed version of the netgroup and +innetgr tools, because I needed them in +Skolelinux. I called the project +ng-utils, and it has served me well. I placed the project under the +Hungry Programmer umbrella, and it was maintained in our CVS +repository. But many years ago, the CVS repository was dropped (lost, +not migrated to new hardware, not sure), and the project have lacked a +proper home since then.
+ +Last summer, I had a look at the package and made a new release +fixing a irritating crash bug, but was unable to store the changes in +a proper source control system. I applied for a project on +Alioth, but did not have time +to follow up on it. Until today. :)
+ +After many hours of cleaning and migration, the ng-utils project +now have a new home, and a git repository with the highlight of the +history of the project. I published all release tarballs and imported +them into the git repository. As the project is really stable and not +expected to gain new features any time soon, I decided to make a new +release and call it 1.0. Visit the new project home on +https://alioth.debian.org/projects/ng-utils/ +if you want to check it out. The new version is also uploaded into +Debian Unstable.