:: Re: [DNG] We Must be Prepared ....
Top Pagina
Delete this message
Reply to this message
Auteur: Hendrik Boom
Datum:  
Aan: dng
Onderwerp: Re: [DNG] We Must be Prepared ....
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.

>
> Lennart Poettering: [systemd-devel] [ANNOUNCE] systemd v221
> http://lists.freedesktop.org/archives/systemd-devel/2015-June/033170.html
>
> I sure hope that kernel developers still review kdbus carefully and do not
> give in to any downstream pressure by distros.


There is a precedent here (to the extend precedents have any
relevance). Google requested kernel deatures for Android, and Linus
refused. Only once Google changed the specs significantly were Googles
changes admitted. I don't know what the Googles initial proposals
were, or how they were changed (I hope they were in the direction of
security and despecialization), but this does suggest that the kernel
developers have some sense. There is still the question is whether
Redhat has more influence by being a more traditional-looking
Linux-based OS.

-- hendrik