<div class="gmail_quote">On Thu, May 12, 2011 at 6:59 PM, Gustavo Sverzut Barbieri <span dir="ltr"><<a href="mailto:barbieri@profusion.mobi">barbieri@profusion.mobi</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div>Well, maybe you didn't get the activation part or you're trolling :-)</div><div><br></div></blockquote><div>Neither...</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div></div><div>As I said in my mail about the bluetooth part, the problem with kernel modules is that "you don't know what's in there until you look in there". If you don't have usb subsystem you can't know an usb sound card may be there :-D Same for audio device on bluetooth on usb, etc.</div> <div><br></div></blockquote><div>But if you have a USB subsystem, you *do* know what the devices are before loading the modules - USB, PCI, etc. all have the notion of a "device class" that tells you what kind of thing it is.</div> <div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div></div><div>And while upstart was indeed all about "events" (at least 3 years ago it was), systemd provides multiple ways to handle services, not just socket activation, but timers, various conditionals (paths, directories...) and events. You used to force one direction in the graph, we offer both.</div> <div><div></div><div class="h5"> <div><br></div></div></div></blockquote><div>You appear to be confusing my mails with someone who isn't genuinely of the opinion that Upstart doesn't work, and is trying to gather information about the other kid in town to see whether that solves problems he's encountered since.</div> <div><br></div><div>Scott</div></div>