Firefox Quantum
Posted: 24 Feb 2018, 05:25
Rerunning update-firefox should overlay what's in the /tmp directory. Accessing the /tmp directory as root should allow you to delete what's in the /tmp directory.
Locked in /tmp, even for root?yldouright wrote: ↑24 Feb 2018, 02:05If you do the "update-firefox" command and incorrectly download the server version, how do you remove it? It's locked in the /tmp directory.
... CheersFirefox was for many years, like most browsers, a good way to both create and read .mht and mhtml files. Mozilla Firefox previously required an extension to be installed to read and write MHT files. Two extensions were freely available, Mozilla Archive Format and UnMHT. Both were rendered non-installable with the advent of "Firefox Quantum" version 57. (Also, neither of them ever implemented support for multi-process mode.)
With the advent of "Quantum" (the version 57 update in late 2017) those extensions, which allowed Firefox to read or write mht & mhtml files no longer were compatible with Firefox. As of 2018 none of these extensions have been updated to function with the Quantum style Firefox browser.
Although Firefox did not (as of version 56) include support for MHTML without the use of add-ons, there was source code available for viewing MHTML files within the related Thunderbird project, indicating that future support in Mozilla software such as Firefox could become available without such add-ons. But as of 2018 it appears unlikely, and Firefox can no longer support writing or reading .mht or .mhtml files due to lack of any working extension.
No.yldouright wrote: ↑27 Feb 2018, 01:56When you run the command "update-firefox" and it asks you if you would like to "build" the latest version (v.59), are they asking me to make the module manually
If you're referring to sesm.sh, no.Does your script allow other depositories not normally associated with Porteus?
No idea. Deactivating, then renaming it's .xzm to something else, like xyzm for example, then rebooting would be an option to ensure it's totally gone.yldouright wrote: ↑27 Feb 2018, 12:43Would this persistence have continued if I had deleted the v.57 instead of just deactivating it as I did?