Responses to Coming changes in impending MX 25 release.

[debianix]

As a KDE user, who used sysV and X11 all the time with MX23, is there a way i can find out if systemd and Wayland with MX25 KDE will work for my use case, other than trying it out and „learn the hard way“ that it does not? :-)

[DukeComposed]

is there a way i can find out if systemd and Wayland with MX25 KDE will work for my use case

Well I don't know your use case, but considering that MX-25 doesn't exist yet that sounds like it's a bit of a tall order at the moment.

[Adrian]

As a KDE user, who used sysV and X11 all the time with MX23, is there a way i can find out if systemd and Wayland with MX25 KDE will work for my use case, other than trying it out and „learn the hard way“ that it does not? :-)

Legitimate questions, for X11 it's just a matter of a switch at the log in, and I think it's going to remember the last selection, so it's super easy.
For syvinit it's a bit more complicated because it's a bit harder to switch the running init system, but I think we should be able to provide a how-to for that -- or if you don't even want to touch systemd (lest you feel impure) you can always install Xfce or Fluxbox flavor with sysvinit and just install KDE on top.

[BitterTruth]

@Adrian just curious, but if it is possible to have KDE running on sysvinit (even via the roundabout way) why not just make the iso available to stop newbies getting confused? Call it a respin if you like.

[AK-47]

Thanks for the link - when I went there, this caught my eye:

"systemd hangs on startup or shutdown
Sometimes it is necessary to investigate why systemd hangs on startup or on reboot/shutdown."

Huh????? Do the Debian devs consider this to be a standard "feature"? If so, then that's another data point *against* using systemD - if it was a bug, or even a "feature", it should have been either fixed or "enhanced" - by removing the "feature".

: - )

It is software. Software has bugs. Software can do funny things. There are talking points for and against, and the Debian wiki also contains this article: https://wiki.debian.org/Debate/initsystem/systemd

[Eadwine Rose]

How does one see.. later on when all is running and such, and when users ask for help.. can you determine from the QSI which version is running, systemd or sysvintit?

[MikeR]

@Eadwine Rose
From my QSI:

Info:
Processes: 270 Uptime: 2d 6h 8m wakeups: 1 Memory: 7.6 GiB used: 1.98 GiB (26.1%) Init: SysVinit

No experience with systemD
Mike

[j2mcgreg]

How does one see.. later on when all is running and such, and when users ask for help.. can you determine from the QSI which version is running, systemd or sysvintit?

Because it says so?

Code: Select all

Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.12-1-liquorix-amd64
    root=UUID=<filter> ro quiet splash init=/lib/systemd/systemd

[Nokkaelaein]

Because it says so?

Code: Select all

Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.12-1-liquorix-amd64
    root=UUID=<filter> ro quiet splash init=/lib/systemd/systemd

Checking the "Info" section at the very end of the report is the way that always works. If the init system isn't set as an explicit parameter like in the example above, it will not show in the kernel section.

Code: Select all

Info:
  Memory: total: N/A available: 7.64 GiB used: 2.38 GiB (31.2%)
  Processes: 263 Power: uptime: 19m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 3 GiB
    services: upowerd,xfce4-power-manager Init: systemd v: 252 target: graphical (5)
    default: graphical tool: systemctl

[Eadwine Rose]

Ahhh thanks for clarifying :)