sh: uncompress: command not found

By -
If you are uncompressing a program from a .bin file and you are working with a freshly installed Linux distro, you might receive the following error - sh: uncompress: command not found. This error might be a result of either the gunzip program is not installed on your system, or a proper link association with the compression application does not exist.

I will provide instruction on how to fix the latter first, because usually gunzip should be installed by default. To create the proper file linking we will use the ln command, which is used to create links to files. So, all you have to do is first make sure you are logged in as root, then run the following command:
ln -s /usr/bin/gunzip /usr/bin/uncompress

Once this has been done try running the command which generated the "sh: uncompress: command not found" error. I last encountered this error when I was installing the Valve Source gaming dedicated server - SRCDS, and I was executing the following command - ./hldsupdatetool.bin.

Now, if gunzip is not installed on your system, just login as root and use yum or yast to do so. Below is how you can install gunzip using yum.
yum install gzip

Popular posts from this blog

Format MAC Address [JavaScript]

By -
I am currently working on a project which will allow users to register their Wi-Fi enabled, non-web browser enabled, devices on the network. These are devices like printers, Apple TV, and Xbox*. One of the data points that have to be collected from the user is the device MAC address. The project customer wants that address to be properly formatted when they see it in the support ticket.

We have several options. We can format the address either on the back-end after the form has been submitted. Or we can format it on the front end via a separate text field for each character pair, but that is too many fields to handle. A better solution is to use a single field and format the user input at the time of input or upon submit. In those cases, the former is better because the data will already be formatted when the overall form input is being validation after the user clicks the “Submit” button.

We are going to format the user input as it is being provided, thus having proper data when vali…
Read more

How to setup Coda 2 to push to GitHub?

By -
Image
Setting up a new site in Coda 2 and cloning a GitHub remote repository is not that big of a deal. Where you will most likely run into problems is when you try to push your changes to the GitHub remote repository. Below I will show you how to update the Git config file in your local repository so you do not run into one of the following errors:
git push failed remote: Remote anonymous access to repository deniedgit push origin master Username: fatal: Could not read passwordThe GitHub repository address I am going to use is that of Source Code DNA: https://github.com/thetitan/sourcecodedna.git. I will assume that you have already setup your Coda 2 site profile and cloned your repository, you have made some changes, and now you are ready to push those changes to your projects GitHub repo.
Read more

Messing with WordPress SPAM Bots

By -
If you have a WordPress based blog, or otherwise use WordPress as a CMS for your website, you are either getting a lot of bad user accounts being created or noticing a lot of knocking on your wp-login.php page. WordPress has a nice feature which allows you to install WordPress in a directory other than the root one. For example, your site is served from http://blog.example.com, but WordPress can be installed in http://blog.example.com/wpcms. In past versions of WordPress, prior to 3.8 or maybe be older than that, unless you knew the exact path to where WordPress was installed you could not get to the dashboard. That has changed! Now even if WordPress is installed in some random directory, if you navigate to http://blog.example.com/wp-login.php you will be redirected to the actual WordPress login page. Convenient, but not helpful when dealing with SPAM bots.
Read more