Re: New Group Calls For Boycotting Systemd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2014-09-07 at 18:49 +0100, Richard W.M. Jones wrote:
> On Sat, Sep 06, 2014 at 06:54:03PM -0400, Rahul Sundaram wrote:
> > On Sat, Sep 6, 2014 at 5:36 PM, Richard W.M. Jones  wrote:
> > 
> > > We need to decide if just because you manage to get an important core
> > > package into Fedora 4 years ago, that means you can forever more push
> > > any old stuff you want into Fedora, without going back and consulting
> > > with the community and FESCo.
> > >
> > 
> > I am puzzled.  Upstream doesn't need to consult FESCo for developing new
> > features.  However it does need to consult FESCo for Fedora integration and
> > it seems that systemd has.  Can you point out any counter examples?
> 
> There's been a lot of change between systemd-26 (Fedora 15 GA) and
> system-216 in Rawhide.  I'm just looking at the Fedora packages here,
> not the upstream features, because as you say, upstream can develop
> whatever they want and good luck to them.
> 
> Anyway, systemd now does the following which it didn't do in F15:
> 
>  - has its own network configuration system

...which we don't use.

>  - has a way to control firmware boot settings
>  - intercepts coredumps

not on Fedora, abrt does that.

>  - has the journal

was *extensively* discussed and argued about when it landed and whenever
changes were made to its behaviour (see list archives).

>  - has tools for setting the system time and timezone, and locale

Sure. They're useful.

>  - has a firstboot mechanism

Where? In any case, Fedora doesn't use it.

>  - detects virtualization (long story here, but a very bad idea to
>    encourage programs to do this)

I don't believe any Fedora units use this ability. It's there for people
who want to use it.

>  - has the sysusers password mechanism
>  - has a tool for maintaining kernels in /boot
>  - has a login manager

Was explicitly reviewed as a feature.

>  - has a DBus inspection mechanism (useful, but does it need to be
>    in the init system?)

Is it? systemd is a collection of utilities and interfaces and so on
which are developed in the same source repository. Rather like
util-linux contains a whole bunch of those discrete unix-y tools people
are always banging on about. There's a large difference between being
part of the systemd pid 1 process and being part of the systemd package.
(I don't know whether this is, or not, because I don't know exactly what
it is you're talking about).

>  - has a 'top'-like program for control groups

Seems a perfectly appropriate thing for the tool that's managing system
processes. If not systemd where should such a thing live?

>  - has a program for comparing /etc configurations
>  - has its own version of the FHS and a tool for managing it

Erm. What?
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux