Hello. I'm new both to this website, and to the world of Linux. I have a DOS background that I've enjoyed so that helps, but I do have some questions as I learn more about Linux and web hosting. I hope you'll endulge me with this.

1. I am running FC4 (Fedora Core 4). I recently tried to upgrade the Apache httpd server, but Fedora still only recognized the version that came with FC4. Where are all the files and directories located for Apache to make the new upgrade visible and operational??

2. To make it easier for this "newbie" to get setup and operational, I loaded FC4 with the GNOME desktop which set the default runlevel at 5. Once I get all the settings squared away, how do I change the default runlevel to 3?? I thought I did once by changing it in the inittab file, but it still wants to boot into the desktop. I understand that cPanel will not work with the x-system running, and I'm assuming other control panels are the same way.

3. Does anyone know if zPanel will work with FC4 or FC5? Their website claims they only support FC2 but I'm wondering if anyone has had success with it while running FC4 or FC5. I would prefer to run cPanel, but until I can really afford it I want to run something in the meantime, and I understand that zPanel is the best (free) and closest to cPanel. Any thoughts?

Thanks for your help. I will greatly appreciate it!!!

1. How did you upgrade using source or RPM? If rpm compiled for fedora then it should work fine but may require a reboot or stopping and restarting the Apache service. If from source then it might have installed where a default source is installed. The old precompiled version of Apache that was installed may have been customed configured and its files may be in a different location. Normally Apache starts with the command ' service httpd start ' and maybe the new /etc/init.d/httpd is still the old from the the orginal install. If I use rpm based software then I would upgrade using rpm based software. If changing to source code building then remove the rpm before installing. Reason is if you use a tool like yum or apt to apply updates then you will overwrite your newer compiled install even though the rpm is newer but still older the compiled version. Confusing isn't it.

2. You need to edit /etc/inittab file and change the line.
id:5:initdefault:
to
id:3:initdefault:

3. Do not know what zPanel is so can't help. But I see no issues if it runned under FC2. Only thing is as long as that version works with fc2 then should work with fc4 or fc5. Only thing is if Your install is missing some rpm's based on your install. If you installed everything I would say it should work with no issues. If a selective install then you might need to install additional needed librairy or application RPMS from the CD.
Do a search at rpm.pbone.net to see if there are any rpms for zPanel.

Hello.

Thank you. I upgraded using source since I was unable to locate a RPM for the latest version of Apache HTTP. The website you referred me to had one and for that I am grateful.

Also, I already did as you said for editing the inittab file, and that didn't work so I figured there were more files to modify to make it work right.

As for zPanel, what can I say. I've gone back to looking at other control panels for web hosting and I'll see what I can come up with.

Again, thank you, and if you have anything else that could be of help to me that would be greatly appreciated.

Not sure what else it can be for the inittab worked for my setup. Not sure if there is something in /etc/rc.local or maybe a service in /etc/init.d.

Brian1

/etc/inittab should do it. Check it again to make sure it is 3 when you get in your GUI - make sure it is saving. You could also try your ALT+F2 or ALT+F3 options to get to another promt. Or open up a terminal and type 'init 3' to get to the basic runlevel to make sure everything is happy. ('init 5' will get back to the GUI.

May I ask why you are trying to upgrade Apache?

J

Okay. I'll try that again, thanks. Also, in regards to upgrading the Apache I understood it was best to keep those updated with the most recent "stable" versions as they become available. Is that not the case????

Again, thanks for the help!

No. If it aint broke, don't fix it.

Only update if it's usefull. If it's for home use, don't bother unless there are new functionalities that you really need. If it's a real webserver (connected to the internet and accessible by the whole world), just update when security is involved or (again) when there are new functionalities that you really need.

Updating involves testing as you have to make sure that it all still works. Proper testing takes time.

Okay. Thanks for the input. No sense doing something that isn't necessary. Again, thanks.