| 1 |
> On Feb 17, 2016, at 5:34 AM, Michał Górny <mgorny@g.o> wrote: |
| 2 |
> |
| 3 |
> Dnia 17 lutego 2016 05:00:27 CET, Richard Yao <ryao@g.o> napisał(a): |
| 4 |
>>> On 02/08/2016 10:09 PM, Rich Freeman wrote: |
| 5 |
>>> On Mon, Feb 8, 2016 at 7:58 PM, Anthony G. Basile |
| 6 |
>> <blueness@g.o> wrote: |
| 7 |
>>>> |
| 8 |
>>>> what does in-house tool mean? i'm a gentoo developer but i also |
| 9 |
>> work |
| 10 |
>>>> on an upstream project (eudev) that 14 distros use. |
| 11 |
>>>> |
| 12 |
>>>> some of the criticism given here are my concerns as well and i've |
| 13 |
>>>> spoken with the various distros --- slack, parted magic, puppy. |
| 14 |
>> they |
| 15 |
>>>> get what's going on and they still see eudev is the best way forward |
| 16 |
>>>> for now. it may not be in the future, but neither will a udev |
| 17 |
>>>> extracted from a compiled full systemd codebase. |
| 18 |
>>> |
| 19 |
>>> How many of those 14 distros have more than 14 users? |
| 20 |
>>> |
| 21 |
>>> Look, I get it, some people don't like systemd. That's fine. |
| 22 |
>>> However, you have to realize at this point that a non-systemd |
| 23 |
>>> configuration is anything but mainstream. There will always be a |
| 24 |
>>> "poppyseed linux" whose purpose in life seems to be to preserve linux |
| 25 |
>>> without sysfs or some other obscure practice. I just think that |
| 26 |
>>> Gentoo should offer the choice to do those things, but have a more |
| 27 |
>>> mainstream set of defaults. |
| 28 |
>> |
| 29 |
>> The new mainstream is docker. Docker recently switched to Alpine Linux, |
| 30 |
>> which uses OpenRC+eudev: |
| 31 |
>> |
| 32 |
>> https://www.brianchristner.io/docker-is-moving-to-alpine-linux/ |
| 33 |
>> |
| 34 |
>> That dwarfs whatever marketshare systemd has in the same way that |
| 35 |
>> Android+iOS dwarfed whatever marketshare Windows has. |
| 36 |
>> |
| 37 |
>> If userbase is what matters to you, then OpenRC+eudev won. It is the |
| 38 |
>> logical choice for those concerned about userbase because that is what |
| 39 |
>> the Linux ecosystem will be using going forward. |
| 40 |
>> |
| 41 |
>> I do not think userbase should be the sole means by which we make |
| 42 |
>> decisions, but those that think otherwise should now join the |
| 43 |
>> eudev+OpenRC camp. It has the bigger userbase share going forward. |
| 44 |
>> |
| 45 |
>> To put it another way, the war is over. Welcome abroad. :) |
| 46 |
> |
| 47 |
> Oh, the new thing every cool kid users these days. I have only one question in return: for how long? |
| 48 |
> |
| 49 |
> Today Alpine uses eudev. But people change, distributions change. One year from now, it may be using systemd. |
| 50 |
> |
| 51 |
> Today docker uses Alpine. Tomorrow it may use something else. Or even require systemd by design. |
| 52 |
|
| 53 |
The Alpine Linux developers use eudev where mdev is a pain to use and prefer mdev to it. They also prefer busybox init to just about everything else. The only way Alpine Linux would use systemd is if it were merged into busybox, but the busybox developers dropped systemd support last year because the systemd developers were not great at collaborating. The "busybox is a joke" remarks that I got from them before that happen means that they have been actively sabotaging that relationship for a long time. |
| 54 |
|
| 55 |
I think it is safe to assume that Redhat will drop Linux for Windows before Alpine Linux uses systemd. |
| 56 |
|
| 57 |
> Today docker is the cool thing. One year from now, nobody may remember about it. Didn't things like this happen before? |
| 58 |
|
| 59 |
The iPhone did the same thing to Windows. Then Android came along. Neither contribute to Windows hemomgeny, which is dead. The same is true for systemd. Coincidentally, neither Android nor iOS use systemd. |
| 60 |
|
| 61 |
> Now, let's extend this to a perspective of few years. What is more likely to be extinct: userbase of eudev or systemd? |
| 62 |
|
| 63 |
systemd will always have its niche. The same is true for eudev. The latter will always exist as long the the former exists though as there are too many people who have been alienated by systemd development for them to accept a system running it. |
| 64 |
|
| 65 |
That is unlikely that will change unless developers who the systemd developers alienate were to all die at once. |
| 66 |
|
| 67 |
>>>> |
| 68 |
>>>> it needs to be in the new stage4s to make a bootable system. imo a |
| 69 |
>>>> stage4 should be bootable modulo a kernel. |
| 70 |
>>> |
| 71 |
>>> Sure, a stage4 based on systemd makes a lot of sense. I don't really |
| 72 |
>>> see the point in leaving a kernel out though - I'd even stick a |
| 73 |
>>> precompiled one in /boot on top of having the sources installed. Why |
| 74 |
>>> not make a stage4 install something that takes all of 5 minutes? |
| 75 |
>>> |
| 76 |
>>> I think that offering an eudev-based distro as a default just doesn't |
| 77 |
>>> make sense in 2016. I just think the better road to take is to start |
| 78 |
>>> treating virtual/udev as something that gets installed post-stage3. |
| 79 |
>>> We can't even get people to agree on vi vs emacs as a default. |
| 80 |
>> |
| 81 |
>> We can leave virtual/udev out of stage3, but that doesn't diminish the |
| 82 |
>> need to select sensible default for the virtual/udev provider. |
| 83 |
> |
| 84 |
> |
| 85 |
> -- |
| 86 |
> Best regards, |
| 87 |
> Michał Górny (by phone) |
| 88 |
> |
Archives