High Activity

News

  Analyzed 7 days ago based on code collected 7 days ago.
 
Posted 4 days ago
Der Spiegel (jedenfalls der Online Arm) jammert ja seit ein paar
Tagen rum, man solle mal seinen Adblocker ausschalten. Wegen der
Kinder, oder so. Das unerwartete Ergebnis: Es gab offenbar noch
jede Menge Nutzer unter den SPON Lesern die ... [More] noch garnicht wußten,
was ein Adblocker ist... Dementsprechend positiv war der Effekt bei
den Leuten von adblockplus.org:

Von daher hat SPON da doch ganz gute Aufklärungsarbeit
geleistet... ;)

Die Titanic hat natürlich ihre eigene amüsante Sicht auf die
Dinge:

Dpa-Flatrate, *schenkelklopf*. Dem habe ich nichts
hinzuzufügen. :-)

(Jaja, die Onlineangebote von anderen Zeitungsverlagen jammern
gerade ebenfalls rum. Nicht nur der Spiegel. Aber irgendwie klingt
die Meldung die der Spiegel einblendet am drastischsten - und
soweit ich weiß waren sie auch die ersten die damit angefangen
haben.) [Less]
Posted 9 days ago
So while testing Proxmox VE 3.0 RC1 I had the need to reboot the system into a kernel version different than the one being the default in the bootloader GRUB. “lilo -R …” worked fine in the past, but with GRUB it’s not as trivial on the first ... [More] sight to get its equivalent. I remembered to have had problems with grub-reboot in the past already, or to quote a friend of mine: “has grub-reboot worked ever?”

Well yes, grub-reboot works – but only once you’re aware of the fact that you need to manually edit /etc/default/grub. It’s actually documented at wiki.debian.org/GrubReboot, but not in the man page/info document of grub-reboot itself (great idea to provide a separate wiki page for this issue but not consider editing the official documentation instead, not).

So here you go:

# grep GRUB_DEFAULT /etc/default/grub
GRUB_DEFAULT=0
# sed -i 's/^GRUB_DEFAULT.*/GRUB_DEFAULT=saved/' /etc/default/grub
# grep GRUB_DEFAULT /etc/default/grub
GRUB_DEFAULT=saved

# update-grub
[...]
# grep '^menuentry' /boot/grub/grub.cfg
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-amd64' --class debian --class gnu-linux --class gnu --class os {
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
menuentry 'Debian GNU/Linux, with Linux 2.6.32-20-pve' --class debian --class gnu-linux --class gnu --class os {
menuentry 'Debian GNU/Linux, with Linux 2.6.32-20-pve (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os {
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

# grub-reboot 2 # to boot the third entry, the command writes to /boot/grub/grubenv
# reboot

FTR: Filed as #707695. [Less]
Posted 11 days ago
Before I started to modify the original setup I wanted to backup a couple of things because I knew, that most of the steps are not straightforward and I might need to get back (To be honest, I had two other Lenovo machines where I tested the steps ... [More] before I applied them on my X230 )
I started with creating the recovery media and Lenovo supports to use usb flash media instead of cd recordables, too. But something told me that I should not fully trust the software to create a bootable usb flash drive. Long story short: The software creates an unbootable flash drive if you do not prepare the flash drive before you start the program
Have a look at the instructions at . It’s not only a missing boot flag which I set afterwards, there seem to be other constraints, too. The flash drive, which did not work, had a strange partition table, too. On the working flash drive it looked like this:

Disk /dev/sdc: 15.8 GB, 15804137472 bytes
255 heads, 63 sectors/track, 1921 cylinders, total 30867456 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0×00000000

Device Boot Start End Blocks Id System
/dev/sdc1 * 2048 30867455 15432704 7 HPFS/NTFS/exFAT

I assume that the starting cylinder is important.

Usually you can create recovery media only once but there’s a hack to do it again, which is very useful if things go wrong. Open command prompt and type:

echo 0 > Q:\FactoryRecovery\RECOVERY.INI:Done

It’s also a good idea to save the mbr and partition table, e.g.:

dd if=/dev/sda of=mbr-backup-sda.img bs=1 count=512
sfdisk -d /dev/sda > sfdisk-sda-dump.txt
sfdisk -l /dev/sda > sfdisk-sda.txt

(Basically the first command is sufficient but I prefer to have different backups) [Less]
Posted 12 days ago
TL;DR: {fqdn, "jabber.die-welt.net"}.

So, how many servers do you have, that are still running Squeeze? I count one, mostly because I did not figure out a proper upgrade path from OpenVZ to something else yet, but this is a different ... [More] story.

This post is about the upgrade of my “communication” machine, dengon.die-welt.net. It runs my private XMPP and IRC servers. I upgraded it to Wheezy, checked that my irssi and my BitlBee still could connect and left for work. There I noticed, that Pidgin could only connect to one of the two XMPP accounts I have on that server. sargentd@jabber.die-welt.net worked just fine, while evgeni@golov.de failed to connect.

ejabberd was logging a failed authentication:
I(<0.1604.0>:ejabberd_c2s:802) : ({socket_state,tls,{tlssock,#Port<0.5130>,#Port<0.5132>},<0.1603.0>}) Failed authentication for evgeni@golov.de

While Pidgin was just throwing “Not authorized” errors.

I checked the password in Pidgin (even if it did not change). I tried different (new) accounts: anything@jabber.die-welt.net worked, nothing@golov.de did not and somethingdifferent@jabber.<censored>.de worked too. So where was the difference between the three vhosts? jabber.die-welt.net and jabber.<censored>.de point directly (A/CNAME) to dengon.die-welt.net. golov.de has SRV records for XMPP pointing to jabber.die-welt.net.

Let’s ask Google about “ejabberd pidgin srv”. There are some bugs. But they are marked as fixed in Wheezy.

Mhh… Let’s read again… Okay, I have to set {fqdn, "<my_srv_record_name>"}. when this does not match my hostname. Edit /etc/ejabberd/ejabberd.cfg, add {fqdn, "jabber.die-welt.net"}. (do not forget the dot at the end) and restart the ejabberd. Pidgin can connect again. Yeah.

5 comment(s) | this blog is flattr enabled [Less]
Posted 12 days ago
My first Lenovo notebook was a X60s, which is still running quite well but 32 bit is not enough It came with WinXP preinstalled because there was no option to order it with Linux or without OS. All other notebooks that I used afterwards came ... [More] without OS so there was no other OS to take care about. My X230 came with Win7 preinstalled so I decided to compare the actual installation with my first one eight years ago (I don’t really need the preinstalled OS so I might as well just make a clean installation but I was interested about the possibilities for our customer installations).
So i will write some posts about certain aspects of the original setup. First one will be about backuping up the factory default state because there the troubles started [Less]
Posted 15 days ago
Take care when ordering your notebook in the Lenovo webshop, you might miss a camera, too. I configured mine and I wanted a builtin camera. Then I decided that the 3×3 antennas would be better than the 2×2 and so I changed the configuration. What I ... [More] did not see was, that the box for the camera options, where you choose if you want a builtin camera or none, just disappeared and the camera gets unselected. When checking the config again before hitting the order button I checked every option but there was no line like “camera: none” so it looked good for me. When the notebook arrived there was no camera builtin. Reason: The third antenna in the 3×3 config needs the space where the camera would be. Unfortunately there was no hint or warning in the webshop
Of course I was able to send it back and order a new one but this process is very time consuming. This happened a couple of weeks ago and in the meantime I got my new X230 but the bug is still not fixed in the shop although I reported it
(BTW: I ordered in the shop of Austria but I also checked the US shop which has a similiar problem)

I hope this post helps somebody else not to run into the same problem. [Less]
Posted 17 days ago
#newinwheezy game: !Grml packages in !Debian: http://ur1.ca/dnbxd
Posted 17 days ago
Following up on the #newinwheezy game: Debian/wheezy is the first Debian release which ships packages from the Grml system. Grml became an official Debian Derivative and I’m very happy that three major projects of Grml found their official way into ... [More] Debian:

grml2usb: install Grml system / ISO to usb device
grml-debootstrap: wrapper around debootstrap for installing pure Debian
grml-rescueboot: Integrates Grml ISO booting into GRUB

As the description states grml2usb is interesting for getting Grml onto a USB device when the dd(1) approach (“dd if=grml.iso of=/dev/sdX“) just isn’t flexible enough.

grml-debootstrap provides a decent way to install Debian systems from the command line. As its author I might be biased but I’ve to mention that it’s working so nice that it is in use at several of my customers for automated roll-outs without any worries at all, and I got reports from other companies that they are very happy users of it as well.

Finally the grml-rescueboot packages provides a very simple and nice way to boot a rescue system from within GRUB (short version: throw a Grml ISO to /boot/grml/, run update-grub and be done).

PS: Thanks everyone for joining the #newinwheezy game over at planet.debian.org. [Less]
Posted 20 days ago
Debian/wheezy includes a bunch of packages for people interested in digital forensics. The packages maintained within the Debian Forensics team which are shipped with the upcoming Debian/wheezy stable release for the first time in a Debian release ... [More] are:

dc3dd: patched version of GNU dd with forensic features
extundelete: utility to recover deleted files from ext3/ext4 partition
rephrase: Specialized passphrase recovery tool for GnuPG
rkhunter: rootkit, backdoor, sniffer and exploit scanner (see comments)
rsakeyfind: locates BER-encoded RSA private keys in memory images
undbx: Tool to extract, recover and undelete e-mail messages from .dbx files

Join the #newinwheezy game and present packages which are new in Debian/wheezy. [Less]
Posted 22 days ago
    
 

 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.