CentOS

And one more thing to note. Use 32 bit CentOS for that hardware, not a 64 bit.

I did it this way: 1. Booted CentOS Live CD. 2. Partitioned and "formatted" the drive. Mainly the swap partition(s). 3. Immediately mounted them, so that the Live system can use them (installer will not run out of memory). 4. Patched the installer hard-coded memory checks, as it is described on link...

To me it looks like a grub.conf file is corrupted, or is incorrectly read by grub. What is your disk setup? Some huge partitions, LVM .. ?

restorecon, not resorecon

You did not specified which version of Postgre you have ran on Centos 5.6, and how the filesystem was formatted. Generally, this kind of problem is most often due to autovacuum setting or inappropriate memory settings of Postgre. Another reason could be, that on older setup you maybe used filesystem...

The command should rather be:

Thanks, Trevor, I will try it in the future when I will install a vanilla Centos 6.x onto some computer. The strange thing is, that without adjusting anything in the system, the FF 17 can handle a far heavier load, than FF 24 can (on the very same setup). In fact I can't recall having those troubles...

I have a terrible experience with FF 24. I am used to open say 20 tabs and while it is possible on a very old rig with FF 17 (Pentium 3 @ 1 GHz with 0.5 GB RAM) it fails often on a far more modern setup with more memory and many times faster CPU with FF 24. When I ran FF 24 from terminal, I noticed ...

Is there any difference in sshd configuration ? (type of encryption ?) 20% cpu usage by sshd is way high imho. Even 9% is high on a modern powerfull hardware imho.

If you only allow pubkey authentication on a publicly accessible SSH server, then there is no way to log in with just a password. So it is impossible to brute force into such a server. Well, theoretically it is possible to brute force search for a valid pubkey, but this would take so long, that in p...