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

Re: systemd - some more considerations



Hi,

On Thu, 03 Apr 2014, Matthias Urlichs wrote:
> > 	https://bugs.freedesktop.org/show_bug.cgi?id=76935
> > 
> It's not "an obvious bug", it's primarily an issue of interpreting whether
> a generic boot parameter like "debug" is intended for just the kernel, or
> the whole system.
> 
> Linux has other programs (and a few kernel modules) whose equivalent of
> verbose=999 will prevent them from working. That's not new. The question is

Besides, they are not PID 1 .... don't divert attention.

> If the maintainer regards this as a design issue which thus should not be
> discussed in a bug report, that's their prerogative. Calling Kai a "d*ck"
> over it (see comment#11) is not going to help.

That is *exactely* the attitude that is dangerous. You are breaking
a system, or many system, but you consider it a design issue that
has to be discussed.

(you being systemd devs, in particular Kay)

See Linus response, and get back to reality
	https://lkml.org/lkml/2014/4/2/420

> I have no sympathy whatsover for people who complain about the systemd
> team's hostility when *they* are the one who start the badmouthing.

WHAT? Did *you* read the bug report. The OP suggested several improvements
and discussions, and *only* after Kay refused to show even a *wink*
of *understanding*, several of the posters got angry at the ignorance
of Kay.

Who on earth is the bummer guy here?

Please *read* the bug report and before coming to completely wrong and
false conclusions.

> > * systemd maintainers (Lennart Poettering) does not care for
> >   segfaults in his code, even if it happens in pid 1.
> > 	https://bugs.freedesktop.org/show_bug.cgi?id=74589
> > 
> Oh come on. It's a nontrivial amount of work to reproduce that bug.

What??? Compiling a kernel with CONFIG_CGROUPS=n is 
*nontrivial* amount of work. You have a twisted impression of reality.

If foobar is developing a program for PID 1 that interacts so tightly
with the kernel, I *expect* that developer to have not one, but *many*
kernel running and testing at any point in time.

> > * several kernel maintainer propose (not completely serious, but
> >   it shows the general opinion), to add
> > 	+	BUG_ON(!strcmp(current->comm, "systemd"));
> 
> URLs please.

Ugg, https://lkml.org/lkml/2014/4/2/422 and follow ups.
I thought that has proliferated into the farest corners of the
internet by now. Followups supporting this idea, of course not 
100% serious, unfortunately.

Norbert

------------------------------------------------------------------------
PREINING, Norbert                               http://www.preining.info
JAIST, Japan                                 TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------


Reply to: