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

Re: systemd-fsck?



[I kept your Cc, I don´t need to be Cc´d tough as I am subscribed to the 
list.)

Am Samstag, 10. Mai 2014, 21:21:30 schrieb Norbert Preining:
> Hi Martin, hi all,
> 
> > being told "Go away" just doesn´t match the responsibility for dealing
> > with
> > issues with something that is a default for all users who don´t change it.
> 
> Indeed, and that is the feeling all around. Systemd developers
> often (by default?) tell people to go away - you don't have commit rights.
> I mentioned this before, here on the list, and elsewhere [1]. Is this
> the upstream we as Debian want to work with? It seems yes, because the
> responsible Debian developers for this piece of software behave the
> same way - go away.
> 
> I mentioned this before in a G+ discussion [2] - devs of programs high
> up in the dependency chain (i.e., not leafs like editors etc) have
> a higher responsibility. Unfortunately neither systemd upstream,
> in particular L. Poettering and K. Sievers, nor the Debian devs
> seem to have grasped the far-reaching responsabilities they have
> taken over.

Just so that it is clear:

I did not make a technical statement about systemd. I understand the reasons 
why Tech-CTTE chose it and while I am skeptical about the attitude of some 
upstream and Debian developers regarding handling bug reports and feedback, I 
am not generally opposed to it. I test drove it for some months some time ago, 
before hibernation was broken when it is in use, and mostly enjoyed the test 
drive.

So please don´t use my feedback for any general anti systemd agenda. I am not 
opposed to it. But it for it to be default certain criteria are not yet met. 
In my eyes partly still open grave bugs and partly the handling or not 
handling of them. I wish that systemd upstream developers and Debian packagers 
adopt the "never break userspace" mantra of the kernel developers as "never 
break applications and application oriented services and if you do take bug 
reports seriously". Cause for me systemd is a system component. Yes, it lives 
in otherspace, but it is so lowlevel that for me it is part of the system 
which provides services to application (just like the kernel does).

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


Reply to: