I got Bluetooth working

[anticapitalista]

From a fresh antiX-M8.5, apt-get dist-upgrade brings in 302MB of downloads.

(Be careful with downloading debs from one antiX and installing them on another antiX, though)

[Danum]

Anti, this might have been mentioned, the script to install KDE in Antix 8.5 is out of date, it tries to install kde-minimal,
it should be kde-standard, (kde-minimal is no more in 4.4),
As a bit of an exercise I installed Antix 8.5 base on a Packard-Bell EasyNote R1005, 1.50GHz Celeron, with a big 500Mb of memory, really cutting edge laptop this is, installed 4.4 netbook from sid and after removing just about everything except the base and 4.4 it runs surprisingly well,
before I removed the alteratve desktop install I checked as it changed last week

[m_pav]

Originally Posted by voorhees1979

Exactly what I do. Download all updates on one machine, then I network the files to the other machines running antiX to avoid re-downloading on all machines. Would hate to think what a fresh install of antiX 8.5 would bring in now, would be a huge update I think.

I also periodically enable all repos, after ensuring my system is fully updated, then run apt-get update followed by apt-get autoclean to remove old version package debs no longer required, then disable the additional repos.

I could use aptoncd but I find external hard disks significantly faster and easier to keep in sync.

Mike P

[m_pav]

Major edit to the end of my first post if anybody cares to try it. One requirement I did not state was the user must be in the fuse group, but as the stock Mepis build has this condition met by default, I left it out.

Source of my findings is the OpenSuse forum

Mike P

[m_pav]

This morning, I managed to get Mobile Tethering, connecting to NZ Telecoms XT network via bluetooth, posting from it right now.

I don't know if this is possible with the stock standard Mepis 8.5, but it is certainly possible using Danums recipe to upgrade a fresh install to KDE 4.4 and installing a few extra bluetooth tools, the most useful of which is blueman.

Snapshot provided.

Mike P

[m_pav]

I suppose I should say a bit about how I got it working.

The main app is blueman 1.2.4 from Testing (blue1.jpg), which will detect the mobile or BT enabled device. You first have to create a trust relationship by pairing the phone and you system by clicking on Device > Pair and follow the prompts. Once the trust relationship has been made, you'll see the option to pair with the device is greyed out because that's already done and the untrust option becomes available, (blue2.jpg)

Once paired, you can go through setup to discover your phones and systems capabilities and make them available. If you only want dialup, then just choose that option, if you want serial, which gives other functions like remote control (move mouse and click buttons with phone, like a wireless presenter, but better), then go ahead and enable that.

Once setup, you can simply choose whatever option you want (blue3.jpg), for this thread, I chose dialup. A few seconds after choosing dialup, the system notification window will pop up saying DUN will now be available via knetwork. You can now go ahead and set up a DUN connection. Your NetworkManager icon will likely change and after creating a new DialUp network connection, (blue4.jpg) the option to use it will show quite clearly when you click on the NetworkManager icon in the future after you have reconnected your phone by bluetooth and selected the dialup service (blue5.jpg)

The options I show in blue4.jpg are for NZ Telecom. I don't think the password is required, but the Telecom rep told me to just use the word telecom as the password if required.

Once connected, throughput is akin to 1.15 mbps, restricted mainly by the max speed of the bluetooth connection between the phone and your system.

Mike P