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.
Mr. Volkerding, how about building the x86_64 kernels with CONFIG_IA32_EMULATION=n ? It seems that in big houses this is considered an important security measure.
sorry about my curiosity, but where this happens and why?
Yes, this is true, Slamd64 was an unofficial x86_64 port of Slackware. But with Slamd64 there was a single source of security updates which worked out of the box without breaking anything. Today, official Slackware64 security updates might break your alien multilib installation.
regards Henrik
Then, be my guest to use Slamd64 if you appreciate it so much. I guess they need users too.
Anyway, while these old times, there was also BlueWhite64 which was a pure 64bit port of Slackware on x86_64. So, our BDFL had the possibility to compare practically both the Multilib and pure 64bit variants of Slackware.
BTW, I truly believe that still raising Multilib issue on -requests thread is straight on: silly. Have a bit of shame, my friend!
While these silly Multilib Wars (already mentioned by ZhaoLin1457) was clearly stated by our BDFL that the Slackware64 will NEVER be Multilib even after an eventual abandon of 32bit Slackware and Mr. Hameleers clearly stated that he will STOP maintaining Multilib IF the 32bit Slackware will be abandoned.
For what is worth, these silly Multilib Wars, with dozens of Mega-Threads where a bunch of angry All-Knowing Men jumped on Darth Vader's throat for defending The Obvious, had a single result: this community losing some valuable members. Years later, Slackware64 is still pure 64bit.
Last edited by LuckyCyborg; 05-01-2024 at 09:27 AM.
I personally think that Multilib is a whim, not a necessity. I have never used Multilib. What is it good for?
I like being able to use my printer that requires a 32-bit only driver.
Quote:
Mr. Volkerding, how about building the x86_64 kernels with CONFIG_IA32_EMULATION=n ? It seems that in big houses this is considered an important security measure.
Distributions would like to reduce their attack surface as much as
possible but at the same time they'd want to retain flexibility to cater
to a variety of legacy software. This stems from the conjecture that
compat layer is likely rarely tested and could have latent security
bugs.
I like being able to use my printer that requires a 32-bit only driver.
Then use an operating system appropriate to your hardware or buy hardware compatible with the 64bit operating systems.
Excuse me, but I do NOT think that the hardware compatibility is an "excuse" here.
After all, there are tons of hardware incompatible with the 64bit Linux. And I talk here not only about printers, but about entire computers built around Intel Pentium II, Pentium III and even many Pentium IV on socket 775, which by grace of Intel are 32bit only. Heck, even I, I have a computer which has a nice 8GB DDR3 memories, SATA 2.0 ports and all shiny features which you expect, BUT it can run only Slackware i586 because its Intel Pentium IV 530 processor at 3GHz on socket 775.
Last edited by LuckyCyborg; 05-01-2024 at 08:52 AM.
Aah - The Microsoft position. Want the latest software? Buy the latest hardware.
So, the "Reductio ad Microsoftum" is the new "Reductio ad Hitlerum" ?
I for one, I talked about the user duty to use compatible hardware and software. The said hardware is not necessarily to be "newer" but "compatible" with the operating system you use. Or vice-versa - the said operating system to be compatible with the hardware you use.
Excuse me of not being impressed by your printer issues, when I know that entire computers are incompatible with 64bit operating systems, even these boxes are decently modern. Even myself I own several computers like this - please be kind to read also the last paragraph from my previous post.
Last edited by LuckyCyborg; 05-01-2024 at 10:31 AM.
how about building the x86_64 kernels with CONFIG_IA32_EMULATION=n ?
The latest stable kernel (6.7 and newer) allows build time CONFIG_IA32_EMULATION=y and CONFIG_IA32_EMULATION_DEFAULT_DISABLED=y. Adding a boot time kernel parameter ia32_emulation=true allows loading 32-bit programs and executing 32-bit syscalls for those who need multilib.
Please, can we have a check on power saving as we're going through the upgrades? I'm going to have to start digging here because this apparently wasn't done. It would be lovely if these things landed jammy side up instead of jammy side down.
Please, can we have a check on power saving as we're going through the upgrades? I'm going to have to start digging here because this apparently wasn't done. It would be lovely if these things landed jammy side up instead of jammy side down.
I personally think that Multilib is a whim, not a necessity. I have never used Multilib. What is it good for?
Feel free not to use it if you don't like it, but please don't come with suggestions that would prevent everyone else from using it.
During the years I have used the multilib for many things including running 32 bit Windows programs in Wine and looking at pdf files containing 3D-models with Acrobat Reader. I do not use multilib every day, but every now and then it is really useful.
BTW, I truly believe that still raising Multilib issue on -requests thread is straight on: silly. Have a bit of shame, my friend!
Shame on you for putting words in my mouth :-) . I have not for a very long time suggested that Slackware64 should be multilib out of the box. As a reply to a request about modifying upgradepkg I only noted the difficulties doing so and mentioned that the problems it would solve would be a non-problem if Slackware64 would have been multilib out of the box.
That said, I would not mind if Slackware64 became multilib out of the box as it would allow Slackware to run more software without the problems of todays third party multilib addition. But the significance of multilib might not be as big as it once were. If I understand things right newer versions of Wine might be capable of running 32 bit Windows programs without multilib and the 32 bit Linux applications are becoming more rare and obsolete.
IME, 32 bit linux applications without source code or a 64bit binary are vanishingly rare, if they exist. The only ones I know of were from the Adobe stable( Flash & pdf reader?). Good luck with them!
Wine ≥9.0 doesn't (or shouldn't) need Multilib. Much of the Multilib structure seemed to me for devs compiling 32bit on a 64bit box, and the accompanying text often reflected that. Developers are not the standard use case for Slackware. I hasten to add I'm no coder. But I have never run 32dev.sh to set up the 32bit environment in ≥12(?) years of multilib usage. AFAIK, our BDFL never accepted Multilib on the install disk.
So once the 9.0 release of wine comes along, I for one will ditch Multilib. Fred Emmot's slamd64-12.2 integrated 32bit in the 64bit builds. I also feel the 4.7GB of a dvd is an artificial limit, unless dvds are sold. If they are, you can eliminate:
/usr/doc/*
The HOWTOs (or links to them)
Insert Links instead of the source code
Put them up on the website. Indeed the info pages should be referenced online also, as info pages have the poorest ratio of verbiage to usable information. The only people more verbose than an idle academic are the legal profession. Phraseology in legal use dates back to when scribes were paid by the word. So "Now, or at any point in time..." = "Now", except your reward for writing the former is greater.
Last edited by business_kid; 05-01-2024 at 01:24 PM.
Developers are not the standard use case for Slackware.
I would disagree on that one. Slackware is a very good distribution for developers as it has a lot of nice libraries and don't separate those libraries in "standard packages" and "developer packages". I am also very happy with the fact that valgrind will be included out of the box in the next upcoming Slackware release. Valgrind is an example of a tool mostly used by developers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.