I ran bastille already but i still think it needs more hardening.

The services i am running are..


Snort
Mysql
Apache


it is still using X, and i nede to harden this system some more

Did you read post #1 of the 1st thread in this forum about links wrt hardening?

yes i did, and the only link there is about hardening RH9 is bastille, which i have already ran like i said it in my post

OUT OF THE WAY DUMB QUESTIONS COMING THROUGH!!!

What do you mean by hardening?

Maybe you want to take a look at

Linux Intrusion Detection System
www.lids.org

I don't know your experience with Linux, but this most certainly hardens your system..

hardening.. errr... securing the system, turning off services, etc ,etc

yes i did, and the only link there is about hardening RH9 is bastille, which i have already ran like i said it in my post

When I asked you to read the first post I didn't mean reading about Bastille and using that alone. You should read the checklists and securing part.

Let's give you a quick run-tru of the main points.
I. Remove any user software, network daemons you have no immediate need for *NOW*. That includes everything in the "hmm, (whats that?|sounds interesting)" and "I'm sure gonna use/need that later on" categories: if you need it later, install it at that time.
Common pitfalls are for instance the MTA: you don't need Sendmail, postfix or exim running to send email, and you dont need DNS (BIND, named) running to *access* your ISPs DNS servers.
II. For network services you need to provide and network daemons you need yourself, place access restrictions in 1. the applications configuration files, 2. tcp wrappers and 3. the firewall.
If the service is run from (x)indetd, see /etc/(x)indet.d for configuration files.
Restart all services and check for services in the LISTENING state with "socklist", "netstat -anp" or "lsof -i".
III. Use a restrictive default firewall policy of DENY. This means you will have to add explicit rules for any serve you need access to, or provide, but doesn't allow access when rogue services are started.
IV. When you installed Linux, you should have installed a filesystem integrity checker like Aide, Samhain or tripwire. Relying on the rpm database to validate your system does not provide sufficient coverage.
V. Prevent malicious local/network activities and privilege escalation by patching your kernel with the Grsecurity(.net) patches and configure your system for it.
VI. Use sufficiently strong passwords. Restrict local user access using /etc/securetty (root access), login.defs, PAM (also see /etc/security) and the shell resource files. Set proper ulimits.
VII. If network-facing daemons can be configured to drop root privileges and run as a lesser-privileged user, configure them so.
VIII. Have the discipline to update your system regularly, especially if an application is found vulnerable. Putting it off will make your system a liability for all who use the network, the internet.
IX. /*can I do that? or do I use VIIII?*/
Have the discipline to regularly run local system checkers like Tiger, COPS, Lsat, Chkrootkit and monitor your logs and act on anomalies.

*Please note this list aint complete. Please read the checklists and securing part. *Then* try to ask more specific questions.

HTH