4 ms·

No, I didn't because I didn't want systemd-coredump to handle (and grab) core dumps in the first place and existing discussions and bug reports didn't appear to

by cm3 11y ago

No, I didn't because I didn't want systemd-coredump to handle (and grab) core dumps in the first place and existing discussions and bug reports didn't appear to miss public awareness of the issue. Also previous experience with the maintainers left a bad taste in my mouth. I should be more professional, but the mental barrier to engage with the systemd community is rather high. I cannot say the same about other freedesktop teams with which I regularly communicate in bugzilla.

chris_wot 11y ago
Sorry to hear that.
- cm3 11y ago
  You don't have to be sorry, it's just that systemd as integrated in distros asks for regular QA work by the users, which I don't want to spend my time on. I'm happy to QA certain applications I follow closely, but in the past a Linux system once configured just worked even across major release upgrades. The patch OpenSUSE integrated to work around coredumpd was funny and quite all encompassing, all the while looking like they're trying very hard to close all possible avenues for it to creep back in. It's somewhere linked in an ArchLinux forum thread as a link to an opensuse github commit. Considering OpenSUSE distro devs as informed and capable that commit convinced me that at some point the workaround of overriding kernel.core_pattern in /etc/sysctl.d/50-coredumpd.conf might stop working. I don't look forward to that day and might switch to another distro before that.
  - chris_wot 11y ago
    Actually, that's not true. I've had situations where my configurations broke between major releases of Ubuntu. I reported the issue and eventually it got resolved (no idea how I'm afraid), but whatever the issue for me it must have been an edge case as it wasn't widely reported. That seems to be the case for you as well. You have my sympathies, it's most frustrating when it occurs.
    - cm3 11y ago
      > I reported the issue and eventually it got resolved (no idea how I'm afraid), but whatever the issue for me it must have been an edge case as it wasn't widely reported. Recently there have been major regressions in the kernel due to DRM atomic modesetting with bug reports with many confirmations and zero action from the maintainers while not being able to go past kernel 4.1 which is fortunately one of the long-term branches. 4.2 is also okay but there's no 4.2 lts branch. I never used Ubuntu as my workstation OS, so I cannot talk about their QA standards or how well it would have worked for me, but I've observed sloppiness in their packaging and integration work on others' systems. I mean, it's also important to remember that the advertised number of Ubuntu packages is not truthful if you're honest, because it's a snapshot of Debian's repositories and thus anything in Universe is probably unmaintained when compared to the repository in Debian. That means, the curated set of packages is quite small in comparison. I hope the situation improved in the last years.
      - chris_wot 11y ago
        Yeah, frustrating. But not really something you can pin solely on systemd...
        cm3 11y ago
        I didn't, it's a totally different part and fallout from a major change.
        chris_wot 11y ago
        In that case I misunderstood you and owe you an apology. Sorry about that. I appreciate your viewpoint, even if I disagree with you. I think systemd is a bit of a sore spot for me so I'm probably a bit too insistent and forceful on this issue so if I overstepped the mark I apologise for that also. Peace :-)

by cm3 11y ago

chris_wot 11y ago

Sorry to hear that.

cm3 11y ago
You don't have to be sorry, it's just that systemd as integrated in distros asks for regular QA work by the users, which I don't want to spend my time on. I'm happy to QA certain applications I follow closely, but in the past a Linux system once configured just worked even across major release upgrades. The patch OpenSUSE integrated to work around coredumpd was funny and quite all encompassing, all the while looking like they're trying very hard to close all possible avenues for it to creep back in. It's somewhere linked in an ArchLinux forum thread as a link to an opensuse github commit. Considering OpenSUSE distro devs as informed and capable that commit convinced me that at some point the workaround of overriding kernel.core_pattern in /etc/sysctl.d/50-coredumpd.conf might stop working. I don't look forward to that day and might switch to another distro before that.
- chris_wot 11y ago
  Actually, that's not true. I've had situations where my configurations broke between major releases of Ubuntu. I reported the issue and eventually it got resolved (no idea how I'm afraid), but whatever the issue for me it must have been an edge case as it wasn't widely reported. That seems to be the case for you as well. You have my sympathies, it's most frustrating when it occurs.
  - cm3 11y ago
    > I reported the issue and eventually it got resolved (no idea how I'm afraid), but whatever the issue for me it must have been an edge case as it wasn't widely reported. Recently there have been major regressions in the kernel due to DRM atomic modesetting with bug reports with many confirmations and zero action from the maintainers while not being able to go past kernel 4.1 which is fortunately one of the long-term branches. 4.2 is also okay but there's no 4.2 lts branch. I never used Ubuntu as my workstation OS, so I cannot talk about their QA standards or how well it would have worked for me, but I've observed sloppiness in their packaging and integration work on others' systems. I mean, it's also important to remember that the advertised number of Ubuntu packages is not truthful if you're honest, because it's a snapshot of Debian's repositories and thus anything in Universe is probably unmaintained when compared to the repository in Debian. That means, the curated set of packages is quite small in comparison. I hope the situation improved in the last years.
    - chris_wot 11y ago
      Yeah, frustrating. But not really something you can pin solely on systemd...
      - cm3 11y ago
        I didn't, it's a totally different part and fallout from a major change.
        chris_wot 11y ago
        In that case I misunderstood you and owe you an apology. Sorry about that. I appreciate your viewpoint, even if I disagree with you. I think systemd is a bit of a sore spot for me so I'm probably a bit too insistent and forceful on this issue so if I overstepped the mark I apologise for that also. Peace :-)