On Sun, 14 Aug 2016 09:02:59 +0200
Didier Kryn <kryn@???> wrote:

> Le 13/08/2016 19:41, Steve Litt a écrit :
> > On Sat, 13 Aug 2016 12:12:04 -0400
> > "Ismael L. Donis Garcia" <slibre@???> wrote:
> >
> >
> >> To my mind would be a better option to opt for eudev that vdev as
> >> it has greater support behind.
> >>
> >> I see half vdev orphan and do not think that support eudev go to
> >> decant by systemd.
> > And when Red Hat buys maintainership of eudev?
> >
>

>      Eudev is free software, isn't it? 

Yes. So is systemd, and so is Dracut, into which Red hat incorporated
systemd things and then emptied its older repositories, making forking
much harder.

> Udev was their baby and they
> integrate it into Systemd.

Udev was created by Kroah-Hartmann and Sievers and others somewhere
around 2002. I'm not a good enough historian to find out who they
worked for back then, but I know that Robert Young still ran Red Hat
back then, and Robert Young **NEVER** would have supported the
shenanigans done by Redhat today. If it was Redhat's baby, Redhat took
it over, possibly by employing Sievers.

> Why would they integrate yet another
> hotplugger.

To stifle systemd competitors.

> In fact, they are only going to drop support for Udev,
> nothing more.

I know nothing about that.

> They only support theur own software; isn't that
> legitimate?

Half of "their own software" was bought, either by acquisition or by
hiring project programmers. They then inserted Halloween Code in their
newly acquired software so it wouldn't run with non-systemd and
non-Freedesktop stuff. Insertion of Halloween code was characterized as
"intentional sabotage" by Adam Borowski in this email:
https://lists.dyne.org/lurker/message/20160813.211227.9340d5a5.en.html

> Our problem is that their software simply doesn't match
> our taste.

We have no problem. Redhat's problem is that they create convoluted
software requiring a million a year in developer salaries to keep
debugged. One can attribute Redhat's actions to some bizarre side
effect of technocracy, or, as I prefer to think of it, to
anticompetitive practices via "intentional sabotage". But one thing's
for sure: they have a pattern and practice of taking simple software and
make it complex. Eudev could be next.

Our only problem is we don't have enough allies.

SteveT

Steve Litt
August 2016 featured book: Manager's Guide to Technical Troubleshooting
Brand new, second edition
http://www.troubleshooters.com/mgr