YES, i know ff 67.0 is not ESR. But, inevitably these changes will come down
the pike, and i'm having a bit of trouble finding useful info.
First: The "Profile per Install" really screws me up, as i have an NFS shared
linux environment where users get firefox via /usr/local/firefox which is a
symbolic link to /usr/local/firefox-{version} (e.g. firefox-67.0). I use
autofs automounter also, but the resolved-realpath changes for every release,
and so the code is going to "help me out" by generating a spankin' new Profile
for all my users all the time. That's entirely untenable. I've updated bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1528082
asking for something more than a proposed Environment Variable (hopefully
mozilla.cfg admin pref) to keep this from happening.
Second: Al l(or at least many) of my mozilla.cfg "defaultPref()" values now
seem to be "LOCKED" in about:config. (what the?!)
Did something change in the autoconfig world intentionally or accidentally?
there's a very good reason to defaultPref() to set desired values w/o being
hostile to my user-base and letting them change if they really need/want to.
If that functionality is being designed away, then i have to figure out some
other way to deal with this.
Any clues/guidance/pointers highly appreciated.
thanks,
--stephen
--
Stephen Dowdy - Systems Administrator - NCAR/RAL
303.497.2869 - [email protected] - http://www.ral.ucar.edu/~sdowdy/
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
[email protected] with a subject of "unsubscribe"
