MX-19 Beta 2.1 Feedback

[winemaker]

take it with a grain of salt? try to look into specifics. i am new to mx and sysvinit or whatever it is called. i do not know much either but i am running decently with it and i trust the developers. I also am not really interested in what people say about systemd as such since technically i am not running it anymore utilizing mx 18.3.

[xtrail]

how do i use sysvinit? is there any tutorials on that?

[timkb4cq]

Not a tutorial per se but a cheatsheet showing how the sysvinit syntax compares to systemd syntax. You'll see it's pretty easy for common commands.
https://fedoraproject.org/wiki/SysVinit ... Cheatsheet

[xtrail]

Not a tutorial per se but a cheatsheet showing how the sysvinit syntax compares to systemd syntax. You'll see it's pretty easy for common commands.
https://fedoraproject.org/wiki/SysVinit ... Cheatsheet

what is frobozz? do i actually have to add that into every command? thanks

[xtrail]

this is too confusing for me.. maybe its better i go back to another linux os that is simpler without all these new commands... thankyou for your help :)

[SwampRabbit]

this is too confusing for me.. maybe its better i go back to another linux os that is simpler without all these new commands... thankyou for your help :)

You don't need to do anything with sysvinit to use MX Linux. If you have specific questions on sysvinit, please start a new thread, this is the MX-19 Beta thread.

[Richard]

@xtrail
I am confused as to why systemd is important to you?
Are you a sysadmin?

To use sysvinit you don't have to do anything but boot the default kernel, start up the apps you wish to use, and do your thing.

[JayM]

how do i use sysvinit? is there any tutorials on that?

Code: Select all

man service

in a terminal is a good starting point. That's the command you use to start and stop services in sysvinit. If you absolutely must have systemd for some reason just boot with that kernel option in your grub menu under advanced options.

[winemaker]

see:
https://mxlinux.org/about-us/

"Our Positions
Systemd
Because the use of systemd as a system and service manager has been controversial, we want to be clear about its function in MX Linux. Systemd is included by default but not enabled. You can scan your MX system and discover files bearing systemd* names, but those simply provide a compatibility hook/entrypoint when needed.

MX Linux uses systemd-shim, which emulates the systemd functions that are required to run the helpers without actually using the init service. This means that SvsVinit remains the default init yet MX Linux can use Debian packages that have systemd dependencies such as CUPS. This approach also allows the user to retain the ability to choose his/her preferred init. For details, see the MX/antiX Wiki."

[Stevo]

I know Dolphin_oracle was concerned about us getting the right version of the stock Debian kernel, as in unsigned vs signed, and possible updates of that breaking persistent Live USBs, but Debian just pushed an updated 4.19.0-6 kernel to all of us, so I am wondering if anyone is reporting any ill effects.

I'm also wondering how we are going to handle Debian security updates to the 4.19 kernel, especially if they go to 4.19.0-7 and so on.