From: nunojsilva@invalid.invalid   
      
   On 2026-01-19, Lawrence D’Oliveiro wrote:   
      
   > On Sun, 18 Jan 2026 23:04:33 +0100, Carlos E.R. wrote:   
   >   
   >> On 2026-01-18 22:04, Lawrence D’Oliveiro wrote:   
   >>>   
   >>> On Sun, 18 Jan 2026 12:50:13 +0100, Carlos E.R. wrote:   
   >>>   
   >>>> By the way, syslog doesn't get all the boot messages.   
   >>>   
   >>> That’s one of the goals of systemd, to be able to capture messages   
   >>> from as early as possible.   
   >>   
   >> Syslog, before systemd intervened, managed to capture all messages   
   >> just fine.   
   >   
   > It was never able to capture the dmesg stuff, as far as I know.   
      
   I don't even know if this is describing something that's systemd under   
   the hood or if it is syslog, but [1].   
      
   Also [2] (requires JavaScript to read what ought to be static   
   content...) for syslog-ng.   
      
   [1] https://docs.redhat.com/en/documentation/red_hat_enterprise_   
   inux/8/html/managing_monitoring_and_updating_the_kernel/getting-   
   tarted-with-kernel-logging_managing-monitoring-and-updating-the-kernel   
      
   [2] https://github.com/syslog-ng/syslog-ng/issues/1360   
      
      
   --   
   Nuno Silva   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)