Packages using SystemD and SysVinit [Solved]

[MX_GRD]

Just curious:
Are there packages that only work with SystemD or only works with SysVinit?
I've been using the default SysVinit, but was wondering if I tried SystemD would that affect packages using WINE, Bottles, Flatpaks, appimages?

Code: Select all

System:    Kernel: 5.10.0-34-amd64 [5.10.234-1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-34-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: ASUSTeK product: VivoBook 15_ASUS Laptop X540UAR v: 1.0 
           serial: <filter> 
           Mobo: ASUSTeK model: X540UAR v: 1.0 serial: <filter> UEFI: American Megatrends 
           v: X540UAR.306 date: 08/23/2019 
Battery:   ID-1: BAT0 charge: 30.0 Wh (97.1%) condition: 30.9/33.2 Wh (93.2%) volts: 10.8 
           min: 10.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Not charging 
           cycles: 95 
CPU:       Info: Dual Core model: Intel Core i3-6006U bits: 64 type: MT MCP arch: Skylake 
           family: 6 model-id: 4E (78) stepping: 3 microcode: F0 cache: L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15999 
           Speed: 500 MHz min/max: 400/2000 MHz Core speeds (MHz): 1: 500 2: 500 3: 500 4: 500 
           Vulnerabilities: Type: gather_data_sampling status: Vulnerable: No microcode 
           Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable 
           Type: reg_file_data_sampling status: Not affected 
           Type: retbleed mitigation: IBRS 
           Type: spec_rstack_overflow status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling, 
           PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: ASUSTeK driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300 
           Device-2: Chicony USB2.0 VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-6:3 
           chip-ID: 04f2:b64a class-ID: 0e02 serial: <filter> 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") 
           s-diag: 414mm (16.3") 
           Monitor-1: eDP-1 res: 1366x768 hz: 60 dpi: 101 size: 344x194mm (13.5x7.6") 
           diag: 395mm (15.5") 
           OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3 chip-ID: 8086:9d70 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-34-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: AzureWave 
           driver: ath10k_pci v: kernel modules: wl port: f040 bus-ID: 02:00.0 chip-ID: 168c:0042 
           class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: IMC Networks type: USB driver: btusb v: 0.8 bus-ID: 1-8:4 chip-ID: 13d3:3496 
           class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 
           sub-v: 25a hci-v: 4.2 
           Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff 
           link-mode: slave accept service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 931.51 GiB used: 113.28 GiB (12.2%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10SPZX-80Z10T2 
           size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD 
           rpm: 5400 serial: <filter> rev: 1A04 scheme: GPT 
Partition: ID-1: / raw-size: 923.25 GiB size: 907.69 GiB (98.31%) used: 113.28 GiB (12.5%) 
           fs: ext4 dev: /dev/sda2 maj-min: 8:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 282 KiB (0.1%) fs: vfat 
           dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 1.8 MiB (0.0%) priority: -2 
           dev: /dev/sda3 maj-min: 8:3 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 1900 
Repos:     Packages: 2724 note: see --pkg apt: 2705 lib: 1481 flatpak: 19 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/winehq-bullseye.sources 
           1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bullseye main
Info:      Processes: 238 Uptime: 7d 1h 38m wakeups: 9 Memory: 7.64 GiB used: 3.68 GiB (48.2%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

[dolphin_oracle]

By and large if it works on sysvinit it will work under systemd.

The converse is not true. Some packages only provide systemd service files (some of the vpns are bad for this). Sysvinit does not have capability to process those.


Another good example is pipewire. It does not have a sysvinit service startup. Under systemd it uses a user level service which sysvinit does not have the concept of.

[timkb4cq]

Snap packages require systemd.
I have yet to find a package that works in sysvinit that fails under systemd. Our LiveUSB w/ persistence does have to run in sysv for full functionality.
On the other hand, there are some packages, especially proprietary ones, where the developers assume systemd and only provide systemd initscripts, or worse, put systemd commands in their install scripts so the packages will fail to install with errors if systemd is not running. Most of those will actually run under sysv once installed.

[asqwerth]

I think most vpn apps will run in sysV, if only the devs bothered to include the init scripts for sysV. That's why we have fehlix who adds them back if you install using MXPI Popular apps.

But snaps absolutely require systemd.

[retroD0d0]

I've been using the default SysVinit, but was wondering if I tried SystemD would that affect packages using WINE, Bottles, Flatpaks, appimages?

all moving to systemD boot does in MX is change Pid1 (initial process) to systemd so that programs that need it can use it. As dolphin says if it works in sysV it will work under systemd. I have never had any issue switching between the two at will from my limited time with MX (under a year). So feel free to try the Dark Side.

Edit: I hope I have that right devs? The 'patched-systemd/systemd-shim' combo, running in both bootup modes, is the secret sauce that enables packages dependent on either systemd or sysV init systems to co-exist. Is that correct?

[MX_GRD]

Thanks all, I go way back to MEPIS days, and always installed with default; if it works, leave it alone.
I have tried 3rd party .deb packages and found some would not work; I suspected SystemD was the issue.
..............
If I ever pick up a used cheap laptop, I may venture to the Dark Side; but for now, everything works under SysV.

Thanks again.

Sidenote: I tried [Solved] on all three posts, but only one works; all three posts were useful as Solved.