SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Sat Nov 15 18:33:27 CST 2008
xap/mozilla-firefox-3.0.4-i686-1.tgz:
Upgraded to firefox-3.0.4.
This fixes some security issues:
For more information, see: http://www.mozilla.org/security/know...firefox30.html
(* Security fix *)
If one upgrades beyond 12.1, it will appear in the next slackware version.
But, I don't know if we'll see firefox 3.0 for the 12.1 stable or not.
I've been using Firefox 3.* for quite some time now, without any problems.
Used the SlackBuild script from Slacky-eu, you only have to adjust the version number.
There is a new FF out now (3.1), which has a "porno button" (still beta!).
Firefox is a binary package in Slackware, it isn't compiled against any other software or shared libraries in the system. That means that you can use the 12.2 Firefox packages on older Slackware releases without any problems (within reason, say Slackware 10 onwards).
You could always just use the binary release from the Firefox site too. The Slackware FF package is just the official binary release repackaged.
I've been using Firefox 3.* for quite some time now, without any problems.
Used the SlackBuild script from Slacky-eu, you only have to adjust the version number.
Why would you use the SlackBuild from slacky.eu rather than the SlackBuild that comes with Slackware itself?
Why would you use the SlackBuild from slacky.eu rather than the SlackBuild that comes with Slackware itself?
Brian
No particular reason, Pat's SlackBuild script is fine too (naturally).
It's also possible to just unpack the binary and make a symlink for the plugins and that's fine too.
Whatever floats your boat.
Firefox is a binary package in Slackware, it isn't compiled against any other software or shared libraries in the system. That means that you can use the 12.2 Firefox packages on older Slackware releases without any problems (within reason, say Slackware 10 onwards).
Doesn't doing this cause the problem people reported with mailto links not opening Thunderbird? Has that been fixed?
I can empathize. Recently I posted my thoughts about updating to 3.0.4 in preparation for 12.2.
I agree that there has been no real improvement between FF 2.0 and 3.0, except maybe some added bloat. They cannot force me to switch, I'll switch when I want, when they fix many of the strange bugs. And if they don't, guess I'll have to look for a new browser if sites complain.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.