On Tue, 16 Feb 2016 23:00:27 -0500
Richard Yao <r...@gentoo.org> wrote:

> On 02/08/2016 10:09 PM, Rich Freeman wrote:
> > On Mon, Feb 8, 2016 at 7:58 PM, Anthony G. Basile  
> <bluen...@gentoo.org> wrote:
> >>
> >> what does in-house tool mean?  i'm a gentoo developer but i also
> >> work on an upstream project (eudev) that 14 distros use.
> >>
> >> some of the criticism given here are my concerns as well and i've
> >> spoken with the various distros --- slack, parted magic, puppy.
> >> they get what's going on and they still see eudev is the best way
> >> forward for now.  it may not be in the future, but neither will a
> >> udev extracted from a compiled full systemd codebase.  
> >
> > How many of those 14 distros have more than 14 users?
> >
> > Look, I get it, some people don't like systemd.  That's fine.
> > However, you have to realize at this point that a non-systemd
> > configuration is anything but mainstream.  There will always be a
> > "poppyseed linux" whose purpose in life seems to be to preserve
> > linux without sysfs or some other obscure practice.  I just think
> > that Gentoo should offer the choice to do those things, but have a
> > more mainstream set of defaults.  
> The new mainstream is docker. Docker recently switched to Alpine
> Linux, which uses OpenRC+eudev:
> https://www.brianchristner.io/docker-is-moving-to-alpine-linux/
> That dwarfs whatever marketshare systemd has in the same way that
> Android+iOS dwarfed whatever marketshare Windows has.
> If userbase is what matters to you, then OpenRC+eudev won. It is the
> logical choice for those concerned about userbase because that is what
> the Linux ecosystem will be using going forward.
> I do not think userbase should be the sole means by which we make
> decisions, but those that think otherwise should now join the
> eudev+OpenRC camp. It has the bigger userbase share going forward.
> To put it another way, the war is over. Welcome abroad. :)

I don't know docker well enough, but an lxc container definitely doesn't
use udev inside the container.

Reply via email to