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.
No, I'm suggesting it's good enough to be included as a default software
I'm with dugan on this one. I've used a dwm/dmenu based environment for several years and I'm a big fan of it, but as shipped in its default configuration I found dwm quite horrible. If nothing else one will want to change dwm's MODKEY to Mod4 else it's hotkeys clash with practically everything. Then there's all the aesthetics such as colours and fonts and the other key/mouse bindings to tune to one's preferences.
I suppose a group of us could get together and come up with a definitive set of patches/config for some sort of 'Suckless on Slackware' project which Pat could potentially adopt in future, but getting agreement on what it should include would be difficult as everyone tends to have their own idea about that and I doubt it would look anything like what upstream ship by the time we were done.
Would anyone here have any objections to a jail program for slackware like firejail or if you have a better one to suggest because a jail/sandbox/virtualize program slackware should have out of the box to isolate any program that you don't fully trust. Before someone suggests chroot it was never intended to be a security program and is trivial for a program to escape if it's root or knows what it is doing https://firejail.wordpress.com/ https://firejail.wordpress.com/download-2/
Also before I forget, pat when firefox updates to ESR 60 in like 3 weeks could you please jump straight to ESR 60? Many extensions only work with 56+ now and I'm trying to stay on 52 for as long as possible but my patience is reaching thin with how many I can use because they're either abandoned if they work or don't work.
Also before I forget, pat when firefox updates to ESR 60 in like 3 weeks could you please jump straight to ESR 60? Many extensions only work with 56+ now and I'm trying to stay on 52 for as long as possible but my patience is reaching thin with how many I can use because they're either abandoned if they work or don't work.
moving to the newer firefox ESR in Slackware 14.2 will be difficult as firefox requires rust to build from version 54.x on and this compiler is not available in stable: it would be the first time that I witness such a backport...
moving to the newer firefox ESR in Slackware 14.2 will be difficult as firefox requires rust to build from version 54.x on and this compiler is not available in stable: it would be the first time that I witness such a backport...
So what does this mean? Will pat give the rust compiler to stable before slackware 15.0 or will he have to release slackware 15.0 this summer before ESR 52 dies?
Take a look at 14.1, its still supported and has mozilla-firefox-45.9.0esr.
On older releases there is less of an expectation for latest versions of software and security patches. You expect the latest slackware release (currently 14.2) to have the latest patches which either pat will have to backport the rust compiler to 14.2 before this fall when 52.x dies or he'll have to release 15.0 this summer before 52.x dies
I think there is a third choice, continue using the 52 esr release until the security issues are too great to deal with. I'm sure Pat will weigh the options when the time comes and come up with the best choice.
Many extensions only work with 56+ now and I'm trying to stay on 52 for as long as possible but my patience is reaching thin with how many I can use because they're either abandoned if they work or don't work.
You can use Ruari's latest-firefox script to fetch upstream binaries of any firefox version and repackage them as Slackware packages. At least 59.0.2 works fine in Slackware 14.2.
You can use Ruari's latest-firefox script to fetch upstream binaries of any firefox version and repackage them as Slackware packages. At least 59.0.2 works fine in Slackware 14.2.
On older releases there is less of an expectation for latest versions of software and security patches. You expect the latest slackware release (currently 14.2) to have the latest patches which either pat will have to backport the rust compiler to 14.2 before this fall when 52.x dies or he'll have to release 15.0 this summer before 52.x dies
At a push, Pat could repackage the Firefox binaries. This was done in the past
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.