Re: [CentOS] CentOS, Firefox, and Java Plugin
On Thu, 2010-09-23 at 00:12 -0500, Barry Brimer wrote: > >> Starting in Firefox 3.6.7 (I think) the (Sun) Java plugin changed names. > >> Here is what it should look like ... > >> > >> $ ls -la /usr/lib/mozilla/plugins/libnpjp2.so > >> lrwxrwxrwx 1 root root 37 Jun 24 19:32 > >> /usr/lib/mozilla/plugins/libnpjp2.so -> > >> /usr/java/latest/lib/i386/libnpjp2.so > >> > >> The plugin name changed .. the old one plugin is still in the jdk, but > >> will silently fail in the browser. > >> > > > > Funny I ahve: amd64 java "Sun" FF 64bit > > libnpjp2.so -> /usr/java/jre1.6.0_21/lib/amd64/libnpjp2.so > > > > and it does not work period. Sun says 64bit plugin works? All my 32 > > bit workstations are fine. > > I only have 32-bit, which is what my example is from. --- Noted... John ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS, Firefox, and Java Plugin
> - the plugin is still working for me, and went smoothly through the I realize that I should have been more precise (and read the OP more carefully): the plugin from the Argeo repo is working for me on x86_64, but I haven't tested it for a while on i386. So it is indeed possible that the Argeo RPM plugin is broken on 32 bit (this is a completely different plugin which is built between i386 and x86_64 since the main plugin was broken on 64 bits) I'll let it know on the list when (if) I find time to work on this again. (interested users/testers/packagers are welcome to show up) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS, Firefox, and Java Plugin
> So it is indeed possible that the Argeo RPM plugin is broken on 32 bit As per http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=405 the old default plugin (which is the one built for 32 bits in Argeo's RPMs) is not supported anymore. The NPP plugin is now the supported version which may explain why the 64bits is still working (more or less) and the 32 bits would be broken. So maybe a simple rebuild based on the existing specs files and using the NPP plugin for 32 bits as well could already give at least basic support (as in 64bits). Using the latest version maybe a bit harder and require more analysis. I'll let you know. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS, Firefox, and Java Plugin
On Sep 22, 2010, at 11:22 PM, Glenn Eychaner wrote: > The latest updates to CentOS 5.5 seem to have broken the Java plugin, > and have defeated any and all attempts to get it working again. > I'm running CentOS 5.5 (32-bit) and Firefox 3.6.9 (installed from the > CentOS repository); I've tried BOTH the openJDK plugin available > through the Argeo repositories, and installing Java 1.6.0 directly > from Sun/Oracle and creating the plugin soft link in /usr/lib/mozilla/plugins. > Neither works at all. Thanks to everyone for their help. It turns out that I had two problems: 1) The page that you get redirected to by the Firefox plugin finder links to these (incorrect) install instructions: http://java.com/en/download/help/linux_install.xml#rpm The correct install instructions can be found at Oracle's website: http://www.oracle.com/technetwork/java/javase/install-linux-rpm-137089.html 2) I was using the Argeo-Plus plugin (32-bit), which appears to be broken. Mathieu, if you get it working again, I'd be happy to use it, but if not, I understand. I was aware that the location had changed (serendipitously), and have the latest version (I've since rolled everything to the Oracle/Sun plugin). Thanks all, -G. -- Glenn Eychaner (geycha...@lco.cl) Telescope Systems Programmer, Las Campanas Observatory ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Disabling IPv6 Auto Configuration
I am using stateless auto configuration for most of my clients. For the servers I prefer to manually assign the address. I have defined the IPv6 address in the ifcfg-eth0 file and set IPV6_AUTOCONF=no. However ifconfig shows both the auto configured and manually assigned address. Looking around I found that net.ipv6.conf.default.accept_ra is set to 1 by default. The ifup-ipv6 is setting net.ipv6.conf.eth0.accept_ra to 0 like it should. From what I can tell the auto configuration is happening right before net.ipv6.conf.eth0.accept_ra is set to 0. If I define net.ipv6.conf.default.accept_ra = 0 in sysctl.conf IPV6_AUTOCONF works as expected for both yes and no settings. Has anybody else noticed this behavior? Ryan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
