Page 1 of 1

SystemD Option

Posted: Mon Apr 17, 2023 8:56 am
by geffers

Code: Select all

System:    Kernel: 5.10.0-21-amd64 [5.10.162-1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-amd64 
           root=UUID=<filter> ro splash quiet 
           init=/lib/systemd/systemd 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: TOSHIBA product: SATELLITE C55D-C v: PSCQEE-03C00TEN 
           serial: <filter> 
           Mobo: FF50 model: 06F7 serial: <filter> UEFI: Insyde v: 5.20 date: 10/02/2015 
Battery:   ID-1: BAT1 charge: 20.1 Wh (100.0%) condition: 20.1/31.7 Wh (63.3%) volts: 16.4 
           min: 14.4 model: SDI PA5185U-1BRS type: Li-ion serial: N/A status: Full cycles: 343 
CPU:       Info: Quad Core model: AMD A8-7410 APU with AMD Radeon R5 Graphics bits: 64 type: MCP 
           arch: Puma family: 16 (22) model-id: 30 (48) stepping: 1 microcode: 7030105 cache: 
           L2: 2 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 17566 
           Speed: 1135 MHz min/max: 1000/2200 MHz boost: enabled Core speeds (MHz): 1: 1135 
           2: 1512 3: 1031 4: 1043 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed mitigation: untrained return thunk; SMT disabled 
           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: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Mullins [Radeon R4/R5 Graphics] vendor: Toshiba driver: radeon v: kernel 
           alternate: amdgpu bus-ID: 00:01.0 chip-ID: 1002:9851 class-ID: 0300 
           Device-2: IMC Networks TOSHIBA Web Camera - HD type: USB driver: uvcvideo 
           bus-ID: 4-1.1:3 chip-ID: 13d3:5652 class-ID: 0e02 serial: <filter> 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: ati,radeon 
           unloaded: fbdev,modesetting,vesa display-ID: :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 res: 1366x768 hz: 60 dpi: 101 size: 344x194mm (13.5x7.6") 
           diag: 395mm (15.5") 
           OpenGL: renderer: AMD KABINI (LLVM 14.0.5 DRM 2.50 5.10.0-21-amd64) v: 4.5 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: AMD Kabini HDMI/DP Audio vendor: Toshiba driver: snd_hda_intel v: kernel 
           bus-ID: 00:01.1 chip-ID: 1002:9840 class-ID: 0403 
           Device-2: AMD FCH Azalia vendor: Toshiba driver: snd_hda_intel v: kernel 
           bus-ID: 00:14.2 chip-ID: 1022:780d class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-21-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Toshiba driver: r8169 
           v: kernel port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter driver: rtl8821ae 
           v: kernel modules: wl port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8821 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Toshiba Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 4-1.2:4 
           chip-ID: 0930:022f class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 
           sub-v: 8821 hci-v: 4.0 rev: a 
           Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park 
           link-mode: slave accept service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 465.76 GiB used: 22.64 GiB (4.9%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 043 scheme: GPT 
Partition: ID-1: / raw-size: 48.83 GiB size: 47.76 GiB (97.81%) used: 22.52 GiB (47.2%) fs: ext4 
           dev: /dev/sda5 maj-min: 8:5 
           ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 115.7 MiB (45.2%) 
           fs: vfat dev: /dev/sda1 maj-min: 8:1 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 44.0 C mobo: N/A gpu: radeon temp: 42.0 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2621 lib: 1494 flatpak: 0 
           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
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list 
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
Info:      Processes: 199 Uptime: 1h 36m wakeups: 1 Memory: 10.67 GiB used: 1.59 GiB (14.9%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI
Folks, this is curiosity, I do not have a problem.

I see with my version of Linux MX I have an option under advanced boot to select SystemD instead of initd

I use systemd with my RaspberryPi systems so am familiar with commands etc but am wondering; for the average user once system has booted up is there any noticeable difference with systemd or initd?

Geffers

Re: SystemD Option

Posted: Mon Apr 17, 2023 8:57 am
by dolphin_oracle
not particularly. the live system works better with sysVinit, but installed doesn't matter at all usually. given debian's use of systemd, there are probably fewer issues with certain applications that use services, the most prominent being the vpn clients.

Re: SystemD Option

Posted: Mon Apr 17, 2023 9:04 am
by BV206
It's probably only an issue if you are used to using "systemctl" commands in the terminal or scripts.

Re: SystemD Option

Posted: Mon Apr 17, 2023 9:47 am
by siamhie
dolphin_oracle wrote: Mon Apr 17, 2023 8:57 am the most prominent being the vpn clients.

and probably certain media servers. I use Emby and it requires systemd.

Re: SystemD Option

Posted: Mon Apr 17, 2023 10:42 am
by anticapitalista
non-free debs like vpn seem to think that only systemd exists grr!

Re: SystemD Option

Posted: Mon Apr 17, 2023 11:00 am
by asqwerth
The fact that fehlix can add sysvinit scripts to vpn packages to make them work, show that they can actually work with sysv; the makers simply didn't include the sysv scripts with their own packages.

Re: SystemD Option

Posted: Mon Apr 17, 2023 11:04 am
by anticapitalista
asqwerth wrote: Mon Apr 17, 2023 11:00 am The fact that fehlix can add sysvinit scripts to vpn packages to make them work, show that they can actually work with sysv; the makers simply didn't include the sysv scripts with their own packages.
Indeed, that was what my growl was about :)

Re: SystemD Option

Posted: Sun Apr 23, 2023 9:15 am
by geffers
Thanks for replies folks, seems in most circumstances nothing really noticed. I do work with command line a lot, usually by ssh into a RaspberryPi so systemD is the one I've lately been accustomed to. Changing an established setup always causes some friction amongst users, the old saying, if it ain't broke don't fix it is true but there again hasn't Linux GUI evolved through changing?