<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
<item>
-<<<<<<< index.rss
+ <title>Ripping problematic DVDs using dvdbackup and genisoimage</title>
+ <link>http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html</guid>
+ <pubDate>Sat, 17 Sep 2011 20:20:00 +0200</pubDate>
+ <description><p>For convenience, I want to store copies of all my DVDs on my file
+server. It allow me to save shelf space flat while still having my
+movie collection easily available. It also make it possible to let
+the kids see their favourite DVDs without wearing the physical copies
+down. I prefer to store the DVDs as ISOs to keep the DVD menu and
+subtitle options intact. It also ensure that the entire film is one
+file on the disk. As this is for personal use, the ripping is
+perfectly legal here in Norway.</p>
+
+<p>Normally I rip the DVDs using dd like this:</p>
+
+<blockquote><pre>
+#!/bin/sh
+# apt-get install lsdvd
+title=$(lsdvd 2>/dev/null|awk '/Disc Title: / {print $3}')
+dd if=/dev/dvd of=/storage/dvds/$title.iso bs=1M
+</pre></blockquote>
+
+<p>But some DVDs give a input/output error when I read it, and I have
+been looking for a better alternative. I have no idea why this I/O
+error occur, but suspect my DVD drive, the Linux kernel driver or
+something fishy with the DVDs in question. Or perhaps all three.</p>
+
+<p>Anyway, I believe I found a solution today using dvdbackup and
+genisoimage. This script gave me a working ISO for a problematic
+movie by first extracting the DVD file system and then re-packing it
+back as an ISO.
+
+<blockquote><pre>
+#!/bin/sh
+# apt-get install lsdvd dvdbackup genisoimage
+set -e
+tmpdir=/storage/dvds/
+title=$(lsdvd 2>/dev/null|awk '/Disc Title: / {print $3}')
+dvdbackup -i /dev/dvd -M -o $tmpdir -n$title
+genisoimage -dvd-video -o $tmpdir/$title.iso $tmpdir/$title
+rm -rf $tmpdir/$title
+</pre></blockquote>
+
+<p>Anyone know of a better way available in Debian/Squeeze?</p>
+
+<p>Update 2011-09-18: I got a tip from Konstantin Khomoutov about the
+readom program from the wodim package. It is specially written to
+read optical media, and is called like this: <tt>readom dev=/dev/dvd
+f=image.iso</tt>. It got 6 GB along with the problematic Cars DVD
+before it failed, and failed right away with a Timmy Time DVD.</p>
+
+<p>Next, I got a tip from Bastian Blank about
+<a href="http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">his
+program python-dvdvideo</a>, which seem to be just what I am looking
+for. Tested it with my problematic Timmy Time DVD, and it succeeded
+creating a ISO image. The git source built and installed just fine in
+Squeeze, so I guess this will be my tool of choice in the future.</p>
+</description>
+ </item>
+
+ <item>
<title>Kommunevalget må visst kontrollregnes på</title>
<link>http://people.skolelinux.org/pere/blog/Kommunevalget_m__visst_kontrollregnes_p_.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kommunevalget_m__visst_kontrollregnes_p_.html</guid>
opptellingen. Det kan på den måten være mulig å finne ut hva en
person stemte. Hvis personen tar med seg en stemmeseddel fra alle
partiene vil det fortsatt være mulig å finne ut hvilken av disse som
-ble talt opp, slik at en ikke kan beskytte seg på det viset./p>
+ble talt opp, slik at en ikke kan beskytte seg på det viset.</p>
<p>Jeg er ikke sikker på hvor realistiske disse scenariene er i dag,
dvs. hvilke andre prosedyrer som finnes i det norske valget for å
</item>
<item>
-=======
- <title>Noen problemer rundt unikt nummererte stemmesedler i norske valg</title>
- <link>http://people.skolelinux.org/pere/blog/Noen_problemer_rundt_unikt_nummererte_stemmesedler_i_norske_valg.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Noen_problemer_rundt_unikt_nummererte_stemmesedler_i_norske_valg.html</guid>
- <pubDate>Tue, 13 Sep 2011 16:00:00 +0200</pubDate>
- <description><p>I digi.no forklarer Ergo Group at gårdagens problemer med
-opptelling av stemmesedler ved kommunevalget var at
-<a href="http://www.digi.no/877938/ikke-programmeringsshy%3Bfeil-i-valgshy%3Bsystemet">noen
-stemmesedler ikke hadde unike løpenummer</a>, og at programvaren som
-ble brukt til telling ikke var laget for å håndtere dette. Jeg ble
-svært overrasket over å lese at norske stemmesedler har unike
-løpenummer, da min forståelse er at det går på bekostning av kravet om
-hemmelige valg.</p>
-
-<p>Jeg har ikke god oversikt over hvilke problemer dette kan skape for
-hemmelig valg, men her er noen scenarier som virker problematiske for
-meg:</p>
-
-<p>(1) Jomar og Bertil avtaler at Bertil skal stemme på Lurepartiet
-med stemmeseddelen som Bertil får utlevert fra Jomar, og belønnes for
-dette. Stemmeseddelen har et unikt løpenummer, og ved opptellingen
-sjekker Jomar at stemmeseddelen til Lurepartiet det unike løpenummeret
-er med i stemmesedlene som ble talt opp før Bertil får sin belønning.
-Unike løpenummer legger så vidt jeg kan forstå opp til kjøp og salg av
-stemmer.</p>
-
-<p>(2) Jomar har også jobb som valgobservatør, og har gått igjennom
-avlukkene og notert parti og løpenummer for alle stemmesedlene i
-avlukkene. Har er i tillegg jevnlig innom og sjekker hvilke
-løpenummer som er igjen i avlukkene (lar seg ganske raskt og enkelt
-gjøre med en mobiltelefon med kamera som kan ta bilder av alle
-løpenumrene). Når en person han vil vite hva stemmer kommer innom,
-sammenligner han stemmesedler i avlukkene før og etter at vedkommende
-har vært innom, og sjekker så om løpenummeret som var på stemmeseddel
-(eller sedlene) som forsvant fra avlukket dukker opp under
-opptellingen. Det kan på den måten være mulig å finne ut hva en
-person stemte. Hvis personen tar med seg en stemmeseddel fra alle
-partiene vil det fortsatt være mulig å finne ut hvilken av disse som
-ble talt opp, slik at en ikke kan beskytte seg på det viset./p>
-
-<p>Jeg er ikke sikker på hvor realistiske disse scenariene er i dag,
-dvs. hvilke andre prosedyrer som finnes i det norske valget for å
-hindre dette.</p>
-
-<p>Det er dog ingen tvil om at det er lurt å nummerere stemmesedler
-ved opptelling for å sikre at ingen forsvinner i prosessen med å telle
-opp stemmer, men det må gjøres når stemmeurnene åpnes og ikke før
-innbyggerne avgir sin stemme.</p>
-
-<p>Under Go Open 2009 presenterte Mitch Trachtenberg fra Humboldt
-County, California hvordan
-<a href="http://goopen2009.friprog.no/program/48-freevalg">de laget et
-system som kontrolltalte stemmene</a> der ved hjelp av en scanner med
-arkmater og fri programvare. Der ble stemmesedlene unikt nummerert
-før scanning, og det er laget en CD med bilder av alle stemmesedler
-slik at enhver kan kontrolltelle stemmene selv hvis de ønsker det.
-Kanskje en ide også for Norge? Programvaren er så vidt jeg vet fri
-programvare, og tilgjengelig fra
-<a href="http://www.tevsystems.com/">hans nettsted</a></p>
-</description>
- </item>
-
- <item>
->>>>>>> 1.377
<title>Mer løgnpropaganda fra BSA</title>
<link>http://people.skolelinux.org/pere/blog/Mer_l_gnpropaganda_fra_BSA.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mer_l_gnpropaganda_fra_BSA.html</guid>
</description>
</item>
- <item>
- <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
- <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
- <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
- <description><p>In the Debian boot system, several packages include scripts that
-are started from /etc/rcS.d/. In fact, there is a bite more of them
-than make sense, and this causes a few problems. What kind of
-problems, you might ask. There are at least two problems. The first
-is that it is not possible to recover a machine after switching to
-runlevel 1. One need to actually reboot to get the machine back to
-the expected state. The other is that single user boot will sometimes
-run into problems because some of the subsystems are activated before
-the root login is presented, causing problems when trying to recover a
-machine from a problem in that subsystem. A minor additional point is
-that moving more scripts out of rcS.d/ and into the other rc#.d/
-directories will increase the amount of scripts that can run in
-parallel during boot, and thus decrease the boot time.</p>
-
-<p>So, which scripts should start from rcS.d/. In short, only the
-scripts that _have_ to execute before the root login prompt is
-presented during a single user boot should go there. Everything else
-should go into the numeric runlevels. This means things like
-lm-sensors, fuse and x11-common should not run from rcS.d, but from
-the numeric runlevels. Today in Debian, there are around 115 init.d
-scripts that are started from rcS.d/, and most of them should be moved
-out. Do your package have one of them? Please help us make single
-user and runlevel 1 better by moving it.</p>
-
-<p>Scripts setting up the screen, keyboard, system partitions
-etc. should still be started from rcS.d/, but there is for example no
-need to have the network enabled before the single user login prompt
-is presented.</p>
-
-<p>As always, things are not so easy to fix as they sound. To keep
-Debian systems working while scripts migrate and during upgrades, the
-scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
-order, ie the scripts that nothing in rcS.d/ depend on can be moved,
-and the next ones can only be moved when their dependencies have been
-moved first. This migration must be done sequentially while we ensure
-that the package system upgrade packages in the right order to keep
-the system state correct. This will require some coordination when it
-comes to network related packages, but most of the packages with
-scripts that should migrate do not have anything in rcS.d/ depending
-on them. Some packages have already been updated, like the sudo
-package, while others are still left to do. I wish I had time to work
-on this myself, but real live constrains make it unlikely that I will
-find time to push this forward.</p>
-</description>
- </item>
-
-<<<<<<< index.rss
-=======
- <item>
- <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
- <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
- <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
- <description><p>While at Debconf11, I have several times during discussions
-mentioned the issues I believe should be improved in Debian for its
-desktop to be useful for more people. The use case for this is my
-parents, which are currently running Kubuntu which solve the
-issues.</p>
-
-<p>I suspect these four missing features are not very hard to
-implement. After all, they are present in Ubuntu, so if we wanted to
-do this in Debian we would have a source.</p>
-
-<ol>
-
-<li><strong>Simple GUI based upgrade of packages.</strong> When there
-are new packages available for upgrades, a icon in the KDE status bar
-indicate this, and clicking on it will activate the simple upgrade
-tool to handle it. I have no problem guiding both of my parents
-through the process over the phone. If a kernel reboot is required,
-this too is indicated by the status bars and the upgrade tool. Last
-time I checked, nothing with the same features was working in KDE in
-Debian.</li>
-
-<li><strong>Simple handling of missing Firefox browser
-plugins.</strong> When the browser encounter a MIME type it do not
-currently have a handler for, it will ask the user if the system
-should search for a package that would add support for this MIME type,
-and if the user say yes, the APT sources will be searched for packages
-advertising the MIME type in their control file (visible in the
-Packages file in the APT archive). If one or more packages are found,
-it is a simple click of the mouse to add support for the missing mime
-type. If the package require the user to accept some non-free
-license, this is explained to the user. The entire process make it
-more clear to the user why something do not work in the browser, and
-make the chances higher for the user to blame the web page authors and
-not the browser for any missing features.</li>
-
-<li><strong>Simple handling of missing multimedia codec/format
-handlers.</strong> When the media players encounter a format or codec
-it is not supporting, a dialog pop up asking the user if the system
-should search for a package that would add support for it. This
-happen with things like MP3, Windows Media or H.264. The selection
-and installation procedure is very similar to the Firefox browser
-plugin handling. This is as far as I know implemented using a
-gstreamer hook. The end result is that the user easily get access to
-the codecs that are present from the APT archives available, while
-explaining more on why a given format is unsupported by Ubuntu.</li>
-
-<li><strong>Better browser handling of some MIME types.</strong> When
-displaying a text/plain file in my Debian browser, it will propose to
-start emacs to show it. If I remember correctly, when doing the same
-in Kunbutu it show the file as a text file in the browser. At least I
-know Opera will show text files within the browser. I much prefer the
-latter behaviour.</li>
-
-</ol>
-
-<p>There are other nice features as well, like the simplified suite
-upgrader, but given that I am the one mostly doing the dist-upgrade,
-it do not matter much.</p>
-
-<p>I really hope we could get these features in place for the next
-Debian release. It would require the coordinated effort of several
-maintainers, but would make the end user experience a lot better.</p>
-</description>
- </item>
-
->>>>>>> 1.377
</channel>
</rss>
projects / homepage.git / blobdiff