When attempting to compile the newest version of S.M.A.R.T. Monitoring Tools on a CentOS Linux server I received an error complaining about the C++ compiler not being able to create executables. In the error output below you can see that the configure script complains of not being able to find a suitable compiler so it errors out.
After a recent Nipper upgrade I received an error when attempting to launch the application. The upgrade was from Nipper 2.1.6 to Nipper 2.1.9 on a Windows 7 Professional 64 bit computer. Below I describe the error in more detail as well as what was done to resolve the error. Nipper Studio is released by Tatania and is used to do network device configuration review including device support for network products from 3com, Alteon Networks, Baracuda Networks, Bay Networks, Blue Coat, Brocade, Check Point, Cisco, Crossbeam, CyberGuard, Dell, Extreme Networks, Fortinet, Foundry Networks, GTA, H3C, HP, IBM, Juniper, McAfee, Microsoft, Netgear, Nokia, Secure Computing, SonicWall, and others.
It is possible to receive an error after updating wpscan via “svn up” complaining about the nokogiri gem. This might be confusing because likely you already have the nokogiri gem installed on Backtrack Linux however it is likely a simple path issue. To resolve you can issue the below gem install –user-install command as shown in the below example.
While getting a Mimo 7″ touchscreen USB monitor working earlier I needed to install some packages however when attempting to do so I received an error. Initially I thought that I had broken something on a system I had just installed BackTrack Linux on however that was not the case. Below I describe the error received in more detail as well as how to resolve the issue.
Earlier tonight while testing the functionality of pbnj including both scanpbnj and outputpbnj on Backtrack Linux I noticed an error with outputpbnj. It appears that during one of the last updates the developer accidentally let a small bug slip by but unfortunately it stops outputpbnj from working at all. The good news is the outputpbnj bug is really easy to fix by remove a couple characters from a single line of the code base. Follow the directions below to get outputpbnj working properly on Backtrack Linux 5 R2.