Monday, November 10, 2014

Ifconfig: command not found

CentOS, say it isn't so! Having just done the minimal install of CentOS 7 as a VM, I wanted to install VMware tools. I thought I installed all the prerequisites when the script halted at "Setup is unable to find the "ifconfig" program on your machine."

I ended the script and incredulously ran the ifconfig command, thinking it had to be wrong, but it's no longer included. The ip command has now taken over networking duties, but the VMware script didn't care. I ran yum provides ipconfig, but no love: "No package ifconfig available". A couple of web searches later and I found the package I needed to bring it back...

# yum install net-tools

BTW, don't be surprised if Fedora and RHEL (and it's other offspring) are missing ifconfig as well.

Sunday, November 2, 2014

Developer Cannot Be Confirmed

I bought a new camera recently and decided I needed the "old" version of Photoshop I had lying around on my MacBook so I could salvage pics taken with my n00btastic photo skills. So as any reasonable person would do, I installed and then attempted to update Photoshop with the latest available patch from Adobe.

Finding the correct patch on Adobe's site wasn't exactly intuitive, which is surprising from a company that specializes in making software for the web, anyway I digress. Once the patch was downloaded, it wouldn't install. "AdobePhotoshop12-4-mul-AdobeUpdate.dmg can't be opened because the identity of the developer cannot be confirmed." Seems hard to believe, and I'm not sure who's to blame here, but after some searching it seems there are a number of rather large companies, i.e. Oracle, that have the same issue. (Either devs are signing their apps incorrectly or Apple released a patch/update breaking the previous verification mechanism.)

In any case, if you trust the developer, this can be overruled with a few clicks and your password:

System Preferences > Security & Privacy > General tab and you will see "App in question" was blocked from opening because the identity of the developer cannot be confirmed.

Click the button to allow anyway and enter your password, the app should start installing immediately.

Wednesday, October 8, 2014

Disabling the Yum RHN Plugin

Due to the sheer number of RHEL installs we have on our network it was time to have our own Yum repo. The setup was fairly straightforward and their are many useful articles available.

Once setup and configured, testing began; both the new test systems worked perfectly. But apparently it was too soon to start slapping myself on the back, because systems already registered with RHN would error out once I removed their subscription, rather than use the local repo.

"There was an error communicating with RHN.
RHN Satellite or RHN Classic support will be disabled.
Error communicating with server. The message was:

Error Message:
        Please run rhn_register as root on this client
Error Class Code: 9
Error Class Info: Invalid System Credentials.

I did many an Internet search only to find numerous suggestions that didn't fix the problem. It wasn't until I looked at the man page for yum.conf did I see the answer. The related files portion at the bottom listed a number of other files, the important one under /etc/yum/pluginconf.d the rhnplugin.conf file. Setting it to enabled=0 stops the plugin from being used and voilĂ , the local repo was working. With each of these, I also follow up with a yum clean all just to be sure it's a fresh start.