-The Host Wizard will download and add/update or remove host entries of advertisers to improve surfing. klhrevolutionist and Mic67 had both mentioned this around here. I looked over the license really well and I think this wizard is ok.

-*The PocketPC Wizard needs password verification and some other fine tuning but it does function ok for testing. If you have a password make sure you get it right. Also make sure you have commented out "usepeerdns" in your /etc/ppp/options file or it will NOT work. Read how to set up Fur after connection, below.

dbus config was modified to run as 'root' rather than 'messagebususr' (or whatever it was). I DO NOT KNOW if this is a security problem of any kind. Since everything else is running as root, I wouldn't worry too much about it. Unless there are some evil looking people withing 30 feet using bluetooth when you turn yours on or you run a multiuser puppy server of some kind.

I configured Claws-Mail with all "polite plugins" included by default. By polite, I mean any plugin that does NOT either modify or copy incoming email (att_remover, etc..) and/or make an internet connection by default (rss plugin). btw, at the last minute I noticed compface plugin was left out. DESTDIR must not work on that one. I'll fix that in the final image.

hmm, does this mean that bluetooth is now working on Puppy? Is it fully working or only partially? my friend stopped using puppy because he wasn't able to use bluetooth to surf the web from his phone's connection.

You've even got my vote on that name. I completely forgot to take 8.3 into consideration.

Sit Heel Speak wrote:

John Doe wrote:

...Do you all want GTKam and GTKPod included also? How about Skype?

Yup to both.

I added both GTKam and GTKPod, decided against Skype (although you can get the pet here). Because of size of it and QT (don't forget to install QT to get it to run) it really "bloats" the squash file. I've got the squash file at 26 megs right now. Skype itself is another 10 and then QT...I figured I leave that seperate.

bostonvaulter wrote:

hmm, does this mean that bluetooth is now working on Puppy? Is it fully working or only partially?

Great question. I don't have any bluetooth myself. I do have a note (in my head) to make sure I add the device node and double check that I have all the utils. It was added because I noticed pilot-link had it as a config option. lib-synce plans to support bluetooth also, but I can't get 0.9.3 to connect to my device and also FUR is only written for 0.9.1 so far.

>>

ALso have a couple "wizards". One to connect the PocketPC. I have some more testing and work to do on it. It a piece of crap right now. It does connect my device but has trouble detecting failure if things don't go 1.2.3.

Working on a CDMA(EVDO)/USB script to use phone as modem. It conflits with PPC /etc/ppp/options options.

Forum member daemon reports that an older version of bluez-libs (2.10) is necessary before Puppy will connect to his gprs unit. He provided the 2.10 libraries here -
http://www.murga-linux.com/puppy/viewtopic.php?p=86314#86314

Maybe this also applies to mobile phones?

And debernardis created a wiki page on Bluetooth setup -
http://puppylinux.org/wikka/ExperimentalBT

If it's true that the recent Bluez-libs and Bluez-utils won't work, then I don't think it will be possible for JPilot to connect to bluetooth devices, because the most recent pilot-link (0.12.2) fails to compile against the older 2.10 Bluez-libs. And earlier versions of pilot-link have no bluetooth support at all.

Thanks for jumping in and bringing some institutional memory to the process.

tempestuous wrote:

Forum member daemon reports that an older version of bluez-libs (2.10) is necessary before Puppy will connect to his gprs unit. He provided the 2.10 libraries here -
http://www.murga-linux.com/puppy/viewtopic.php?p=86314#86314

Thanks. Seems he identified starting dbus as the problem. I seem to recall Nathan posted somewhere that the newer kernel he was using in graphpup fixed something to do with bluetooth (perhaps this is what it was).

tempestuous wrote:

...then I don't think it will be possible for JPilot to connect to bluetooth devices, because the most recent pilot-link (0.12.2) fails to compile against the older 2.10 Bluez-libs. And earlier versions of pilot-link have no bluetooth support at all.

ARG!!! Thanks for the info. I'll still post what I've got soon but it's looking as if this squash file is a version or two ahead of it's usefulness.

There was once a bluetooth mouse with usb plug around here. I'll try to see if I can dig it up for testing.

"The package should create a specific key for the machine it is running on with the command 'dbus-uuidgen --ensure' and the daemon will have to be started with 'dbus-daemon --system', which I have added to rc.local."

I wonder if dbus simply needs started for the latest bluetooth utils to work?

A quick phone call and found that the usb/bt/mouse that I thought was around here is with my dad in another state. He's back in 12 hours, so I can test then. I hope it was bluetooth anyway, it glowed blue.

damn...glowing blue was the only thing it had in common with bluetooth (other than RF, but it's not "bluetooth"). It's one of these:

http://www.shopping.com/xPF-Wireless-Optical-Notebook-Mouse-DX-WOM20

More soon. It's 3AM here. It did seem hcid started with dbus after recompiling dbus with the --localstatedir=/usr option. Had same problem as this:
http://lists.freedesktop.org/archives/dbus/2006-September/005891.html

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum