Central Filesystem Instalaltion
I'm an administrator of a Linux network of over 400+ workstations at a University. In the past I was able to simply go to your site download the latest version of firefox, (nicely without digging through numerous pages), by simply untaring a tar ball into a NFS mounted filesystem like /usr/local. This filesystem then was mounted to every workstation. This simplified doing updates as all I had to do is update it in one location. Though it's a bit difficult digging around I did find your ftp release site where I could download the tar.bz2 x86_64 and i686 releases. Yet it seems that now firefox has deviated from supporting this in the manner that all plugins are installed in /usr/lib64 or /usr/lib (64bit or 32bit). Can you please go back to having a plugins folder inside of the main Firefox install directory or give an environment variable that I can change so that I can point it to a central install location? This mainly effects the java plugin and flash plugin. I understand that flash is about to die off (glad to hear it too) yet maintaining any reasonable size network it is helpful if the installation can be done in /usr/local.
Všetky odpovede (2)
Did you try to create a plugin folder yourself and place symlinks to those plugins in that plugins folder?
If this folder isn't there by default then it doesn't mean that Firefox isn't looking for them.
Note that in future Firefox version you may need to create this folder in the browser folder (other folders like the Firefox icon have moved there too).
It seems that firefox19.0.2 (and now 20) is looking for plugins inside /usr/lib/mozilla/plugins, regardless to the fact the system is a 64bit system. One would have expected that firefox19.0.2 x86_64 binary should look into /usr/lib64/mozilla/plugins but it doesn't.
To resolve my issue I essentially downloaded both the 64bit and 32bit tgz files for firefox 19.0.2.
Next untarred the 64bit version into /usr/local/FirefoxPlugins_x86_64, and untarred the 32bit version into /usr/local/FirefoxPlugins_i686.
Now this is the ugly part (which I really shouldn't have to do):
Delete the folder on every single workstation (400+) called /usr/lib/mozilla or /usr/lib64/mozilla
Next make a soft link from /usr/lib/mozilla to /usr/local/FirefoxPlugins_i686 Next make a soft link from /usr/lib64/mozilla to /usr/local/FirefoxPlugins_x86_64
Why would you delete the Plugins folder from within the browser folder and relocate how firefox looks for the plugins to the local install?
To create a plugin folder inside of central firefox folder I would need to know the syntax of the naming directory convention.
Upravil(a) JasonNaughton dňa