On Sun, 3/1/15, Jude Nelson <jud...@gmail.com> wrote: Subject: Re: [Dng] What if systemd infects the kernel? To: "Gravis" <rin...@adaptivetime.com> Cc: "dng@lists.dyne.org" <dng@lists.dyne.org> Date: Sunday, March 1, 2015, 12:01 AM >> I have been aware of the pending assimilation of systemd into the kernel >> since Linus dramatically rejected Kay >> Sievers' code last spring. Recently there has been renewed chatter about >> the impending doom. But I'm not quite >> clear how that would affect devuan. Hoping you can help me get a grip on >> the situation: >> > As far as I know, systemd is *not* getting merged into the kernel. It's not > even being *considered* for merging. > > Linus was mad at Kay Sievers for something completely unrelated. Kay had > introduced a regression in udev that > could cause it to hang due to the way it handled a driver's request for > firmware (until the kernel timed the firmware > request out after 30 > seconds). Instead of fixing the regression (and it was a regression--he was > using the *well > documented* firmware loader *incorrectly*), he went on to suggest that the > kernel developers were at fault for the > situation by designing Linux's > firmware loader the way they did, instead of fixing the problem he created. > The rest > is history. > > As I said in another thread, kdbus as it is incarnated today (and this is > subject to change--it's been pretty much > re-written each time Greg KH has submitted it to lkml) requires some > userspace help in setting it up. This is only > necessary if your kernel has kdbus and you have programs that want to use it. > kdbus by itself is just another way > to move bytes between processes, and > it offers some semantics that aren't found in other existing IPC > mechanisms. It is *not at all* like dbus, any more than a UNIX domain socket > is like dbus or a pipe is like dbus. > The only thing kdbus has in common with dbus is that it shares part of the > name. > > -Jude
-------------------------------------------- Thank to you, Jude, and the others who helped to clear some of the fog. :) golinux _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
