Why are both ALSA card state management schemes started equally?

Recommended Posts

On attempting to disable `sound.target` in a Nanopi Neo3 I noticed that both `alsa-state.service` and `alsa-restore.service` use the same `ConditionPathExists=!/etc/alsa/state-daemon.conf` (apparently called Card State Management Schemes). This contrasts with the unit files on my host system, with `alsa-state.service` using `ConditionPathExists=/etc/alsa/state-daemon.conf` and `alsa-restore.service` using `ConditionPathExists=!/etc/alsa/state-daemon.conf`. What is the reason for using both services within the same scheme?

Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.