Repository key expired VI

The repository-key had expired. The expiration date of the renewed key has been set to be October 20th 2012. You will have to update the key in your apt keyring by either using the pgp.mit.edu keyserver or a local keyfile in ASCII format at wgdd_archive_key.asc or by updating the wgdd-archive-keyring Debian package. Detailed information can also be found here.

New bluefish 2.0 packages available for i386 and amd64

With the release candidate 2 for Bluefish 2.0 my repository provides bluefish packages for the amd64 and i386 architectures. They will be automatically installed when you update your installed bluefish-unstable packages:

# apt-get dist-upgrade
The following NEW packages will be installed:
  bluefish bluefish-data bluefish-dbg bluefish-plugins
The following packages will be upgraded:
  bluefish-unstable bluefish-unstable-data bluefish-unstable-dbg bluefish-unstable-plugins

The latter became so called "transitional packages" and don't provide any functionality. They can be safely removed after upgrading to the bluefish packages:

# apt-get autoremove --purge bluefish-unstable bluefish-unstable-data bluefish-unstable-dbg bluefish-unstable-plugins

The package upgrade/installation will further replace any installation of the bluefish packages of Debian and Ubuntu!

Re: Making pbuilder just that little bit faster

It is true that making /var/cache/pbuilder/build a tmpfs makes a noticeable speed difference. But it seems you cannot cache the downloaded debs: ln: creating hard link ...: Invalid cross-device link.

Testing SMART status of my Toshiba USB harddrive

I recently bought an external USB harddrive, made by Toshiba. It's the HDDR500E03X model with 500GB space, internal shock sensor and ramp loading technology. Now yesterday I learned, that I can also cover its health status using the smartmontools. The usb* device types did not fit, but the sat did. It is as easy as running:

smartctl -d sat -c /dev/sdb
smartctl -d sat -t long /dev/sdb

Toshiba Tecra A10 (PTSB5E) - Part III

Connecting a NOKIA 6310i mobile phone via serial DLR-3P cable and the serial connector of the laptop (for Bluetooth see part II): After installation of the gnokii package(s) the the configuration file says:

model = 6510
connection = dlr3p

Then gnokii reports:

$ gnokii --identify
GNOKII Version 0.6.28
IMEI         : XXXX
Manufacturer : Nokia
Modell       : 6310i
Product name : NPL-1
Revision     : V 5.22

Toshiba Tecra A10 (PTSB5E) - Part II

So I got a little bit further with my little toy.

Bluetooth

Bluetooth works. The packages gnome-bluetooth and bluez are installed and the kernel module bluetooth is loaded. hciconfig reports this:

# hciconfig
hci0:   Type: USB
        BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 310:10 SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:11354 acl:105 sco:0 events:286 errors:0
        TX bytes:4012 acl:99 sco:0 commands:66 errors:0

I tried to connect to a SAMSUNG and a NOKIA mobile phone. After enabling visibility of the phone the bluetooth-applet showed the device. However I got an error saying The name org.openobex was not provided by any .service files when trying to access the mobile device. This was solved by installing obexd-server obex-data-server. Then I was able to access the phone contents via Bluetooth.

Virtualization

I recently tried to debug the mopac7 build error. I installed the qemu(-kvm) emulator. Loading of the kvm_intel module failed with kvm: disabled by bios. But this was easy to solve by enabling the Intel virtualization technology in the BIOS: push and hold the ESC key during startup until the laptop tells you to press the F1 key. Then enable the related BIOS option and you are done.

Fixed server outtime

The server and the whole domain wgdd.de were unreachable since this morning. This has been fixed now and everything should work as expected.