If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Following the Arch wiki (which wasn’t that obvious since there is no conversion guide from initscripts/sysvinit to systemd yet), I enabled systemd and while my PC did boot fine, I had no sound (no ALSA) and it got stuck at shutdown. So I guess not everything’s ready yet.

(I searched the wiki/forums and didn’t find anyone talking about ALSA or sound problems with systemd. Tried a few things but no luck.)

Paul Davis isn't involved with RoseGarden, but is the Original Author/Designer of Jack audio connection kit, as well as the Daw; Ardour (cross-platform, Mac and Linux - if you include the Work Done jointly by Harrsion Consoles, their version called 'Mixbus' then there is a Windows port, as well). He has also been involved in some other projects, Notably; he was one of 2 of the original programmers who helped start Amazon.com.

I've also via the jack-dev-list heard him discuss other low-level plumbing he had been involved with in the past, although i can't remember all of the specifics (something to do with schedulers, but i don't think it was to do with linux). he is definitely a very intelligent, talented programmer (among other areas of expertise, which are listed in Wikipedia). The guy really knows his stuff.

Well fancy that. What a small forum we write to
Thanks for the corrections, and links. I'd no idea what he'd done save what I gleaned from his and your comments.
I wonder if klang will be continued considering that the dev didn't really seem able to address Paul's concerns.

Following the Arch wiki (which wasnít that obvious since there is no conversion guide from initscripts/sysvinit to systemd yet), I enabled systemd and while my PC did boot fine, I had no sound (no ALSA) and it got stuck at shutdown. So I guess not everythingís ready yet.

(I searched the wiki/forums and didnít find anyone talking about ALSA or sound problems with systemd. Tried a few things but no luck.)

That's weird, my sound is working just fine. In fact I never had to enable anything to do with the sound, Systemd seems to start ALSA automatically.

But as you say, I guess there must be some bug bears lurking there in certain cases.

I dont think I enabled anything before I reboted. After the boot I enabled (and started) kdm. In the months thereafter I probably have enabled some daemons like networmanager and cups manually. As systemd has graphical target as deafult my guess it should give a working system as default. If something not start as it should it easy to fix it when it happens...

What must be stated

Systemd has thus far not been a huge problem, yet I truly believe both upstart and launchd are better systems. BSD Init scripts are too limited, and they were my no. 1 reason to avoid Arch. A modern Init system is important, and anything recently written in C was an improvement. Systemd limitations aside... Although the lack of portability rubs me the wrong way.

PulseAudio is terrible, 100 ways to Sunday, superfluous doesn't even describe it's worthlessness. Even the PulseAudio developers admit, unwillingness/inability to improve ALSA was used to excuse it's dreaded conception. This actually describes, extremely accurately, what is most irritating about the FOSS development community. When something needs to be improved, instead of cleanly implementing improvements, an extra layer of latency is always the response.

Systemd has thus far not been a huge problem, yet I truly believe both upstart and launchd are better systems. BSD Init scripts are too limited, and they were my no. 1 reason to avoid Arch. A modern Init system is important, and anything recently written in C was an improvement. Systemd limitations aside... Although the lack of portability rubs me the wrong way.

PulseAudio is terrible, 100 ways to Sunday, superfluous doesn't even describe it's worthlessness. Even the PulseAudio developers admit, unwillingness/inability to improve ALSA was used to excuse it's dreaded conception. This actually describes, extremely accurately, what is most irritating about the FOSS development community. When something needs to be improved, instead of cleanly implementing improvements, an extra layer of latency is always the response.

Qualms about pulseaudio's implementation aside, saying its completely terrible or superfluous is just stupid. For my usage plain alsa straight up does not cut it, certain things either do not work at all or take significant configuration (for example my hdmi audio output on my laptop). Pulseaudio handles all these things perfectly for me out of the box.

1. How the fuck was systemd 'created because pulseaudio sucks'? That literally makes no sense, pulseaudio and systemd have absolutely nothing to do with eachother, besides being created by the same author.

2. Again, what the fuck do rkit and pulseaudio have to do with systemd? NOTHING.

3. Why is this bad exactly? Dbus is extremely useful and tons of software already depends on it.

4. How the flying FUCK does it "gnomify" your computer? That makes absolutely no sense, systemd has nothing to do with gnome.

5. I don't even understand what the hell you are trying to say here...