Originally Posted by franzen

On my 64bit host without multilib, i run a 32bit lxc container to be able to run wine to use a tax app only available as closedsource 32bit, it works fine. No experience with gaming/steam-client.

Originally Posted by Darth Vader

BUT, I will love to stop calling people trolls. I know that's the new trend around is to yell troll to anyone who disagree with you, but from you I have some expectations. As Culture.

Originally Posted by a4z

I said this is my main usecase, read it up, and that I do not care so much about the other use cases, but that there are many reasons why multilib compiler should be default in Slackware. Fits of course not to your trolling, you troll. Now deliver what you are talking about or shut up, because everyone knows now what a big moth and troll you are

Originally Posted by Darth Vader

OK, people, so the incredible and impossible Slackware 32bit operating system with a 64bit kernel, had been incarnated in the form of a VirtualBox virtual machine. Screenshot attached.

It is just a standard full install of Slackware 32-bit excluding KDEI series and usual configuration.

After finishing installation, I replaced the non-smp kernels with the ones from Slackware64, then configured the LILO and reboot.

Sure, there is no possible to build kernel modules, because the lack of a proper x86_64 compiler, as I said in a previous post.

Must be invented some cross-compiling, or maybe used a multi-architecture GCC, with the note that of course GLIBC is no need to be touched. That's why I said that I tested that, it is possible, I had intention to propose that from long time, but I had no time yet to find a minimal invasive solution for building X86_64 kernels and modules from this 32bit operating system.

Long story short, if someone wants to download this virtual machine, just to ask in private, I will export it and in several hours I will send them a link from where can be downloaded. In several hours, because I have something to do meantime.

And again, sorry! But I have no public server at disposition for publicly share it.

BUT, leaving out all [removed] and all that MULTILIB AKBARU! it is trivial to run a full-install 32bit operating system with a 64bit kernel, when we talk about Slackware. IF you already have them and you do not need to build modules, ie. from Slackware64, yet to make a cross-compiler to x86_64 is not so complicated.

Another visible issue is that anything using the UNAME feature believes that's in a 64bit operating system, just like in Slackware64 and Multi-Lib, but that could be fixed using simply /usr/bin/linux32

Something like that started to use Fedora around 10 years ago. It is nothing new.

Originally Posted by a4z

well, if you ignore what was give to you only god can help you, (what is what your signature says) ... you are definitely not just total incompetent but also a troll.
actually admins should stop you from polluting threads like you do, I will not longer fix the shit you write since ... PLONK!

Originally Posted by jakedp

Quit please. It has been shown repeatedly that one can compile 32-bit on Slackware64 by default and it has been shown repeatedly.

Originally Posted by orbea

It has been shown you can cross-compile for 32-bit on Slackware64. It has not been shown you can build 32-bit programs for Slackware64 without multilib. Can you please stop spreading misinformation and derailing the thread?

Originally Posted by jeremy

a4z, I was very clear in post #176. Your posting privileges have been revoked for 24 hours. Please reconsider your posting habits during that time. If you have any questions, do feel free to contact me. Thanks.

--jeremy

Originally Posted by ZhaoLin1457

Permit me to confirm that Slackware 32bit works fine with 64bit kernels from Slackware64, tested in a real machine by replacing the non-smp kernels, just like was described.

And apparently with these 64bit kernels the system feels much faster and responsive, also the test program proposed by OP obtain a better score (if I understand right and a smaller number is better)
Then I think an optional 64bit kernel for Slackware 32bit is a interesting suggestion for improvements.

To be honest, I would like to know more about the possible advantages of using 64bit kernels with a 32bit operating system, and I think that's legit and on-topic if we discuss for real about "the future of 32bit in Slackware", and this thread is not exclusively a campaign for "multilib should be included in Slackware!"

And yes, a cross-compilation toolchain does not scare me, because I used a cross-compiler many times in the past, to compile Android for ARM architecture, from a x86 Fedora box.

About how some people use or abuse terms like "off-topic", "troll" and "FUD", I remember that recently I was myself called troll and blamed to spread FUD in another thread, because I stated that from what I read some KDE-only dependencies maybe will be distributed in l/ series and not in kde/, then several posts later someone else to accept that there are packages like that in l/ even today, and they has no further usefullness if you do not install KDE, but they never was a issue until a certain user questioned that.

Originally Posted by stoffepojken

How come that Darth Vader in every thread is allowed to go off topic and go on with his FUD about plasma 5?

Originally Posted by solarfields

The same reason his nationality has been brought up as an argument against him. Free speech.

Originally Posted by stoffepojken

Romanians are nazis. What they do to the gipsys are apartheid.