Slack Community call

It came to my worries that a lot of threads currently in the forum here becomes very emotional because of software stand of point.

We as community should act upon this together, and find the proper solution.
I will make a solution/proposal for this.

Currently there is a lot of debate about testing different kinds of inits in Slackware.
we basically could make 4 forks in doing so.
Why not work together and combine our talents into a bleeding edge slack. basically a similar model as fedora is to red hat.

so, why not have the community test these things, make their decision and help us all and especially PV to adept other things into Slackware. we basically decide if something is stable and proven stable. PV is basically the person that says that the little piece you are working on, is stable enough for the whole Slackware OS.

the following projects could work together.
eudev for slackware
systemd for slackware
I think we have someone working on RUnit for slackware.
Also the installer internationalization project.
and people are talking about wayland vs. X11


What do people think about this ?
Should we have everyone together on this,
this is not just Sbo pkg, it would be the dev/bleeding edge OS of Slackware.
do not compare it with -current.

the OS would be based on every Slackware release, with our packages / scripts we could make testing releases, help each other in improving things that will find its way into Slackware.

No thanks, that's basically asking me to help me screw myself. systemd has already forced me to read more incomplete documentation to *not* find an answer than I ever had to do under the old init system. So now I'm being called to frustrate myself yet more in the hope of keeping the old init system as an option. No.

Pat's more than welcome to throw the old init into /pasture and give reliable instructions on how to switch it in and still get to single-user mode. I don't need a full set of scripts, just /etc/inittab, minimal rc.S, minimal rc.M, example rc.6, and a skeletal program rc script that I can adapt for my own daemons. I'll be happy to recompile programs that give the option of using the old init.

Don't worry about people becoming emotional. I won't ever meet you in person and won't hate you personally. However, I do have to make a stand, even if it is positioning myself to get out of the way of "progress." My late nights of administration look like they're about to become yet longer, so there's no other choice but to make a stand.

My opinion is that I'd welcome the existence of a project like this, but I'm not personally interested in participating.

There is already an eudev slackbuild:
https://www.linuxquestions.org/quest...es-4175505218/

I'm currently testing it, and it works fine.

I'm not interested in testing systemd.

For my money, no one was yet able to show anything wrong with the current init. It is dead simple. The boot time is completely irrelevant for me. So is the predicted inability to run Gnome or any other application dumb enough to stick its neck into the systemd noose (and I don't even have a strong opinion about the latter, I just think that tying any app to an init system is moronic). I am still convinced that the best way forward is to wait and see. Praise "Bob", the bringer of slack.

Originally Posted by bartgymnast We as community should act upon this together, and find the proper solution.

Speak in singular form next time, please.

Having nothing against decent alternatives not taking away freedom of choice in other areas. I've personally tried eudev and found it mostly functional and working. It may be a solid replacement of udev RH guys recently entombed. init replacement don't find in any way urgent, neither system daemons and tools so not interested in systemd monoculture.

Originally Posted by qweasd I am still convinced that the best way forward is to wait and see. Praise "Bob", the bringer of slack.

That's what most people are doing, and it's probably a good choice. However, I want to help steer the future away from systemd and to alternatives because there are many and because I don't want lock-in. From what I've seen systemd devs have been extremely aggressive in pushing systemd down as many throats as possible and locking people in so they can't use anything else. Simply waiting and seeing what happens may not be enough.

id like wayland even though i couldn't use it (nvidia gpu)
it would require adding a couple ./configure flags to mesa, xorg-server 1.16 and probably a couple other things (and ofc wayland lib)
oh, ye, and the whole logind thing from openBSD for some DE-s

@metaschima I find the best strategy don't support anything trying to succumb to systemd's subsystem so projects like uselessd would not help much. Just let upstream devs know/aware their software is used also on non-systemd distributions so there won't be wired-in mostly unnecessary hard dependencies to it.

When speaking about Wayland, besides debates about (in)maturity of current codebase and drivers support, I've read it does not and even doesn't plan implement remote logins/sessions. How can fill this missing gap Wayland users ? I've read about NX-dervied x2go but yet not yet heard about production use.

Originally Posted by dunric I've read it does not and even doesn't plan implement remote logins/sessions. How can fill this missing gap Wayland users ?

with VNC (example)
it may be controversial but X devs recommend VNC even for remote X, since the X client-server protocol is a bit of a mess

Originally Posted by genss id like wayland even though i couldn't use it (nvidia gpu)

Could you explain? Why does having an nvidia gpu prevent you from using wayland?

Originally Posted by thirdm Could you explain? Why does having an nvidia gpu prevent you from using wayland?

before it was practically impossible due to random lockups
now the nouveau driver is a lot more stable but i still can't run dota2 on it (terrain does not render), and that is a requirement for me

Originally Posted by genss with VNC (example) it may be controversial but X devs recommend VNC even for remote X, since the X client-server protocol is a bit of a mess

I'm afraid VNC is something different. VNC is only a shared remote desktop control solution which does not support independent remote sessions like RDP servers do.

Originally Posted by dunric I'm afraid VNC is something different. VNC is only a shared remote desktop control solution which does not support independent remote sessions like RDP servers do.

i'm sure wayland will support off-screen rendering eventually
https://dvdhrm.wordpress.com/tag/offscreen-rendering/ is what i found