Announcement

Collapse
No announcement yet.

Systemd 210 Already Has Many Changes Piled Up

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

  • #11
    Originally posted by e8hffff View Post
    I really like SystemD on how you enable and disable processes but I feel the JournalCtl is lacking, or not dishing up. I feel fault finding is more difficult on SystemD setups than other mechanisms. These comments may not be founded but that's the impression I'm getting without proper research.
    I don't know if this would be considered "proper research" but Lennart has some useful examples on his blog.

    http://0pointer.de/blog/projects/journalctl.html

    Comment


    • #12
      Originally posted by michal View Post
      So from my POV it's a bit surprising that Canonical maintains it. The only reasonable explenation for it is that Novel doesn't thread it as important and they don't really care about it's support.
      http://news.cnet.com/8301-13580_3-9796140-39.html

      Most of the AppArmor developers left SUSE back in 2007. One or two of them were hired by Canonical soon after and it was merged upstream after that. SELinux is used by Fedora/RHEL and Android by default. AppArmor is used by SUSE and Ubuntu. SMACK is used in some mobile platforms including Tizen.

      Comment


      • #13
        Originally posted by michal View Post
        So from my POV it's a bit surprising that Canonical maintains it. The only reasonable explenation for it is that Novel doesn't thread it as important and they don't really care about it's support.
        novell is out.
        http://www.itjungle.com/tfh/tfh052311-story10.html
        attachemate owns SUSE /openSUSE since 2011

        Comment

        Working...
        X