Shorewall Geek wrote: > > Do you actually know that for certain? Or is what you know is rather > that the Shorewall-perl compiler didn't try to load that module until > after the upgrade? I ask because it could also be that the default @INC > array (which specifies the directories to search when loading Perl > Modules) was 'upgraded' to include /usr/lib/perl5/site_perl/5.8.8 where > it did not previously. The result is the same and it really doesn't > matter a whole lot.
Please pardon me for following up my own post but after I sent this I realized that another possibility is that this library has been used up until the upgrade and that it matches the build/arch of the Perl 5.8.8 that was previously installed. > > Unfortunately, an earlier 'upgrade' rendered my CentOS system unbootable > so I can't attempt to perform a similar upgrade until I find the time to > work through that problem. Apparently the problem I had with CentOS was due to a KVM issue and not with CentOS itself. I'm able to boot up both of my CentOS images but neither of them had anything in site_perl/5.8.8, either before or after I applied all available updates. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
