Skip to main content

Poll Results

Well, another month, that means another poll results from Slackblogs. Last month's question was about OOo inclusion on Slackware's official tree. We 94 voters last month and here's the final results:

Yes, definitely 58 (61%)
No, people can use other source like Slackbuilds 29 (30%)
I don't use OOo, so it doesn't matter for me 7 (7%)

Most people would love to see OOo included on the Slackware. So far, people get it from SlackBuild as they already provide the SlackBuild script to convert the RPMs files into tgz so it can be easily be managed by pkgtools. I myself uses rpm2tgz to convert the files and so far, everything works just fine here.

FYI, building OOo from source it's really something painful. You have lots of requirements and lots of settings before you can start compiling (it doesn't count error on the compilation phase). If you don't believe it, try looking at this page. This will give you a head start of what the build process like.

One thing that makes me tickle when i read the vote post was the last option. There were people who still don't use OOo. I know it's bloated, but still it's probably the best office suite available in Linux platform.

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