Linux (generic)

Custom kernel on your XENvz (OpenITC)

Saturday, 11 September 2010 22:30 Dirk Tilger

Abstract

This page is a tutorial on how to get a custom kernel running on a XENvz VPS.

Regular expressions with bash =~

Sunday, 22 August 2010 02:00 Dirk Tilger

A number of articles in the web give examples of how to use the bash regular expression operator =~ that exists since bash version 3. However the majority of these examples did not work for me.

The enlightenment occured when I had fully digested the sentence Any part of the pattern may be quoted to force it to be matched as a string. That means this example (taken from http://aplawrence.com/Linux/bash-regex.html) does not work:

OpenOffice 3.2 build fails on Gentoo

Wednesday, 26 May 2010 12:47 Dirk Tilger

Building openoffice 3.2.0 failed for module bridgetest with:

ERROR: error 65280 occurred while making ...

A previous build succeeded with the java USE flag disabled. There are a number of bug reports pointing to bug 283668, which seems related to the boost library.

Add new comment

eix-update fails

Saturday, 13 February 2010 15:07 Dirk Tilger

If eix-update doesn't quits with the following error message:

Unknown cache 'none' for directory '/usr/portage/local/layman/sunrise

Then you're running a newer version of eix with an older configuration file. Maybe you haven't run etc-update or dispatch-conf yet?

Add new comment

Last Updated on Friday, 08 October 2010 16:32

Feeding bad block reported by the kernel into e2fsck -l

Saturday, 30 January 2010 22:02 Dirk Tilger

Intro

Today I did again a backup of a machine that has served me well for years. As it happens with old hardware, apparently some hard drive sectors have gone bad over time. These messages I got in syslog:

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=23181294, sector=23181191
ide: failed opcode was: unknown
junge end_request: I/O error, dev hda, sector 23181191
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=23181294, sector=23181199
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 23181199

These sectors are "bad sectors" and they should be connected to the bad-inode of the ext3 filesystem the machine is using. A quick Google revealed tons of tutorials how to run badblocks to determine bad sectors, but I didn't find one that tells you how to add these reported ones. So here it comes.

miriup.de