svc: failed to register lockdv1 RPC service (errno 97).

When I tried to start ‘nfs-kernel-server’, it failed.

# /etc/init.d/nfs-kernel-server start
Exporting directories for NFS kernel daemon....
Starting NFS kernel daemon: nfsd svcgssd failed!

syslogs:

Nov 11 23:32:04 nasbox kernel: [ 8106.165582] nfsd: last server has exited, flushing export cache
Nov 11 23:32:05 nasbox kernel: [ 8107.240419] svc: failed to register lockdv1 RPC service (errno 97).
Nov 11 23:32:05 nasbox kernel: [ 8107.245528] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Nov 11 23:32:05 nasbox kernel: [ 8107.245566] NFSD: starting 90-second grace period
Nov 11 23:32:05 nasbox rpc.svcgssd[26744]: ERROR: GSS-API: error in gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more information - Key table entry not found
Nov 11 23:32:05 nasbox rpc.svcgssd[26744]: unable to obtain root (machine) credentials
Nov 11 23:32:05 nasbox rpc.svcgssd[26744]: do you have a keytab entry for nfs/@ in /etc/krb5.keytab?


If you have DNS server running, make sure you remove the following lines from /etc/hosts:

127.0.0.1 nasbox localhost
::1 nasbox localhost ip6-localhost ip6-loopback

However, if you don’t have DNS server running to manage your domain then you need to explicitly assign the IP address to the domain. Adjust the IP address and hostname to your environment:

#192.168.1.123 nasbox.myserver.com nasbox

In my case, I could successfully start nfs-kernel-server:

# /etc/init.d/nfs-kernel-server start
Exporting directories for NFS kernel daemon....
Starting NFS kernel daemon: nfsd svcgssd mountd.

Ubuntu 11.10: 32-bit applications do not run 64-bit

After upgrading from natty (11.04) to oneiric (11.10), some 32-bit applications don’t run anymore. I have ‘ia32-libs’ and ‘libc6-i386′ packages installed. For example, when I run Android adb,

$ ./adb
bash: ./adb: No such file or directory
$ file adb
adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, stripped

After googling around, the fix is quite simple: re-install ‘libc6-i386′.

$ sudo apt-get install --reinstall libc6-i386
$ ./adb
Android Debug Bridge version 1.0.29

-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
...

Thanks to this post: https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/852101

How to decompress .tar.Z

One way to extract a .tar.Z file:

$ zcat file.tar.Z | tar xvf -

Beautify gitk font on Debian/Ubuntu

Install tk8.5, if not yet installed:

# apt-get install tk8.5
# update-alternatives --config wish

There are 3 alternatives which provide `wish'.

  Selection    Alternative
-----------------------------------------------
          1    /usr/bin/wish8.4
*+        2    /usr/bin/wish-default
          3    /usr/bin/wish8.5

Type in the number that corresponds to tk8.5 (in my case was 3) then hit enter.
Change fonts in ~/.gitk to DejaVu Sans Mono.

set mainfont {{DejaVu Sans Mono} 9}
set textfont {{DejaVu Sans Mono} 9}
set uifont {{DejaVu Sans Mono} 9 bold}

How to replace default fonts in MIUI rom

MIUI (1.7.22) uses Arial as the default font.  If you hate it as I do, here is how to change it.

I assume you have ‘adb’ working. We are going to replace only 2 fonts – Arial.ttf and Arial-Bold.ttf.

First, let’s back up the old fonts just in case thing didn’t go well as we want to. (I learned this the hard way, and keen to avoid it at all cost)

$ adb pull /system/fonts/Arial.ttf
$ adb pull /system/fonts/Arial-Bold.ttf

You should have a copy of the above 2 fonts on your local computer. Next is to connect to your phone and replace those fonts with DroidSans.ttf and DroidSans-Bold.ttf respectively.

$ adb shell
# cd /system/fonts
# cp DroidSans.ttf Arial.ttf
# cp DroidSans-Bold.ttf Arial-Bold.ttf

Restart your phone. Voila, your text doesn’t look as ugly as before; well at least that’s what I think.