blag: typos, indentation fixes (libmultimarkdown-perl is a bit more picky with code...

diff --git a/blag/post/af9015-bulk-message-failed-switch-usb-ports.mdwn b/blag/post/af9015-bulk-message-failed-switch-usb-ports.mdwn
index 489061f..1c6d73a 100644 (file)
--- a/blag/post/af9015-bulk-message-failed-switch-usb-ports.mdwn
+++ b/blag/post/af9015-bulk-message-failed-switch-usb-ports.mdwn
@@ -7,13 +7,13 @@ Yesterday, I suddenly wasn’t able to use my AF9015-based DVB-T USB stick
 anymore. It only worked for about a minute, then the image froze and
 `dmesg` said the following:
 
 anymore. It only worked for about a minute, then the image froze and
 `dmesg` said the following:
 

-       [10633.166371] usb 1-3: USB disconnect, address 5
-       [10633.186247] af9015: bulk message failed:-22 (8/-339951920)
-       [10633.186254] af9013: I2C read failed reg:d417
-       [10633.186258] af9015: bulk message failed:-22 (8/-1067461161)
-       [10633.186265] af9013: I2C read failed reg:d417
-       [10633.186279] af9015: bulk message failed:-22 (9/-339951284)
-       [10633.186282] mt2060 I2C write failed
+    [10633.166371] usb 1-3: USB disconnect, address 5
+    [10633.186247] af9015: bulk message failed:-22 (8/-339951920)
+    [10633.186254] af9013: I2C read failed reg:d417
+    [10633.186258] af9015: bulk message failed:-22 (8/-1067461161)
+    [10633.186265] af9013: I2C read failed reg:d417
+    [10633.186279] af9015: bulk message failed:-22 (9/-339951284)
+    [10633.186282] mt2060 I2C write failed

 
 I was not even able to `rmmod` the dvb-usb-af9015 kernel module, the
 rmmod process just hung itself up.
 
 I was not even able to `rmmod` the dvb-usb-af9015 kernel module, the
 rmmod process just hung itself up.

diff --git a/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu.mdwn b/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu.mdwn
index 0157fef..0720177 100644 (file)
--- a/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu.mdwn
+++ b/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu.mdwn
@@ -16,71 +16,71 @@ connectivity.  Windows Mobile 6.1 allows tethering over a Bluetooth PAN
 step-by-step tutorial what I did for my PAN approach, with a few
 (german) screenshots, tested on Ubuntu 10.04 Lucid:
 
 step-by-step tutorial what I did for my PAN approach, with a few
 (german) screenshots, tested on Ubuntu 10.04 Lucid:
 

-* Since my laptop was running on Ubuntu Lucid, there was already a
-  recent Blueman version in the Ubuntu repos available. On older
-  systems, you may want to add the [Blueman Launchpad PPA][5].
-
-      $ sudo apt-add-repository ppa:blueman/ppa  # only necessary on pre-lucid systems
-      $ sudo aptitude update
-      $ sudo aptitude install blueman
-
-* Note that this also removes possibly installed `gnome-bluetooth`
-  packages since Blueman is an adequate replacement for the GNOME
-  Bluetooth UI.
-
-* After the installation has finished, I had to enable the NMPANSupport
-  plugin for NetworkManager 0.8 by right-clicking on the Blueman icon in
-  the GNOME notification area and selecting “Plugins”. For older
-  NetworkManager versions, there is also a plugin for NetworkManager
-  0.7, called NMIntegration.
-
-  <div class="gallery">
-  [[!img blueman-menu.png alt="Blueman context menu"]]
-  [[!img blueman-plugins.png alt="Blueman plugin page"]]
-  </div>
-
-* Then I activated tethering on my phone (“Programs” → “Internet
-  Sharing” on my Windows Mobile 6.1, but YMMV). Apparently this was
-  neccesary with my model, because without tethering enabled I could not
-  get a Bluetooth PAN connection in the next step.
-
-  <div class="gallery">
-  [[!img winmo-program-menu.png alt="Windows Mobile Program screen"]]
-  [[!img winmo-connection-sharing.png alt="Windows Mobile Internet
+*   Since my laptop was running on Ubuntu Lucid, there was already a
+    recent Blueman version in the Ubuntu repos available. On older
+    systems, you may want to add the [Blueman Launchpad PPA][5].
+
+        $ sudo apt-add-repository ppa:blueman/ppa  # only necessary on pre-lucid systems
+        $ sudo aptitude update
+        $ sudo aptitude install blueman
+
+*   Note that this also removes possibly installed `gnome-bluetooth`
+    packages since Blueman is an adequate replacement for the GNOME
+    Bluetooth UI.
+
+*   After the installation has finished, I had to enable the NMPANSupport
+    plugin for NetworkManager 0.8 by right-clicking on the Blueman icon in
+    the GNOME notification area and selecting “Plugins”. For older
+    NetworkManager versions, there is also a plugin for NetworkManager
+    0.7, called NMIntegration.
+
+    <div class="gallery">
+    [[!img blueman-menu.png alt="Blueman context menu"]]
+    [[!img blueman-plugins.png alt="Blueman plugin page"]]
+    </div>
+
+*   Then I activated tethering on my phone (“Programs” → “Internet
+    Sharing” on my Windows Mobile 6.1, but YMMV). Apparently this was
+    neccesary with my model, because without tethering enabled I could not
+    get a Bluetooth PAN connection in the next step.
+
+    <div class="gallery">
+    [[!img winmo-program-menu.png alt="Windows Mobile Program screen"]]
+    [[!img winmo-connection-sharing.png alt="Windows Mobile Internet

          Sharing application"]]
          Sharing application"]]

-  </div >
-
-* I paired the phone and my laptop via Bluetooth, and created a PAN
-  (Personal Area Network) by connecting to the “Network Access Point”
-  service on the phone. In Blueman, all you have to do after pairing is
-  right-click on the device and select “Connect To: Network Access
-  Point”. This creates a new network device `bnep0` which is
-  automagically configured through NetworkManager (using [stateless
-  address autoconfiguration][6]).
-
-  <div class="gallery">
-  [[!img blueman-pan.png size=x100 alt="Blueman: Context menu for device
+    </div >
+
+*   I paired the phone and my laptop via Bluetooth, and created a PAN
+    (Personal Area Network) by connecting to the “Network Access Point”
+    service on the phone. In Blueman, all you have to do after pairing is
+    right-click on the device and select “Connect To: Network Access
+    Point”. This creates a new network device `bnep0` which is
+    automagically configured through NetworkManager (using [stateless
+    address autoconfiguration][6]).
+
+    <div class="gallery">
+    [[!img blueman-pan.png size=x100 alt="Blueman: Context menu for device

       “Leia”, menu entry “Network Access Point” is selected"]]
       “Leia”, menu entry “Network Access Point” is selected"]]

-  </div>
+    </div>

 
 

-  (Yes, my phone is called [Leia][7]… I also have a yet another HTC
-  Prophet for testing purposes, which is called [Luke][8] :-))
+    (Yes, my phone is called [Leia][7]… I also have a yet another HTC
+    Prophet for testing purposes, which is called [Luke][8] :-) )

 
 

-* However, in my setup, though I was able to ping certain IP adresses on
-  the internet, DNS lookups timed out for some reason. It got better
-  when I explicitly set an IP address for the Bluetooth PAN driver on my
-  phone, and did the tethering process all over again.
+*   However, in my setup, though I was able to ping certain IP adresses on
+    the internet, DNS lookups timed out for some reason. It got better
+    when I explicitly set an IP address for the Bluetooth PAN driver on my
+    phone, and did the tethering process all over again.

 
 

-  <div class="gallery">
-  [[!img winmo-connections.png alt="Windows Mobile System Settings
+    <div class="gallery">
+    [[!img winmo-connections.png alt="Windows Mobile System Settings

       Screen, with item “Wi-Fi” selected"]]
       Screen, with item “Wi-Fi” selected"]]

-  [[!img winmo-networkdrivers.png alt="Windows Mobile Network Driver
+    [[!img winmo-networkdrivers.png alt="Windows Mobile Network Driver

       settings screen, with menu item “Bluetooth PAN Driver” selected"]]
       settings screen, with menu item “Bluetooth PAN Driver” selected"]]

-  [[!img winmo-bluetooth-ip.png alt="Windows Mobile Bluetooth PAN Driver
+    [[!img winmo-bluetooth-ip.png alt="Windows Mobile Bluetooth PAN Driver

       settings screen"]]
       settings screen"]]

-  </div>
+    </div>

 
 

-* And off I went with mobile internet access. Woo-hoo! \o/
+*   And off I went with mobile internet access. Woo-hoo! \o/

 
 I may also add that the NetUsage plugin in Blueman is very reasonable to
 use ;-) After activated, the network usage can be viewed by
 
 I may also add that the NetUsage plugin in Blueman is very reasonable to
 use ;-) After activated, the network usage can be viewed by


@@ -97,4 +97,4 @@ right-clicking on the Blueman icon and selecting “Network Usage”.
 [8]: http://en.wikipedia.org/wiki/Luke_Skywalker
 
 [[!tag Blueman bluetooth mobile_internet_access network NetworkManager
 [8]: http://en.wikipedia.org/wiki/Luke_Skywalker
 
 [[!tag Blueman bluetooth mobile_internet_access network NetworkManager

-       Ubuntu Ubuntu_Lucid Windows_Mobile]]
+    Ubuntu Ubuntu_Lucid Windows_Mobile]]

diff --git a/blag/post/ssh-key-authentication-with-encrypted-home-directories.mdwn b/blag/post/ssh-key-authentication-with-encrypted-home-directories.mdwn
index 1b4a2da..9841994 100644 (file)
--- a/blag/post/ssh-key-authentication-with-encrypted-home-directories.mdwn
+++ b/blag/post/ssh-key-authentication-with-encrypted-home-directories.mdwn
@@ -57,19 +57,19 @@ appropriately:
 There is yet a better approach instead, which doesn’t need the SSHd
 config to be edited at all:
 
 There is yet a better approach instead, which doesn’t need the SSHd
 config to be edited at all:
 

-1. login to the user on the remote machine
-2. create `/home/.ecryptfs/$USER/.ssh` and put your `authorized_hosts` there
-3. symlink your encrypted version there:
+1.  login to the user on the remote machine
+2.  create `/home/.ecryptfs/$USER/.ssh` and put your `authorized_hosts` there
+3.  symlink your encrypted version there:

 
 

-       $ ln -s /home/.ecryptfs/$USER/.ssh/authorized_hosts ~/.ssh/authorized_hosts
+        $ ln -s /home/.ecryptfs/$USER/.ssh/authorized_hosts ~/.ssh/authorized_hosts

 
 

-4. symlink your unencrypted version there (as above, **make sure** no
-   process wants to write to your home directory in the meantime):
+4.  symlink your unencrypted version there (as above, **make sure** no
+    process wants to write to your home directory in the meantime):

 
 

-       $ ecryptf-umount-private
-       $ mkdir ~/.ssh
-       $ ln -s /home/.ecryptfs/$USER/.ssh/authorized_hosts ~/.ssh/authorized_hosts
-       $ ecryptfs-mount-private
+        $ ecryptf-umount-private
+        $ mkdir ~/.ssh
+        $ ln -s /home/.ecryptfs/$USER/.ssh/authorized_hosts ~/.ssh/authorized_hosts
+        $ ecryptfs-mount-private

 
 The paths are for Ubuntu 9.10 (Karmic Koala) and later. On other
 systems, you might want to replace `/home/.ecryptfs` with
 
 The paths are for Ubuntu 9.10 (Karmic Koala) and later. On other
 systems, you might want to replace `/home/.ecryptfs` with

diff --git a/blag/post/sync-your-windows-mobile-5-6-pda-with-your-linux-pc.mdwn b/blag/post/sync-your-windows-mobile-5-6-pda-with-your-linux-pc.mdwn
index 1f4d972..b5fbd2a 100644 (file)
--- a/blag/post/sync-your-windows-mobile-5-6-pda-with-your-linux-pc.mdwn
+++ b/blag/post/sync-your-windows-mobile-5-6-pda-with-your-linux-pc.mdwn
@@ -16,4 +16,4 @@ like a charm :-)
 [1]: http://wiki.ubuntuusers.de/Archiv/Synchronisation_mit_Windows_Mobile
 
 [[!tag howto Ubuntu blacklist Evolution iPAQ kernel_module Linux PDA
 [1]: http://wiki.ubuntuusers.de/Archiv/Synchronisation_mit_Windows_Mobile
 
 [[!tag howto Ubuntu blacklist Evolution iPAQ kernel_module Linux PDA

-       synchronisation Ubuntu Windows_Mobile]]
+    synchronisation Ubuntu Windows_Mobile]]

diff --git a/blag/post/ubuntu-karmic-upgrade-issues.mdwn b/blag/post/ubuntu-karmic-upgrade-issues.mdwn
index 49b37bd..41a5d66 100644 (file)
--- a/blag/post/ubuntu-karmic-upgrade-issues.mdwn
+++ b/blag/post/ubuntu-karmic-upgrade-issues.mdwn
@@ -13,46 +13,46 @@ but as in every upgrade I ever made (and I probably should know by now
 -.-), there are a few things that were annoying me or are still doing
 it:
 
 -.-), there are a few things that were annoying me or are still doing
 it:
 

-* kaffeine-1.0~pre is not even as useful as 0.8.7 from jaunty: While
-  staying in touch with the main KDE (4) line, the developers seemed to
-  completely remove the Playback -> Video menu, so it is not possible
-  anymore to toggle deinterlacing, or any other video filter, which is
-  very annoying for DVB-T.  I filed a [bug report][1] on that.
-  Futhermore, my DVB-T channels were lost, so I had to rescan them.
-
-* The notifications displayed by notify-osd somehow have wandered from
-  the upper right edge towards the middle right. This seems to be fixed
-  now, as pointed out in the [bug report][2], but somehow this fix never
-  got onto my system, though the changelog of notify-osd says so…
-  Additionally, the notifications for received messages in Pidgin do not
-  hide anymore if I actually read the messages, they persist until their
-  default timeout has elapsed. And they even show up now when my IM
-  status is on “Do not Disturb” – this was not the case (just as I
-  expected it) in jaunty.
-
-* Icons in GTK menus are now hidden by default, which seemed very
-  unfamiliar to me, since I always used them as an orientation guide,
-  especcially in the Firefox search plugin menu. You can show them again
-  in the System -> Preferences -> Appearance applet on the Interface tab
-  by selecting “Show icons in menus”.
-
-* GDM is no longer custumizable through themes. It just doesn’t support
-  it, as it seems to be a [complete rewrite][3]. IMHO just another
-  Unmature Software Thing.
+*   kaffeine-1.0~pre is not even as useful as 0.8.7 from jaunty: While
+    staying in touch with the main KDE (4) line, the developers seemed to
+    completely remove the Playback -> Video menu, so it is not possible
+    anymore to toggle deinterlacing, or any other video filter, which is
+    very annoying for DVB-T.  I filed a [bug report][1] on that.
+    Futhermore, my DVB-T channels were lost, so I had to rescan them.
+
+*   The notifications displayed by notify-osd somehow have wandered from
+    the upper right edge towards the middle right. This seems to be fixed
+    now, as pointed out in the [bug report][2], but somehow this fix never
+    got onto my system, though the changelog of notify-osd says so…
+    Additionally, the notifications for received messages in Pidgin do not
+    hide anymore if I actually read the messages, they persist until their
+    default timeout has elapsed. And they even show up now when my IM
+    status is on “Do not Disturb” – this was not the case (just as I
+    expected it) in jaunty.
+
+*   Icons in GTK menus are now hidden by default, which seemed very
+    unfamiliar to me, since I always used them as an orientation guide,
+    especcially in the Firefox search plugin menu. You can show them again
+    in the System -> Preferences -> Appearance applet on the Interface tab
+    by selecting “Show icons in menus”.
+
+*   GDM is no longer customizable through themes. It just doesn’t support
+    it, as it seems to be a [complete rewrite][3]. IMHO just another
+    Unmature Software Thing.

   
   

-  **Edit:** I just found out that it is also not able to start GDM in
-  Xnest, as I usually did for testing:
-
-      $ gdmflexiserver --xnest
-      ** (gdmflexiserver:5916): WARNING **: Not yet implemented
-
-* And finally, my customized GNOME window theme (based on Clearlooks)
-  was broken :-( I am very confident that the color of selected text was
-  not the same color in the title bar, but now both seem to be the same
-  color. This is really bad, as for the title bar, I used to have a
-  darker shade of orange than for selected text. OK, changing to another
-  theme may be simple, but until now, I haven’t found anything I like
-  best.
+    **Edit:** I just found out that it is also not able to start GDM in
+    Xnest, as I usually did for testing:
+
+        $ gdmflexiserver --xnest
+        ** (gdmflexiserver:5916): WARNING **: Not yet implemented
+
+*   And finally, my customized GNOME window theme (based on Clearlooks)
+    was broken :-( I am very confident that the color of selected text was
+    not the same color in the title bar, but now both seem to be the same
+    color. This is really bad, as for the title bar, I used to have a
+    darker shade of orange than for selected text. OK, changing to another
+    theme may be simple, but until now, I haven’t found anything I like
+    best.

 
 [1]: https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/499938
 [2]: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/419894
 
 [1]: https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/499938
 [2]: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/419894

diff --git a/blag/post/zsnes-on-amd64-ubuntu.mdwn b/blag/post/zsnes-on-amd64-ubuntu.mdwn
index 5df598c..6c96c52 100644 (file)
--- a/blag/post/zsnes-on-amd64-ubuntu.mdwn
+++ b/blag/post/zsnes-on-amd64-ubuntu.mdwn
@@ -45,40 +45,40 @@ there is no warranty here—but I’m happy to hear if it works :-)):
 ## How to Reproduce It
 For the curious people reading here, here is what I actually did:
 
 ## How to Reproduce It
 For the curious people reading here, here is what I actually did:
 

-1. `wget http://archive.ubuntu.com/ubuntu/pool/universe/z/zsnes/zsnes_1.510-2.2ubuntu3_i386.deb`
-2. `ar x zsnes_1.510-2.2ubuntu3_i386.deb`
-3. `tar xzf data.tar.gz`
-4. Edit `usr/share/applications/zsnes.desktop` and added `-ad sdl` to the
-   `Exec:` field, otherwise it would just segfault on the first run:
-      
-       Exec=zsnes -ad sdl
-
-5. Edit `usr/share/doc/zsnes/changelog.Debian.gz` and added a new
-   changelog entry for the version (just copy one of the previous
-   entries and adapt it)
-6. `tar xzf control.tar.gz`
-7. Edit the `control` file, changed the `Version:` and `Architecture:`
-   field to `amd64`, added the `ia32-libs` dependency, and set myself as
-   maintainer:
-
-       Package: zsnes
-       Version: 1.510-2.2ubuntu3~ppa1
-       Architecture: amd64
-       Maintainer: Roland Hieber <foobar@example.org>
-       Installed-Size: 4160
-       Depends: ia32-libs, libao2 (>= 0.8.8), libc6 (>= 2.4), libgcc1 (>= 1:4.1.1),
-         libgl1-mesa-glx | libgl1, libpng12-0 (>= 1.2.13-4),
-         libsdl1.2debian (>= 1.2.10-1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.2.2.3)
-       [...]
-
-8. Change the `md5sums` file for the right values for
-   `usr/share/applications/zsnes.desktop` and
-   `usr/share/doc/zsnes/changelog.Debian.gz` (I used the `md5sum`
-   command and copy-pasted it)
-9. `tar czf control.tar.gz control md5sums postrm postinst`
-0. `tar czf data.tar.gz usr/`
-1. `ar r zsnes_1.510-2.2ubuntu3~ppa1_amd64.deb debian-binary
-   control.tar.gz data.tar.gz`
+1.  `wget http://archive.ubuntu.com/ubuntu/pool/universe/z/zsnes/zsnes_1.510-2.2ubuntu3_i386.deb`
+2.  `ar x zsnes_1.510-2.2ubuntu3_i386.deb`
+3.  `tar xzf data.tar.gz`
+4.  Edit `usr/share/applications/zsnes.desktop` and added `-ad sdl` to the
+    `Exec:` field, otherwise it would just segfault on the first run:
+
+        Exec=zsnes -ad sdl
+
+5.  Edit `usr/share/doc/zsnes/changelog.Debian.gz` and added a new
+    changelog entry for the version (just copy one of the previous
+    entries and adapt it)
+6.  `tar xzf control.tar.gz`
+7.  Edit the `control` file, changed the `Version:` and `Architecture:`
+    field to `amd64`, added the `ia32-libs` dependency, and set myself as
+    maintainer:
+
+        Package: zsnes
+        Version: 1.510-2.2ubuntu3~ppa1
+        Architecture: amd64
+        Maintainer: Roland Hieber <foobar@example.org>
+        Installed-Size: 4160
+        Depends: ia32-libs, libao2 (>= 0.8.8), libc6 (>= 2.4), libgcc1 (>= 1:4.1.1),
+          libgl1-mesa-glx | libgl1, libpng12-0 (>= 1.2.13-4),
+          libsdl1.2debian (>= 1.2.10-1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.2.2.3)
+        [...]
+
+8.  Change the `md5sums` file for the right values for
+    `usr/share/applications/zsnes.desktop` and
+    `usr/share/doc/zsnes/changelog.Debian.gz` (I used the `md5sum`
+    command and copy-pasted it)
+9.  `tar czf control.tar.gz control md5sums postrm postinst`
+0.  `tar czf data.tar.gz usr/`
+1.  `ar r zsnes_1.510-2.2ubuntu3~ppa1_amd64.deb debian-binary
+    control.tar.gz data.tar.gz`

 
 I’m afraid that I can’t put the package into [my PPA][3], Launchpad only
 accepts source packages for uploads, and builds the binary packages
 
 I’m afraid that I can’t put the package into [my PPA][3], Launchpad only
 accepts source packages for uploads, and builds the binary packages