On Sat, Jun 20, 2015 at 12:07:59PM +0200, Martin Steigerwald wrote:
> Am Donnerstag, 18. Juni 2015, 12:29:57 schrieb Marlon Nunes:
> > "The job of keeping kernel development moving isn't so much about
> > "technical know-how" these days, he said. Running the core of arguably
> > the world's most important operating system is now about "being trusted
> > and being available. GREG (AKA GREG KROAH HARTMAN) IS THE OBVIOUS NUMBER
> > TWO. HE COULD TAKE IT UP, and then there are a couple of other people.""
> > Linus Torvalds
> >
> > Guy, that's the guy who wants by all means, kdbus in the kernel. That's
> > the systemd guy in the linux kernel community.
> >
> > http://www.theregister.co.uk/2015/06/17/now_i_can_die_happy_what_linus_did
> > nt_iquitei_say/
>
> In the light of
>
> * kdbus support is no longer compile-time optional. It is now
> always built-in. However, it can still be disabled at
> runtime using the kdbus=0 kernel command line setting, and
> that setting may be changed to default to off, by specifying
> --disable-kdbus at build-time. Note though that the kernel
> command line setting has no effect if the kdbus.ko kernel
> module is not installed, in which case kdbus is (obviously)
> also disabled. We encourage all downstream distributions to
> begin testing kdbus by adding it to the kernel images in the
> development distributions, and leaving kdbus support in
> systemd enabled.
Does this mean that kdbus support is not compiled into Poeterring's kernel?
Is this effectively a kernel fork?
-- hendrik
::
Re: [DNG] We Must be Prepared ....
