Announcement

Collapse
No announcement yet.

Lennart Poettering - systemd + PulseAudio Creator - Departed Red Hat

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    Originally posted by tildearrow View Post

    Binary logs aren't a problem.

    The bigger problem is systemd's log spam feature which can be triggered by pressing SysRq-U.
    ``u`` Will attempt to remount all mounted filesystems read-only.
    surprised_pikachu.jpg

    Well, what did you expect?

    Comment


    • #22
      Originally posted by intelfx View Post



      surprised_pikachu.jpg

      Well, what did you expect?
      I need to clarify.

      Something recently caused my root volume to be remounted read-only. Unfortunately, I was not able to find out what it was because journald filled the kernel log with messages reading Failed to trun...


      What I expected is systemd not to spam the journal/dmesg with "failed to write entry" when a disk goes read-only. Yes, this can happen if the kernel decides to remount a disk in read-only mode (e.g. due to read or write error).
      Last edited by tildearrow; 05 July 2022, 08:04 PM.

      Comment


      • #23
        Originally posted by loganj View Post

        i sure hope pulse will stay forever
        pipewire has to many issues and workarounds for me to replace pulseaudio
        From the day I made the switch to PipeWire I have had no issues with it. In fact, about the only difference I even noticed was improved Bluetooth audio.

        Comment


        • #24
          Originally posted by andyprough View Post
          He was planning to remain an IBMer for another ten years, but like with so many processes these days, systemd-oomd terminated his employment process suddenly and without prior warning.
          I think I peed a little bit when I laughed out loud.

          Comment


          • #25
            Originally posted by loganj View Post
            i sure hope pulse will stay forever
            pipewire has to many issues and workarounds for me to replace pulseaudio
            And I hope pulse will die as soon as possible. Even 2 years ago PipeWire was already much better - better resampling quality by default, less resource consumption, less latency and it worked with my bluetooth headphones out of the box using best codec available.

            Comment


            • #26
              Originally posted by intelfx View Post



              surprised_pikachu.jpg

              Well, what did you expect?
              It's not that this bug is only triggered by the sysrq key in question, but that is a way to simply reproduce it. The bug is journald will spam the ring buffer making it harder to diagnose why your system went read only by looking at your console. It's an old bug but as annoying as ever this many years later.
              Last edited by jbean; 05 July 2022, 03:56 PM.

              Comment


              • #27
                Originally posted by pWe00Iri3e7Z9lHOX2Qx View Post

                I know it's cool to hate on anything that isn't a plain text file, but those consolidated binary logs make it a shit ton easier to find what you need when debugging with journalctl than trying to guess / find which one of 15 different text log files might have what you need spread across many different locations.
                Off topic but I've been wondering: all open document files (.ods, .odf, ..) are zip files with a different extension so when you update say a text paragraph in your .odf file the LibreOffice editor has to do a ton of work when you press Ctrl+S: when opening the .odf it unzips all files into a temp location, changes the text in the proper file, builds a new zip file and replaces the existing zip file with the new one (with the corresponding extension instead).

                I was wondering if there could be a (smart?) binary format so that you just update that single text paragraph (or what have you) and that's it.
                As for size, maybe it could have optional compressed sections to save space. You know, a smart file format if you will. Maybe it already exists elsewhere for a long time I just don't know what it's called.

                Comment


                • #28
                  Originally posted by treba View Post
                  I'm really looking forward for one of his younger projects, systemd-homed, to mature enough to be offered by distribution installers. Having my data encrypted while only having to insert one password has been a feature I've been missing on Linux for a long time. Especially removing that password from memory on suspend so I don't need to turn off the device for it to be save.
                  I would only be comfortable with full disk encryption. If you just encrypt the profile then you never know if, for some reason or another, some private information might get saved elsewhere on the system.

                  Also too, I think it would take quite a high-level adversary to extract your encryption key from the system's memory when it's locked.

                  Comment


                  • #29
                    Originally posted by Alexmitter View Post
                    I would wonder what he will do next if he really leaves redhat, no matter what it will likely be outstandingly great and as revolutionary like his other works.

                    A absolutely outstanding developer, one of the few best we have.
                    he is definitely one to push Linux forward, even if it means making it incompatible with other operating systems. and taking the criticism.

                    i remember when people cried "FHS violation" when systemd proposed /run for volatile files - even though the existing alternatives were quite literally a dumpster fire of random ideas. or people moaned that systemd was not portable to non-linux os, since it used so many advanced features of the kernel. features that barely anyone used up to that point. or that people still hate Pulseaudio, even though it solves so many problems for regular users.

                    nowadays, thanks to systemd we have standardized service definition files, easy resource control for services, service dependencies, hardware triggered services, and likely a whole lot more things. i'd rather not go back to classic init systems unless i was doing an embedded system image on very low resource footprint and needed a handful of features.

                    some ideas in systemd are likely way ahead of their time, because majority of users (and developers) are stuck in legacy thinking. or they just lack an reasonable use-case. that factory reset idea, stateless systems and reproducible images - they got on it before anyone else came up with a solid implementation for that idea.

                    also, iirc, the kernel introduced a lot of practical enhancements for userspace, simply because systemd showed that there was a need for them.

                    Comment


                    • #30
                      Since he mentions that systemd is still his focus, I'd guess he ends up at some company as Intel or another big player. Anyway, all the best.

                      For all those hating on Pulse: You remember the days before that? Basically everyone and everything having their own implementation for dealing with ALSA (or for the worse OSS)? Pulse took a lot of complexity off that, and made managing and using the audio and devices universal and comparably "easy" in applications. And seriously, I wouldn't want to deal with implementing anything on top of ALSA, ever. PipeWire is more modern, ofc, is better suited for modern use cases. But Pulse was first released in 2004 and in the works some time before that (as a side note, Bluetooth was first used in consumer devices 1999, and didn't have a very wide adoption by 2004 in the pre-smartphone time). PipeWire just started development in 2015, and is very likely designed with more modern use cases in mind.

                      Not saying all about Pulse was good, it was not. But it really got rid of a lot of issues and got us a deal forward when it comes to using sound devices on Linux.

                      Comment

                      Working...
                      X