Group items tagged

Check your phpinfo() to see if pdo_sqlite is listed, if not, try adding extension=php_pdo_sqlite.so into the dynamic extensions section of your php.ini

To install SQLite3 on a Debian based system, use apt-get install php5-sqlite3

http://widget.mibbit.com/?server=irc.freenode.net&channel=%23test

4.1. A large warning message is displayed when I boot Linux, saying something about '/lib/tls'. What should I do? Do as the message advises! Some modern distributions ship with a 'TLS' version of glibc that is not fully compatible with Xen. To use Xen reliably and with maximum performance you must disable the incompatible glibc. You can easily do this by moving the /lib/tls directory (e.g., mv /lib/tls /lib/tls.disabled). Alternatively, install a Xen-specific GLIBC, see XenSpecificGlibc.

Linux/Unix notes If you installed Azureus 3.0.2.0 or higher, you can also try a manual update. Make sure Azureus is not running Open up a shell Change to the azureus program dir Run "./updateAzureus" (If this is your first time using the script, you may have to "chmod +x ./updateAzureus"). If you don't have this script, you can create one: sudo java -cp ./plugins/azupdater/Updater.jar org.gudy.azureus2.update.Updater updateonly `pwd` ~/.azureus Assuming you have a ./plugins/azupdater/Updater.jar, this will elevate your rights and apply any updates that couldn't be done with your normal user's rights.

Transmission

Azureus

Azureus FTL. System resource hog, it's dependant on Java, and personally, I've encountered more bugs with Azureus than any other BT client out there.

08/31/08 12:55:48 changed by josef ¶ I've written a patch to support magnet links now. You need to check out svn rev 1065 of libtorrent/rtorrent, and get http://ovh.ttdpatch.net/~jdrexler/rt/experimental/dht-pex-static_map.diff and http://ovh.ttdpatch.net/~jdrexler/rt/experimental/magnet-uri.diff then in the directory that has the libtorrent and rtorrent subdirs you've checked out, do patch -p0 < dht-pex-static_map.diff patch -p0 < magnet-uri.diff and recompile both. It uses the official magnet protocol from Bittorrent BEP-0009 which is incompatible with Azureus and so far only supported by uTorrent 1.8+, so it'll only work if there are recent uTorrents in the swarm. It supports magnet links in both the old style base32 encoded hashes as well as the recommended URL-encoded hashes. Note that if there is one or more tracker URLs to use for the download, it must be present as "tr=..." argument in the magnet URI, because there is currently no way of adding trackers in rtorrent afterwards, so without that it'll use DHT and nothing else. After opening a magnet URI, it will add a meta download to download the actual torrent info. When that is complete, it is replaced by the real torrent. The meta data is saved in your standard torrent download directory, you can delete that after the real torrent has appeared, or you can keep it in case you need to open the same magnet URI again.

SRTP usually, ZRTP less often, and VOIP over VPN least often. As long as both sides of the connection support SRTP or ZRTP and are configured to kick it in as needed, usually all I do is check for the lock icon.

Any clients which support OTR should be encrypted easily. Adium is pretty standard on OS X; Pidgin or Miranda work fine on the Windows end. And if the other person doesn't support OTR, the system falls back to unencrypted.