This is what I've done to get it working on Fedora (I forget the exact kernel version). Don't know if this will work for you but it's here if you want to try.
1) Turned off SELinux because it was preventing some shared library activity required by bpcd. You have the option of running Security Enhanced Linux on Fedora but it's very paranoid and makes it hard to do a lot of things. So, we turned it off. Here's how: -Edit the /etc/selinux/config file and set the SELINUX variable to "disabled" -Rebooted the server (required to have this change take effect) 2) Ran the iptables commands to allow NBU servers access but I used the IP address of the master/media server instead of the hostname. 3) Then ran this to save the new iptables rules: # /sbin/service iptables save 4) Restarted xinetd /etc/init.d/xinetd restart Then we could access the client via NBU. ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Wednesday, February 21, 2007 14:15 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Redhat or Fedora 2.6 kernel NB 5.1? Before anyone says it - I know none of the 2.6 kernels for RH/FC are in the compatibility matrix. My question is despite the above has anyone got it successfully working on either Redhat or Fedora Core version 4 or higher with the 2.6 kernel? If so would you be willing to share how you got it going or at least the xinetd changes you made for it? It seems I saw a thread about this some time ago but I can't find it in the archives. By the way - is there a way to search the archives for keywords? The page I went to just gives me the archives by month so I have to open each one and even then I can only search on the thread titles.
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu