In the last days I uploaded several (new) packages to backports.org:
A new haproxy 1.4.4-1~bpo50+1 package is in preparation and needs testing before uploading. You can find the package here.
While I normaly don’t care much about Ubuntu, I’m subscribed to lauchpad.net for the packages I’m involved within Debian.
Sometimes apears informative stuff there, which reminds me about my todos or just pointing me to real problems. Most of the time, I’m just ignoring the reports, as the are useless or just unrelated to me packages in Debian.
But in some cases the reports are just making my day.
In the last days, I replaced my Nokia E90 with a Nokia N97 mini. As I’m using my mobile from time to time to hook up to the internet when traveling, I thought I just need to replace the MAC in my /etc/bluetooth/rfcomm.conf and that’s it. As always … Murphy striked back. After debugging for hours I realized the DUN channel seems depending on the model.
You can discover your DUN channel something like:
# hcitool scan
Scanning …
3C:F7:2A:1A:4D:2A Cycophone
# sdptool browse 3C:F7:2A:1A:4D:2A | \
grep -9 “Service Name: Dial-Up Networking” | \
tail -10 | grep Channel
Channel: 22
So your /etc/bluetooth/rfcomm.conf should now look like:
…
rfcomm0 {
bind yes;
device 3C:F7:2A:1A:4D:2A;
channel 22;
comment “Cycophone”;
}
…
xm list | grep <VMName>
xm block-list <VMName_Number>
xm block-detach <VMName_Number> <VMName_Vdev> -f
xm block-attach <VMName_Number> file:///iso/disk.iso \
hdc:cdrom r