1. 26 Jul, 2012 1 commit
    • Tom Gundersen's avatar
      man: add ArchLinux(7) · 4a84b518
      Tom Gundersen authored
      This outlines what files needs to be configured to get a well-behaved
      For now it is extremely terse, but the main point is to work as a
      check-list, and to point people to the correct manpages to learn more.
      I'll be happy to take patches to extend this in the future.
      One might argue that this sholud not be part of initscripts, and we
      might indeed move it to 'filesystem' or something like that in the
      future. For the time being I'll keep it here for convenience.
      Suggested-by: default avatarThomas Bächler <thomas@archlinux.org>
      Signed-off-by: default avatarTom Gundersen <teg@jklm.no>
  2. 24 Jul, 2012 6 commits
  3. 23 Jul, 2012 3 commits
  4. 21 Jul, 2012 4 commits
  5. 19 Jul, 2012 3 commits
  6. 18 Jul, 2012 7 commits
  7. 17 Jul, 2012 6 commits
  8. 15 Jul, 2012 2 commits
  9. 12 Jul, 2012 2 commits
  10. 11 Jul, 2012 2 commits
    • Tom Gundersen's avatar
      cryptsetup: deprecate old syntax and default to the systemd one · 3779f700
      Tom Gundersen authored
      We detect if the old syntax is used, and if so print a warning and use
      the old parsing code. Otherwise, we pass everything on to
      systemd-cryptsetup. Similarly to what was done with the network syntax,
      we intend to keep the legacy stuff working for a long time.
      See crypttab(5) for the new syntax[0].
      The main reason for this change, is to be closer to what other distros
      do. The systemd syntax is based on Debian's format, and is essentially
      what is being used by at least Debian, Ubuntu, Fedora and Suse. Such
      widespread use means that it will be better documented in
      non-Arch-specific documentation, and is more likely to see integration
      with third-party tools. It is also surely appreciated by admins who
      use more than one distro, that they don't have to know more than one
      config format for these sorts of basic things.
      Furthermore, by actually sharing the code with systemd we get to rely on
      their much more widespread testing and review compared to what we are able
      to do ourselves. This is particularly important for the encryption code,
      as it is the most obscure code in initscripts and any bugs in it would
      have potentially very severe consequences.
      Lastly, there are a few (albeit minor) issues I see with our current
      format: /etc/crypttab is not a plaintext file, but needs to be parsed
      through bash. The (deprecated) embedded passwords have been a source
      of problems in the past. And, there is no level of abstraction between
      the crypttab options and cryptsetup, we just pass them on blindly.
      The new format and the old one cover roughly the same usecases. To the
      best of my knowledge, the only use-case not (yet) supported by
      systemd-cryptsetup, is mounting a removable device and reading
      the key from a file on that device. For this, stick with the old syntax
      (though be careful, it is inherently racy).
      [0]: <http://0pointer.de/public/systemd-man/systemd.unit.html> (note
           that keyfile-offset support is coming in the next systemd version).
    • Dave Reisner's avatar
      remove /run/nologin before leaving rc.multi · 27c29c2b
      Dave Reisner authored
      systemd-186 writes this file when running systemd-tmpfiles, but
      initscripts never removes it. This disallows all non-root logins.
      Reported-by: default avatarDan McGee <dan@archlinux.org>
      Signed-off-by: default avatarDave Reisner <dreisner@archlinux.org>
  11. 02 Jul, 2012 1 commit
  12. 29 Jun, 2012 3 commits