Re: (Really) Free Software future

[Alexander Vdolainen]

Hi,

On Tuesday, October 15, 2019 11:31:18 PM EEST address@hidden 
wrote:
> I agree completely about Systemd. Corporate interests are too controling
> over it. I don't know how we could remove elogind and eudev and the likes.
> GNOME doesn't seem to eager to even consider the forks, let alone an
> alternative implementation that Systemd.

Actually you don't need to remove eudev and/or elogind, keep it as a stand 
alone daemons and all is going well. udev was eaten by systemd ... so keeping 
a standalone implementation is quite good thing.

> 
> Free Software should be community developed. There is no problem for
> companies to contribute but they absolutely should not be the the driven
> factor. Otherwise we have an hostile solution to forks like Systemd.

I'm afraid, but in a wildlife most of the big opensource projects are 
supported by the companies. And that is might be ok.

> 
> Fannys
> 
> Oct 15, 2019, 21:56 by address@hidden:
> > On Mon, 2019-10-14 at 22:41 -0400, Richard Stallman wrote:
> >> If systemD is be hard to replace, that is a kind of lock-in.  But it
> >> isn't _vendor_ lock-in.  systemD, like most free software packages,
> >> is not tied to any particular vendor.  Indeed, the usual concept of
> >> "vendor" for free software is not applicable to free software at all.
> > 
> > Sorry Richard, but it is really a vendor lock-in. As you know there is
> > only one _upstream_ of systemd and that upstream is a company. Systemd
> > software is developed by that company, and as you also know is that
> > contributions, patches and bug reports coming from outside that company
> > are frown upon. People reporting issues are even met with hostility.
> > 
> > In case you have counterexamples of the above, please give links,
> > please!
> > 
> > Additionally, software system distributors, like Debian, are fully in
> > the hands of the upstream. They are merely users of systemd, trying to
> > tweak the code to create distributions.
> > 
> > I know that there are partial forks of systemd like eudev and elogind,
> > but such forks should not be needed if upstream created and documented
> > libraries and APIs so that third-party people could adopt and
> > contribute their (maybe complementary) software too. But that is not
> > happening, because if upstream would do that they'd loose their market
> > advantage.
> > 
> > In conclusion: systemd is a _vendor_ lock-in. Fortunately Guix/Shepherd
> > are not (yet??) using systemd, but they use e.g. eudev and elogind.
> > 
> > Thank you for your time!

signature.asc
Description: This is a digitally signed message part.