Ondřej Čertík: How to connect to the internet using T-Mobile and bluetooth
I have a laptop with Debian, cell phone (Nokia N70) with bluetooth and this howto describes how to connect to the internet.
Connect USB bluetooth dongle to the laptop and check it:
Scan for the phone:
Create a serial device for communicating with the modem in the phone:
(A dialog will popup on the phone asking me to allow the laptop to connect.)
Connect using wvdial:
And that's it, I am connected.
Prerequisities
And setup the /etc/wvdial.conf file:
Connect USB bluetooth dongle to the laptop and check it:
$ hciconfig
hci0: Type: USB
BD Address: 00:02:72:D2:23:12 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:686 acl:0 sco:0 events:22 errors:0
TX bytes:337 acl:0 sco:0 commands:21 errors:0
Scan for the phone:
$ hcitool scan
Scanning ...
00:19:79:86:EB:BC Nokia N70
Create a serial device for communicating with the modem in the phone:
$ rfcomm connect /dev/rfcomm0 00:19:79:86:EB:BC 3
Connected /dev/rfcomm0 to 00:19:79:86:EB:BC on channel 3
Press CTRL-C for hangup
(A dialog will popup on the phone asking me to allow the laptop to connect.)
Connect using wvdial:
$ wvdial
--> WvDial: Internet dialer version 1.56
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT*99***1#
--> Waiting for carrier.
ATDT*99***1#
CONNECT
~[7f] #@! ! 2 # $@# ! $ %\ " & * g %~
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Wed Nov 28 12:58:55 2007
--> Pid of pppd: 4378
--> Using interface ppp0
--> pppd: [08][06][08] [10][06][08]
--> pppd: [08][06][08] [10][06][08]
--> pppd: [08][06][08] [10][06][08]
--> pppd: [08][06][08] [10][06][08]
--> local IP address 172.24.171.97
--> pppd: [08][06][08] [10][06][08]
--> remote IP address 10.6.6.6
--> pppd: [08][06][08] [10][06][08]
--> primary DNS address 62.141.0.2
--> pppd: [08][06][08] [10][06][08]
--> secondary DNS address 213.162.65.1
--> pppd: [08][06][08] [10][06][08]
And that's it, I am connected.
Prerequisities
$ wajig install wvdial bluez-utils
And setup the /etc/wvdial.conf file:
$ cat /etc/wvdial.conf
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = USB Modem
Baud = 460800
New PPPD = yes
Modem = /dev/rfcomm0
ISDN = 0
Phone = *99***1#
Password = doesnt_matter
Username = doesnt_matter
Stupid Mode = 1
Well, I havn't seen this recently. Maybe because aptitude has rename
'upgrade' do 'safe-upgrade', to make it obvious, that 'dist-upgrade' might do
unwanted things.Back when I was the maintainer of the galeon webbrowser package, I got bug
reports and reports on IRC each time the mozilla packages was updated.The galeon package used to have a conflict with mozilla of any newer major
version than the one it was built with. This was a good thing - mozilla APIs
were chaning, and when Mozilla was upgraded from let's say version 1.5 to 1.6,
it would break galeon. Galeon would at least need to be recompiled or might
even need source changes. So there was plenty of reason to add this conflic.People were using 'dist-upgrade' all the time, and what dist-upgrade did then
was to upgrade the mozilla package by removing galeon. And they couldn't even
install galeon back again, because the new mozilla had replaced the old mozilla
in unstable. And each time, I basically had to tell people "well, you shouldn't
have used 'dist-upgrade', it's for upgrading between major version of Debian,
not for daily use.In fact, running dist-upgrade right now would uninstall
'iceweasel-dom-inspector' for me. I guess this is exactly due to the same
reasons.I'm wondering whether we should maybe do a 'uninstall-ok' list (or
'dist-upgrade-hints') and ship it with the distribution. I'd then modify the
'dist-upgrade' command to
These are all just 'first-builds' so problems could well lie ahead but I have now built a set of cross built packages for Emdebian (ARM) that edos-debcheck says is installable for a basic GPE installation. Only one package remains as a problem - gpe-filemanager builds fine but the current dependencies of libgnomevfs mean that gconf is required which doesn't give an option to disable ldap which is something I would rather do without. Certainly, existing GPE installations do without ldap but that could just be because these tend to use older versions of the particular libraries.
I bought me a cheapo webcam the other day and the first thing (meh… actually the second. The first thing I had to do was obviously getting this little piece of plastic working…) I wanted to do was making a time-lapse video of me working on my diploma thesis or something. With a little help from google and the friendly folks at debian-user-german I finally got it working.
What you need:
When Ubuntu announced public availability of Personal Package Archives, I
thought it might be good to use it to provide up to date Gammu related
packages. After successful registration I uploaded Gammu package and no
reaction so far, so I'll wait.
However this memorised me that I wanted to use OpenSUSE Build Service for same
purpose some time ago. I filled in registration and as I didn't receive any
email about being accepted, I absolutely forgot about that. Now just tried to
log in and it works. So you can now have access to latest Gammu, python-gammu
and Wammu packages for most recent RPM distributions (Fedora 7, Fedora 8,
Mandriva 2006, Mandriva 2007, openSUSE 10.2, openSUSE 10.3, openSUSE Factory,
SLES 9 and SLE 10). I could not test them so any feedback is welcome :-). You
can find all packages on
Finally, thanks to anibal, I got my pgp signature by a DD, now I can continue
We had a nice trip the rest of the way home from our
Is there an existing system which will allow me to query Apache logfiles via an SQL string? (Without importing into a database first).
I've found the perl library SQL::YASL - but that has a couple of omissions which mean it isn't ideal for my task:
PDF on Kindle
I've seen plenty of good commentary on the
It seems there is a long standing tradition to post a “Hello Planet” entry when being added to a new planet.
Well Hello 
The radeonhd xorg driver recently gained full RandR 1.2 support, I’ve tested it out moments ago and it works. It just works. (DIE fglrx, DIE DIE DIE).
Joy and happiness today, and thanks to Julien CRISTAU, it’s even packaged in experimental (I owe you a beer, obviously).
Now, given that we now have a working video driver, and an opensource one even, let’s think about implementing something in pommed for that nice little video switch button that’s on F7.
I don’t really know how to go about implementing the video switch feature. Either I’m doing it in pommed in the form of a shell script that will have to “steal” the user’s X session, or I’m doing it in the frontends, which will obviously be a bit easier.
Which raises another question: shell script around xrandr, or RandR support in the frontends?
That latter option doesn’t look terribly appealing to me, as it involves quite some code that will have to be maintained up-to-date wrt RandR evolutions, and that also means being backward-compatible with older RandR versions etc.
So it’s probably going to be only a simple shell script, executed by the frontend.
I’d like more input on this, so if you have a take on how it should/could be done, please drop me a mail. Otherwise you’ll have to live with whatever I’ll come up with ;-)
It's quite some time since I didn't blog about D-I i18n and the number of new languages we'll support in the next Debian version, lalala...
A few works are on their way, indeed:
What does this topic mean? Hmh... Maybe you don't know
I've given the idea of centrally configuring my hosts another go. Previously I
had some meta packages that would pull in packages, but that's not very
interesting. Furthermore the archive I set up didn't scale, dpkg-scanpackages
plus makefiles aren't really fun to use.
Now, I have a set of cfengine scripts that gets distributed as .deb. That
sounds messy, but connecting reprepro with the right .dput.cf makes updating a
breeze.
cfengine itself is a beast not easily tamed. It has some weird ideas about
timeouts and when (not) to execute scripts. So far I'm only using "editfiles"
in this setup to do tweaks like comment HashKnownHosts in ssh_config, add some
sources.list entries, add %adm to sudoers, etc. Next step will be to also
automatically push config into chroots, and to pull passwd.db and friends for
use with libnss-db.