Fedora Core 4 how-to

[mikeygstl]

To install on Fedora Core 4, follow these simple instructions:

Perform a FC4 install making sure to do the following:

• select no firewall
• select no SELinux
• select custom installation
• in package selection, select minimum install

after you boot into FC4 for the first time, log in as root and perform the following:

• yum update
• ln -s /lib/libcrypto.so.0.9.7f /lib/libcrypto.so.4
• ln -s /lib/libssl.so.0.9.7f /lib/libssl.so.4
• vi /etc/hosts

  make sure the first non-comment line is:

  127.0.0.1 localhost.localdomain localhost

• yum install libidn
• yum install curl
• yum install fetchmail
• yum install gmp
• yum install elinks
• yum install compat-db # <-UPDATED, see footnote 1
• chkconfig sendmail off
• service sendmail stop

use /usr/bin/links (a text browser) to download the FC3 zimbra rpm from www.zimbra.com

extract the .tgz archive
cd into zcs
run install.sh

Everything should go smoothly.

------------------------------

As promised, here are some iptables entries. Keep in mind, these in no way fully protect your system, but should help a bit. These rules will allow remote ssh, http, https, smtp, and remote administration via zimbra interface. Please be aware, your mileage may vary.

iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 25 -j ACCEPT
iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 7070 -j ACCEPT
iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 7071 -j ACCEPT
iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 7075 -j ACCEPT
iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 7443 -j ACCEPT
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A INPUT -s YOUR.INTERFACE.IP.HERE -j ACCEPT
iptables -A INPUT -s 127.0.0.1 -j ACCEPT
iptables -A INPUT -p icmp -m icmp --icmp-type 255 -j ACCEPT
iptables -A INPUT -j REJECT --reject-with icmp-host-prohibited

---------------------------------------------------------------------------------------------------
footnotes:
1 - There is a compatibility issue with the libdb version in FC4. What you must do is downgrade the libdb to the suitable level -or- provide backward compatibility through the compat package.

[onlydarksets]

Thank you! I started to install, but was worried about hosing my existing setup. Maybe I will give it another try now!

[Dijital]

Excellent post, I will have to try this one tomorrow, thanks again.

[johndevine]

Can you tell me how to extract correctly please, not fully used to linux text mode yet

Thanks

JD

[mikeygstl]

Originally Posted by johndevine

Can you tell me how to extract correctly please, not fully used to linux text mode yet

Thanks

JD

No problem:

# extract(x) the compressed(z) file(f) archive
tar -xzf zcs.tgz
# change directory into zcs
cd zcs
# run install.sh from the present working directory (./)
./install.sh



Everything should go smoothly.

[sshgz]

I have installed correctly.
Thank you very much.

But i find the CPU status is 100%,
Who can tell me why?

[mikeygstl]

Originally Posted by sshgz

But i find the CPU status is 100%,
Who can tell me why?

what process is holding the CPU at 100% ?

[marcmac]

run the command "top" - which process is listed as using the entire CPU?

[gzoug]

well, followed all the above steps, on FC4. After "saving config" notice the local configuration starts but never ends: I've got 3000 processes of
"unicode_start" and keep growing... What the heck!
Any hints?

[mikeygstl]

Originally Posted by gzoug

well, followed all the above steps, on FC4. After "saving config" notice the local configuration starts but never ends: I've got 3000 processes of
"unicode_start" and keep growing... What the heck!
Any hints?

I have seen this when installing without editing the /etc/hosts file properly, and also when zimbra is unable to 'find' itself.

I have seen this before. Honestly, I'm not sure what causes it. However, I do know that several threads start up with zimbra, and that I have seen the startup take nearly ten minutes on some systems. You may (ack can't believe I am saying this) want to restart the system and insure that all services come up properly. It will take a while to start - don't get impatient.