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.
I don`t want to sound too emotional but Slackware was the seed of all my knowledge in Linux/Sysadmin/Networking. I was only 16 when I played with slackware 8 and used it as a router (P1 133 MHz) for my small neighborhood ISP. All of my knowledge derives from Slackware. I learned a lot from it. If you can work with Slackware, you can work with every distro and of course, BSD. So..yes. Thank you Patrick for giving me a start in my IT career.
For me too. It was extremely great learning curve. And the reason why I bitch around (some may say troll), that Slackware is dying because of couple of wrong decisions.
The question: why is the distribution needed if you can do everything on your own?
Go ahead and create your own distribution!
A distribution simplifies installing packages onto a system to provide a user a system. It doesn't mean that the user will never need to modify that system. I had to install 14.2 with workarounds because the installer doesn't support NVMe drives. I also upgraded my graphic stack on 14.2 to support newer hardware (mesa, libdrm, llvm, xf86-video-amdgpu, and a few others). I also don't run the stock kernel (currently on a self-compiled 5.10.25) and I have my own versions of freetype, hplip, and nasm.
Make the system your own. If it isn't being done from upstream and you can change it, do it!
Quote:
Originally Posted by ialexand
It is a bad excuse that you could do a workaround on something.
I'm not excusing it, but it is a trivial workaround until it does get fixed.
Quote:
Originally Posted by ialexand
Just imagine. You have a system with LUKS + LVM, initramfs is updated. You then create a snapshot and cannot boot. Do you really think it is ok? Oh, yes, workarounds... booting from livecd and fixing it. That's what regular user expects. Surprises.
Where did I say it's ok for this to remain in the distro? If a severe issue is there, keep reporting until it's fixed. You've been around on this forum long enough to know that there can be a lot of noise (including all 3 threads you created that ended up locked). In knowing there's a lot of noise, you specifically created enough noise that led to your permanent ban with your old account (that you bypassed by creating a new account).
Reports/requests are going to get missed without noise, and with the noise that is sometimes seen in these forums, it increases the chances that some report/request will be missed. If they're important to you, you should continue to report them until they're fixed.
I'm not going to reply to you, because you have 5-10 recorded responses and copy-paste them. Replying to you is like writing something to /dev/null
I don't copy/paste my responses (unless I'm literally copying something from another post to quote). I dare you to find the text I wrote above elsewhere on this forum.
Just imagine. You have a system with LUKS + LVM, initramfs is updated. You then create a snapshot and cannot boot. Do you really think it is ok? Oh, yes, workarounds... booting from livecd and fixing it. That's what regular user expects. Surprises.
What is sad is that through your own arrogance and insecurities, you are attempting to decimate a thread about the Slackware 15.0 beta, one of the most interesting things to happen to the distro and community in years, and make it about you. I take back what I previously said, you are not telling "the truth", you are just seeking attention. Looking at these threads below, you did nothing but berate posters until some of the threads were locked:
This is not about you, this thread should be a celebration of the 15.0 beta. If you cared at all about Slackware - genuinely - you would remove yourself from this board. Nobody cares as much as you about your posts, you are a pollutant to this forum and you should leave.
The best anyone here can do is ignore you.
Last edited by Lysander666; 04-14-2021 at 05:28 PM.
You do not know how to spell. I would appreciate it if this thread could get back on topic and discuss Slackware 15.0 Beta 1.
Let's report bugs so that Mr. Volkerding can get us closer to 15.0.
What is sad is that through your own arrogance and insecurities, you are attempting to decimate a thread about the Slackware 15.0 beta, one of the most interesting things to happen to the distro and community in years, and make it about you. I take back what I previously said, you are not telling "the truth", you are just seeking attention. Looking at these threads below, you did nothing but berate posters until some of the threads were locked:
This is not about you, this thread should be a celebration of the 15.0 beta. If you cared at all about Slackware - genuinely - you would remove yourself from this board. Nobody cares as much as you about your posts, you are a pollutant to this forum and you should leave.
The best anyone here can do is ignore you.
Calling common sense as arrogance is kind of weird. I will remind you this post in a year when you are still waiting for 15.0
Alternative: 15.0 can be released soon and will be a garbage.
You do not know how to spell. I would appreciate it if this thread could get back on topic and discuss Slackware 15.0 Beta 1.
Let's report bugs so that Mr. Volkerding can get us closer to 15.0.
He doesn't give a 'any interest' to that. He even didn't change setup program to accomodate modern laptops (I could be wrong, but most likely mini iso won't work with wireless interface only laptops).
What is sad is that through your own arrogance and insecurities, you are attempting to decimate a thread about the Slackware 15.0 beta, one of the most interesting things to happen to the distro and community in years, and make it about you. I take back what I previously said, you are not telling "the truth", you are just seeking attention. Looking at these threads below, you did nothing but berate posters until some of the threads were locked:
This is not about you, this thread should be a celebration of the 15.0 beta. If you cared at all about Slackware - genuinely - you would remove yourself from this board. Nobody cares as much as you about your posts, you are a pollutant to this forum and you should leave.
The best anyone here can do is ignore you.
You've "investigated" my banned account. You have a lot of time I should say. I'm just trying to imagine myself looking into the history of some old account.
...which means that for some reason, Samba is still being built against MIT Kerberos, which again means that using Samba as a Domain Controller will not work.
(It's weird, because the Samba SlackBuild script doesn't specify "--with-mit-krb5", so one would think the build script would fall back to using embedded Heimdal libraries, but it seems to detect MIT Kerberos and use that instead. To make matters worse, there seems to be no build option to force it to use embedded Heimdal.)
...which means that for some reason, Samba is still being built against MIT Kerberos, which again means that using Samba as a Domain Controller will not work.
(It's weird, because the Samba SlackBuild script doesn't specify "--with-mit-krb5", so one would think the build script would fall back to using embedded Heimdal libraries, but it seems to detect MIT Kerberos and use that instead. To make matters worse, there seems to be no build option to force it to use embedded Heimdal.)
...which means that for some reason, Samba is still being built against MIT Kerberos, which again means that using Samba as a Domain Controller will not work.
(It's weird, because the Samba SlackBuild script doesn't specify "--with-mit-krb5", so one would think the build script would fall back to using embedded Heimdal libraries, but it seems to detect MIT Kerberos and use that instead. To make matters worse, there seems to be no build option to force it to use embedded Heimdal.)
Sounds like a SAMBA bug to me? but I honestly, just did a little searching around; and I found this:
Quote:
Originally Posted by https://wiki.samba.org/index.php/Running_a_Samba_AD_DC_with_MIT_Kerberos_KDC
Building Samba with MIT Kerberos Support
To enable MIT Kerberos support when you build Samba:
Install the MIT Kerberos 1.15.1 or later server and header files. For details, see Package Dependencies Required to Build Samba.
Pass the --with-system-mitkrb5 --with-experimental-mit-ad-dc option to the configure script when you build Samba. For further details on building Samba, see Build Samba from Source.
If you read the rest of the page, you'll see its highly unlikely, that they would design SAMBA to auto compile against Kerberos. I'm sure its possible something else might be the cause here; but I place my bets on it being a SAMBA bug? or some kind of user / config error?
Quote:
Originally Posted by https://slackware.nl/slackware/slackware64-current/source/n/samba/samba.SlackBuild
# Choose correct options depending on whether PAM is installed:
if [ -L /lib${LIBDIRSUFFIX}/libpam.so.? ]; then
PAM_OPTIONS="--with-pam --with-pammodulesdir=/lib${LIBDIRSUFFIX}/security --with-system-mitkrb5 --with-experimental-mit-ad-dc"
unset SHADOW_OPTIONS
else
unset PAM_OPTIONS
SHADOW_OPTIONS="--without-pam"
fi
Last edited by khronosschoty; 04-14-2021 at 07:29 PM.
Obvious to whom? Isn't that a subjective value judgment? If viewed as welcome activity and an opportunity to extol and demonstate one's virtues it looks like "making lemonade out of lemons" to me.
If you owned a store that experienced zero shoplifting, it is likely your store also has zero or at least very low sales. Demand is an essential part of of what is valued. Supply is not enough on it's own. If a thing is highly valued, highly in demand, by nature it will also be attacked, stolen, vilified, etc as well as sought after.
I can't recall if it was actually Bill Gates, but some top level memo revealed that it was Microsoft's policy that "if an OS is going to be pirated, we want it to be ours". Seems that attitude has served them well.
If one goes through life never upsetting anyone, it is unlikely that person did anything of any impact or influence. Things are rarely so simple as to be all good or all bad, or even objectively good or bad. They are all package deals subjectively evaluated.
To whom? I would say to pretty much everyone here. It's not about the critique, a constructive critique can be very useful. This, however, doesn't look like that. And with that attitude, the way of communication.. it is obvious.
Regarding the store example.. If you don't like the product, you can complain. If that doesn't work and the boss just won't listen, then go somewhere else, buy what you think is good for you, don't stand at the door endlessly, throwing the hate around.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
