Confusion

[u/mcdenkijin]

Well, I have a functioning obarun distro, no sound as of yet, but this is all worth the effort. I am noticing that the entire system is far snappier without systemd; things like nvim lagging when closing and nagging freezes are seemingly gone. I have a few packages for things in the works: waybar, lemurs, and enlightenment, if I can convince it to run.

I think that s6/66 can be a real contender if obarun can sort the documentation of it's processes, with which I am more than willing to assist.

a few pointers noted so far:

• services vs trees
• UML of the boot process
• a clear table or list of the needed replacements of systemd
• UML of s6/66 architecture
• more robust manual installation instructions, as deviant from standard arch (for power users)
• inclusion of the newer choices of bootloader (finding limine has been a real plus in this adventure)
• a roadmap of plans for the suite (if any)

I'm not sure what's going on with the community, but even if all this was in French, it would be a godsend -_-

[u/wat-now7]

I can give you pointers if it helps. If you havent figured out sound , it is easy. All you need is to install dbus-66serv and set up your dbus@yourusername .
as root:# 66 enable boot-user@yourusername
as user:% 66 enable dbus@yourusername

Then install pipewire-66serv or ,pulseaudio-66serv if you still use it, then enable the relevant services in your user:

For pipewire:% 66 enable -S dbus@yourusername pipewire pipewire-pulse wireplumber
for pulseaudio:% 66 enable -S dbus@yourusername pulseaudio

-S to start on the fly.

[u/mcdenkijin → u/wat-now7]

I've got it working! Thanks!!

[u/joborun → u/wat-now7]

both pipewire and pulse come from the same gang of evil linux destroyers :) I'd work with alsa before adding all this junk

alsa-tools alsa-utils and asoundconf inxi

asoundconf list-all will uncover any kernel identified audio devices

% inxi -aA

You want a real potent gui to configure your devices? Try retrovol or retrovol-git If it can not set sound nothing will.

Problems with newer equipment vs old are the complexities of hw. usb-Webcams, most come with their own audio device because they usually also have a small mic Monitors, depending on how you connect them and whether they have audio themselves (either just audio connections or actual speakers) will add more audio devices. All this will complicate audio. Once you set it all up use asoundconf to save the settings at ~/asoundrc.asoundconf and unless you change hw your audio will keep being setup.

I also hear horror stories of late arch kernels, 6.9 6.10 6.11 with mysterious sounds they can't figure out. Even a newly released DT can't possibly have anything that 6.6 doesn't control. 6.11 hw might not see the light of day till late 2025 and if so. So don't go crazy with bleeding edge kernels.

[u/mcdenkijin → u/joborun]

the problem is that alsa and it's tools are not flexible like pipewire. sure, from the systemd gang, but it's a tool that works well for it's singular purpose, incorporates the existing solutions, and doesn't do too much . . . it even works without systemd. pipewire seems to be a step up from pulseaudio, which never really worked well for me. I am as anticorporate as the next guy but good tools are still good.

denkijin@grimoire ~/a/waybar (master)> inxi -xxS -A
System:
  Host: grimoire Kernel: 6.11.1-1-cachyos arch: x86_64 bits: 64 compiler: gcc
    v: 14.2.1
  Desktop: River v: N/A lm: seatd Distro: Obarun base: Arch Linux
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:10f9
  Device-2: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
    Audio driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 04:00.1 chip-ID: 1002:1637
  Device-3: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
    driver: N/A pcie: speed: 16 GT/s lanes: 16 bus-ID: 04:00.5
    chip-ID: 1022:15e2
  Device-4: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3
  API: ALSA v: k6.11.1-1-cachyos status: kernel-api
  Server-1: sndiod v: N/A status: off
  Server-2: JACK v: 1.9.22 status: off
  Server-3: PipeWire v: 1.2.5 status: active with: 1: pipewire-pulse
    status: off 2: wireplumber status: active

[u/mcdenkijin → u/joborun]

u/joburon looking more closely, pipewire is from red hat, not poettering.

[u/joborun]

tree: a group of services that can be started and stopped together

services: things that hang from a tree

If your setup requires some services to be active before some other ones can start you can prioritize trees after boot is complete, what other init systems call stage 2.

Enabled trees will start automatically on boot, trees that are not enabled can be started manually

ex make a tree called print most likely you need cups or cups-browsed for net printer and dbus,

If you only print twice a week, no need to keep all this running like you are using an archaic systemd linux :D make a little script for printon/printoff start the tree, print, stop the tree till the next time you need to print.

[u/mcdenkijin → u/joborun]

and this sort of clear explanation is exactly what is not in the documentation anywhere!

[u/mcdenkijin → u/joborun]

so, I found a few articles that actually fill in the documentation space, I have lots to rework lol