Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index cb30bc1c44472912ea9b40ec17e73c7e62b5cac0..af1b2cfe87aff6cf3f4e6fdd24085a66a4763eea 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,55 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
                 <link>http://people.skolelinux.org/pere/blog/</link>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        

+       <item>
+               <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>&lt;p&gt;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 favorite 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.&lt;/p&gt;
+
+&lt;p&gt;Normally I rip the DVDs using dd like this:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+#!/bin/sh
+# apt-get install lsdvd
+title=$(lsdvd 2&gt;/dev/null|awk &#39;/Disc Title: / {print $3}&#39;)
+dd if=/dev/dvd of=/storage/dvds/$title.iso bs=1M
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;Anway, 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 repacking it
+back as an ISO.
+
+&lt;blockquote&gt;&lt;pre&gt;
+#!/bin/sh
+# apt-get install lsdvd dvdbackup genisoimage
+set -e
+tmpdir=/storage/dvds/
+title=$(lsdvd 2&gt;/dev/null|awk &#39;/Disc Title: / {print $3}&#39;)
+dvdbackup -i /dev/dvd -M -o $tmpdir -n$title
+genisoimage -dvd-video -o $tmpdir/$title.iso $tmpdir/$title
+rm -rf $tmpdir/$title
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;Anyone know of a better way available in Debian/Squeeze?&lt;/p&gt;
+
+</description>
+       </item>
+       

        <item>
                <title>Kommunevalget må visst kontrollregnes på</title>
                <link>http://people.skolelinux.org/pere/blog/Kommunevalget_m__visst_kontrollregnes_p_.html</link>
        <item>
                <title>Kommunevalget må visst kontrollregnes på</title>
                <link>http://people.skolelinux.org/pere/blog/Kommunevalget_m__visst_kontrollregnes_p_.html</link>


@@ -368,56 +417,5 @@ og bør aldri glemmes.&lt;/p&gt;
 </description>
        </item>
        
 </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>&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-</description>
-       </item>
-       

         </channel>
 </rss>
         </channel>
 </rss>