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.
Maybe 32-bit Slackware should switch to i686 instead of i586 by default?
I have been struggling with performance issues with pcsx2 for a long time and decided to investigate again. After asking in irc I was shown this issue.
So I recompiled glibc using alienbob's multilib script changing i586 to i686 and adding '--enable-multi-arch'. In certain slow scenes I saw the fps jump from 20 to 40. I suspect there will be other instances where i686 performs much better than i586.
Pat, when you're ready to start shipping a 5.2 or later kernel, please build it with CONFIG_UNICODE=y. That's needed to mount ext4 filesystems that were created with the casefold feature ("-E encoding=anything"), which is required to support case-insensitive directories ("chattr +F empty_directory"). While you're at it, it would be great if the installer was tweaked to create ext4 filesystems with "-E encoding=utf-8".
Just thinking ahead to when 5.2 or later kernels land in Slackware...
It is good to see that the Linux distro I grew up on back in 1999 (and until around 1993), before switching to FreeBSD, is still alive and kicking. Still using FreeBSD as OSPF routers in our network (all else is now Ubuntu - bless me) but would dearly like to know if a new Slackware release is due any time soon (the last 'version' I used was Slax, and that was for running GCSE exams (in the UK) around five years ago) as I'm looking to finally replace the FreeBSD boxen (despite them being my second love).
Pat, when you're ready to start shipping a 5.2 or later kernel, please build it with CONFIG_UNICODE=y. That's needed to mount ext4 filesystems that were created with the casefold feature ("-E encoding=anything"), which is required to support case-insensitive directories ("chattr +F empty_directory"). While you're at it, it would be great if the installer was tweaked to create ext4 filesystems with "-E encoding=utf-8".
Just thinking ahead to when 5.2 or later kernels land in Slackware...
I don't see Slackware shipping with 5.2 as it is not LTS. I will wager to bet that Slackware 15.0 will be on the 4.19.x series still. The 5.x kernel branch has already gone through 2 subversions(not sure the right term - 5.1 and 5.2) and still no LTS designation, so I also wager to bet no LTS on 5.3 either.
I don't see Slackware shipping with 5.2 as it is not LTS. I will wager to bet that Slackware 15.0 will be on the 4.19.x series still. The 5.x kernel branch has already gone through 2 subversions(not sure the right term - 5.1 and 5.2) and still no LTS designation, so I also wager to bet no LTS on 5.3 either.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
