Basic setup for Red Hat Fedora 14

You CAN use the windows rdp program to connect into Red Hat Fedora 14.  Here is a link to the instructions:

Don’t forget to configure the service to startup during system boot…


You may also need to add yourself to the sudoers file… The setup is simple:

[mirandam@charon ~]$ su Password: <— Enter root password [root@charon mirandam]# chmod +w /etc/sudoers [root@charon mirandam]# echo ‘mirandam ALL=(ALL) NOPASSWD:ALL’ >> /etc/sudoers [root@charon mirandam]# chmod -w /etc/sudoers [root@charon mirandam]# exit



Tivoli Endpoint Manager Software…

download client from:

see when trying to start

Helpful BigFix/QnA Tip: Launching QnA on Linux

Vanilla installs of the BigFix client will include QnA for development and debugging purposes.  But one problem…

if you try to launch it you receive the following error:

qna: error while loading shared libraries: cannot open shared object file: No such file or directory

The way to fix that is to execute the following command…

export LD_LIBRARY_PATH=/opt/BESClient/bin

This will let you launch QnA on several flavors of Linux…
(Tested on CentOS and openSUSE)

Reference (thanks Noah):

Compiling NMap on a fresh install of SuSE 11.0

So, I’m researching the NMAP tool from… and needed to compile it on my various linux test boxes.

suse1:~/nmap # ./configure
checking whether NLS is requested… yes
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking for gcc… no
checking for cc… no
checking for cl.exe… no
configure: error: in `/root/nmap’:
configure: error: no acceptable C compiler found in $PATH
See `config.log’ for more details.

Only problem is they are fresh installations with the minimum of options during the setup of the computers. IE: I went with basic server options with no additional packages during the install of each flavor of Linux.

So where do I go from here… welp, download and compile of course.
In the end I needed 15 different rpm packages from my SuSE DVD… and they needed to be installed in the following order:

1. gmp-4.2.2-30.1.i586.rpm
2. libmpfr1-2.3.1-4.1.i586.rpm
3. cpp43-4.3.1_20080507-6.1.i586.rpm
4. cpp-4.3-39.1.i586.rpm
5. linux-kernel-headers-2.6.25-8.1.noarch.rpm
6. glibc-devel-2.8-14.1.i586.rpm
7. libstdc.43-devel-4.3.1_20080507-6.1.i586.rpm
8. libstdc.43-4.3.1_20080507-6.1.i586.rpm
9. libgomp43-4.3.1_20080507-6.1.i586.rpm
10. libmudflap43-4.3.1_20080507-6.1.i586.rpm
11. gcc43-4.3.1_20080507-6.1.i586.rpm
12. gcc43-c.4.3.1_20080507-6.1.i586.rpm
13. gcc-4.3-39.1.i586.rpm
14. gcc-c.4.3-39.1.i586.rpm
15. make-3.81-103.1.i586.rpm

I’ve posted them at my files webiste

After installing all of these, the remaining installation proceedure outlined on the nmap website went perfectly… I now have a working version on my SuSE 11.0 text box.

CentOS 5 and the BigFix Client

Installing this was a bit more difficult compared to the easy as pie SuSE and the Fedora 14 installs…

Following the instructions for the RedHat install, but downloading the CentOS client from the BigFix website (

Couldn’t get it to start and unlike Fedora 14, I received no indication as to what the problem was…
After solving the Fedora 14 install problem, I figured I’d try the same solution and I was successful…

Using the “setsebool -P allow_execstack 1” command, i was able to get it working finally… see ( for details.

Also reference ( for additional information…

Red Hat Fedora 14 and BigFix Client Software

Finally got the client working on my Fedora 14 test box…

basically following the instructions on the bigfix website:

Ran into a problem with the basic instructions though… a fresh install of Fedora 14 apparently has additional restrictions and would not allow the libBEScrypto library to function properly… i got the following error while attempting to launch the BESClient:

[root@fedora1 BESClient]# /etc/init.d/besclient start Starting BESClient: /opt/BESClient/bin/BESClient: error while loading shared libraries: cannot enable executable stack as shared object requires: Permission denied

As it turns out the solution was simple… and i’m working via the BigFix forum thread ( to explain to me why it worked… but basically to get the client started and working I had to run the following command:

setsebool -P allow_execstack 1

then using the “/etc/init.d/besclient start”, the client started right up…