The fate of Upstart
Enrico Weigelt, metux IT consult
enrico.weigelt at gr13.net
Tue Dec 2 22:39:34 UTC 2014
On 29.11.2014 22:31, I.E.G. wrote:
> I was a "little" surprised to see the "...has been converted to an
> upstart job" message some time ago in response to a ~$ /etc/init.d/
> stop/start/restart/foo .
> I tried the ~$ service stop/start/restart/foo and it either didn't work
> or produced the same "...has been converted to an upstart job".
Yeah, had the same problems...
> I'll just offer one example of what I don't want to see . A deployment
> or migration such as the the protracted abortion that was PulseAudio . I
> still have several hardware instances that never did (and I suspect
> never will) tolerate PulseAudio.
For me, it at least works w/ my hardware, but far from rock-stable.
I regularily have to kill and restart it.
In fact, I never really understood why it's necessary at all.
Okay, moving more stuff into userland has some benefits (eg. adding
virtual devices running as separate servers, etc) - but then it should
be done more consequently, like Plan9 does.
Maybe, if i've someday got enough spare time, I'll fork it and rebuild
it to an plan9'ish system-wide service. Then it would make sense to
move all audio applications to that service only (dropping all native
But for now, I'm still too occupied with other things. For now I'm
more concerned with getting rid of dbus/polkit.
> I even had PA/Devl tell me to upgrade my
> month old hardware in order to make it work (a long and only slightly
> humorous story I'll spare you ) .
Well, the usual Lennartists behaviour ...
metux IT consulting
More information about the Ubuntu-devel-discuss