Announcement

Collapse
No announcement yet.

Debian Jessie Might Get Rid Of The kFreeBSD Port

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

  • #31
    Originally posted by jrch2k8 View Post
    journald: is a early log system for systemd in binary format but doesn't replace r/ng/syslog, this is what make most people cry but it has a very valid reason to exist, r/ng/syslog is too big and have too many runtime dependencies to run too early in the boot process(and for the same reason die too early in the shutdown process) and this was never solved by sysV, i know many people asked why not berkleydb but im not sure if dependencies got too messy or license became a problem since its oracle's now.
    rsyslog, sure.
    syslog-ng needs libc, libglib, and libeventlog (less than 29 kilobytes installed, here on Alpine)
    I don't see that as being heavy compared to systemd's dependencies. Maybe the 230 kilobytes for syslog-ng itself qualify.
    There's also the standard ingredients for an initrd: busybox has a syslogd.
    And logsave can handle early logging.

    Comment


    • #32
      Originally posted by pal666 View Post
      systemd has vastly reduced attack surface. it does not include bash(hello shellshock) and hundreds of other buggy cli tools and unfixable shell scripts. every part of systemd's attack surface has much bigger counterpart in obsolete world of sysvinit
      There are better sysvinit replacements out there: Dan J. Bernsteins daemontools, runit, s6, monit, perp, supervisord, Upstart, GNU dmd to name a few.

      Comment

      Working...
      X