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.
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.
So do you really think that the only two options are to 1) ignore the person and the topic immediately upon any suspicion, or 2) "throw the hate around" ? Firstly from my POV suspicion is a subjective value judgment based on little evidence. I don't want to be judged that way and I doubt you do, Andersen. If you review even a couple of my responses here I think you will find I was not at all hateful and after the OP amassed sufficient evidence to at least doubt his knowledge and concern for Slackware and made a ghood case for some sort of negative agenda, possibly mere trigger trolling, I ignored OP... not the thread obviously, but the person.
I consider the thread to have value as well as fairly high profile. It demonstrates that most of us here in Slackware Land are not easily triggered, capable of handling dissent and even attacks in an intelligent and gentile manner, and very likely a knowledgeable, informed and helpful community. Isn't that the wisest and best conclusion against trolling?
Hello Tshane - Please allow me to suggest that you examine your choices and attitude for the simple reason that if you surround yourself with only people who defer or who are polite and only polite on your terms by your standards, you risk being surrounded by mediocre (at best) sycophants, and it does "rub off". Please choose carefully.
Eric (AlienBob) can indeed sometimes seem abrasive or dismissive... so what? For starters, He is not likely a product of your environment... much like the differences between Californians and New Yorkers. The man apparently works his ass off and with little reward beyond some gratitude and personal satisfaction. You too might be occasionally short-tempered if you worked so endlessly hard, so productively, and often suffering fools and posers.
You might enjoy a thicker skin... and some tolerance.
Doesn't this official Slackware support forum have its own moderator? Removing unhelpful, rule-breaking, rude, off-topic posts from this let's-all-have-a-party-Beta 1-thread wouldn't hurt...
That my precious ones will fall too, I surely can live with that!
Oh! And Eric's behaviour?
For all that I care, he should have total freedom to express whatever he feels like. If you come unprepared and/or ignorant (as in didn't read the blog), not even God can help you!
But come otherwise, you won't find better, more thorough support anywhere. Period.
...
And Pat? Of course he deserves to be pestered and hunted down!
Considering the enormeous amount of dollars he request for his bug-ridden, half-assed...
Oh!
Wait...
Scratch that!
Pat's "ignore list" must be quite long... or he's way, way more patient than most of us.
I have to disagree : it's seems that's not from scandal but rather from resurrecting your report.
Why ?
You're looking for scandal for much more days than you referred to this report.
It might even be because someone, thinking it worths a fix, pointed it to the BDFL outside this forum.
Pat knows. You don't. :-P
Well, I know what happened. I told the guy in my reply yesterday that this was a valid bug report, but it was buried in 500 pages of requests. Some things fall through the cracks.
So I discussed it with Pat and the others and everyone agreed it was a bug that needed fixing. Pat created a somewhat better fix, but he did credit the guy in the ChangeLog.txt. What better could one wish for.
Bottom line: be patient and if you are not, just repeat your request. What not to do: create a new account and start insulting us for not following up on your bug report.
Actually, this mkinitrd report was the only real bug report from I.G.O.R. I could find in his posting spree during the 3 months in 2020 before his LQ account got suspended because of the hate speech. The rest of his requests are improvement suggestions, and well, they're just that.
Back in my day, we had to go to usenet and brave those flamefests for linux help. Uphill both ways! In the snow! Barefoot! And we LIKED it!
I was on a.o.l.s. a long time before I came over to LinuxQuestions.org.
The Usenet people were mostly a bunch of toxic haters mixed with a disjunct bunch of very gentle people and the resulting diatribes could go in any direction.
I did not like that atmosphere eventually and moved over to this LQ forum where people are mostly civil and helpful, and focus on answering questions about how to use our favorite distro.
There are some people (still there) on a.o.l.s. which I hold in high regard. It's not all bad of course.
Bottom line: be patient and if you are not, just repeat your request.
Regarding those requests, you are kind to explain the team position regarding the Wayland/Plasma5 ?
There are some people (including me) who experimented with it and found ways to improve the Wayland/Plasma5 stability and usability.
And it's about rebuilding of some packages and no major changes, unless we call major changes a daemon thingy which have 200KB as size, a config file and a man file.
However, speaking of myself only, I started to feel like barking at Moon, so I wonder if Slackware has any intention to improve its Wayland/Plasma5 a bit?
That's it? The Slackware 15.0 would be released with the today Wayland/Plasma5 setup which have?
And which is the official way to run the PipeWire daemons on Slackware? I looked really careful on its package and overall on -current, and NO way to run them is specified.
Last edited by ZhaoLin1457; 04-15-2021 at 11:12 AM.
I was on a.o.l.s. a long time before I came over to LinuxQuestions.org.
The Usenet people were mostly a bunch of toxic haters mixed with a disjunct bunch of very gentle people and the resulting diatribes could go in any direction.
I did not like that atmosphere eventually and moved over to this LQ forum where people are mostly civil and helpful, and focus on answering questions about how to use our favorite distro.
There are some people (still there) on a.o.l.s. which I hold in high regard. It's not all bad of course.
I mainly hung out on the alt.rec.arts end of things. I didn't get into Linux until late into my Master's/early on in my doctorate. I'm a late bloomer. By that time usenet was less of a thing than it was. (First time I really touched a computer was college--my high school was too broke to afford computers. I started with Linux in 2000, and switched over completely to it by 2006.)
However, speaking of myself only, I started to feel like barking at Moon, so I wonder if Slackware has any intention to improve its Wayland/Plasma5 a bit?
Wrong thread. You should post it in requests to be sure it will be soon forgotten. And be patient. Patience is virtue which every Slackware user should posses. However I must say with deep regret - some people don't have that virtue. Myself? I am not willing Slackware user. I am cursed to use it. Just nothing works except.
Regarding those requests, you are kind to explain the team position regarding the Wayland/Plasma5 ?
There are some people (including me) who experimented with it and found ways to improve the Wayland/Plasma5 stability and usability.
And it's about rebuilding of some packages and no major changes, unless we call major changes a daemon thingy which have 200KB as size, a config file and a man file.
However, speaking of myself only, I started to feel like barking at Moon, so I wonder if Slackware has any intention to improve its Wayland/Plasma5 a bit?
That's it? The Slackware 15.0 would be released with the today Wayland/Plasma5 setup which have?
And which is the official way to run the PipeWire daemons on Slackware? I looked really careful on its package and overall on -current, and NO way to run them is specified.
No release will be 100% perfect.
To be honest- I pushed Pat to add Wayland support to the 15.0 release to avoid having no way to experiment with it at all for years (until the next stable release).
Wayland is not particularly ready-to-market at the moment but it is getting there. I did address the qt5.SlackBuild changes to improve Wayland support though. Having the Slackware core packages properly built is the most important thing. Configuration is something that does not cost much if you would have to do that yourself after release of 15.0, since you could keep upgrading packages and your configuration would not break.
I think everyone should realize that implementation of requests like this requires extensive research and testing... and testing... and testing. This will only result in a 15.0 release which gets pushed back... and pushed back... just like what has been happenening during the past years.
Wayland session support is not the target of Slackware 15.0 so everything that works when 15.0 gets released is a bonus.
Pipewire support is also something you can document in a Slack Docs Wiki article accompanied by custom add-on packages and configurations. There is no reason for Slackware to have an "official way to run Pipewire daemons" since the main reason for its inclusion was fulfilling a build dependency. The nice thing about Slackware is that you can share your improvements with the community and Slackware readily accepts these without breaking, so everybody is happy.
At this point in time I really only care about functional bug reports. But I am not Pat, he is a thousand time more patient (and reclusive) than I am. I am just a grumpy abrasive arrogant insecure troll.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.