Skip to main content

TeamViewer 8 Beta SlackBuild Script

I have just pushed a new SlackBuild script into my SlackHacks repository and that is TeamViewer 8 Beta. I have taken a maintainer position on this script from Binh Nguyen and before the final version of this package gets released, i would like to get a feedback from all of Slackware users who uses TeamViewer to try this new version.

There's one difference with previous version of TeamViewer 7, which is the new version requires you to start teamviewerd, a new daemon for TeamViewer process prior launching the application. I have created a simple rc.teamviewerd file to handle this and it's placed under /etc/rc.d/ directory which happens to be the same directory used by other services in Slackware.

So, the procedure is:
- build the TeamViewer 8 Beta
- chmod +x /etc/rc.d/rc.teamviewerd (to make sure it's executed on next boot as well)
- /etc/rc.d/rc.teamviewerd start
- launch the shortcut of TeamViewer 8

To make this process repeated on every boot sequence, add this line
in your /etc/rc.d/rc.local:
if [ -x /etc/rc.d/rc.teamviewerd ]; then
/etc/rc.d/rc.teamviewerd start
fi

If nothing goes wrong, you shall see the new TeamViewer 8 Beta in action.



PS: If you are running multiple TeamViewer on different machines and the other machine has been upgraded to TeamViewer 8, you must use this beta version as well or else you won't be able to connect to that machine using the previous version (7).

Please let me know if you are running into trouble using this SlackBuild. FYI, i'm running Slackware-Current on 32 bit machine. I don't have 64 bit machines and i don't think i can help you on those architecture for now. Previous maintainer has stated that TeamViewer 7 can work on multilib setup, but i can't guarantee on this version as i haven't tested yet.

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue