>Hi Jerry,
>
>I restored my postgres databases/tables this morning. Guess what. I'm having trouble connecting to postgres outside the local network. I went back and read the pg_hba.conf file and it has some lines that can be comment out dealing with SSL. It also say something like if SSL has been built into your kernal. I'm thinking SSL may come compiled in the the Redhat kernal that is installed from the CDs. I think I would like to try and compile a new kernal and see if I can eliminate SSL.
>
>I'm making a mirrow image backup right now just in case. I have the readme file that explain how to build a new kernal. Looks like Redhat has changed some of the paths.

Here is a URL of the method I use that gives you the ability to boot more than one kernel. So, you can keep your current kernel, compile another, including the initrd and system.map, and the modules for it, without harming the originals or any others. Works very nice!
http://www.linuxgazette.com/issue68/ghosh.html
(Note: he uses "make xconfig" to run the x version. I prefer make menuconfig, which is the ncurses version, but easier to use. SuSE has a kernel configurator option in YaST2, and I'd suppose that RH may have something similar, which would be used instead of "make menuconfig". ??? But, configuring the kernel is easy to do. I've done it dozens of times over the last 5 year just playing around. I have had only one compile fail. I went back to menuconfig and turned off the feature that didn't compile and everything worked ok.


>
>I'm currently using the Grub loader to boot Linux. It seems like there was a thread on this some time back where grub or lilo might cause problems in a dual boot system.

I am currently using grub. Here is a useful howto
http://www.tldp.org/HOWTO/Linux+Win9x+Grub-HOWTO/
GRub can lie about where Windows boot partition is, and it can lie about where the /boot is, too. Mandrake 8.2 uses grub and I defaulted to it. They seem similar but work differently. GRub's primary mission is to allow the installation of Linux on a box that already has a Window's partion. If you run lilo on a box with WinXX on it lilo will overwrite the MBR and you will loose your ability to boot into WinXX if you haven't included it's partition in lilo.conf. You can undo a lilo install with "/sbin/lilo -u", and if for some reason your WinXX HD won't boot you can boot a bootable dos floppy and do "fdisk MBR" to restore the MBR.



>The readme file on building the a new kernal assumes I'm using the lilo loader to boot. I would like to go back to lilo so I can follow the instruction in the Readme file. Do you know if I do the following command it will write a new master boot record and default back to using lilo to perform the dual boot or is there something else I need to do to restore lilo as the default boot loader?
>
>/sbin/lilo

lilo is the command that causes the /etc/lilo.conf configuration file to be used as a template for the MBR, so make sure you have /etc/lilo.conf configured the way you want it before you run lilo.


>
>Thanks
>
>Jerry,
>
>Never mind. I check /etc for lilo.conf and it was not there. I also did a search of the entire partition and no lilo.conf. Then I remembered that I could create a new Linux Loader by running an update off the distribution CD. The upgrade install now has a separate window addressing this issue, so I can choose which loader I want to use or whether to install new, update, or no loader, etc.
>
>If you know of any issues with lilo or grub and a dual boot system, let me know.

Grub would be the one you want to use if you are going to be in a dual boot situation with WinXX and Linux, and WinXX was previously installed.
JLK
>
>Thanks