1. 12 Apr, 2012 1 commit
  2. 11 Apr, 2012 2 commits
  3. 10 Apr, 2012 1 commit
  4. 14 Mar, 2012 1 commit
  5. 15 Feb, 2012 1 commit
  6. 05 Jan, 2012 1 commit
  7. 07 Oct, 2011 1 commit
  8. 01 Aug, 2011 1 commit
  9. 25 Jul, 2011 1 commit
  10. 28 Mar, 2011 1 commit
    • Kay Sievers's avatar
      use /run instead of /dev/.run · 2b583ce6
      Kay Sievers authored
      Instead of the /dev/.run trick we have currently implemented, we decided
      to move the early-boot runtime dir to /run.
      An existing /var/run directory is bind-mounted to /run. If /var/run is
      already a symlink, no action is taken.
      An existing /var/lock directory is bind-mounted to /run/lock.
      If /var/lock is already a symlink, no action is taken.
      To implement the directory vs. symlink logic, we have a:
      now, which is used in the mount units.
      Skipped mount unit in case of symlink:
        $ systemctl status var-run.mount
        var-run.mount - Runtime Directory
          Loaded: loaded (/lib/systemd/system/var-run.mount)
          Active: inactive (dead)
                  start condition failed at Fri, 25 Mar 2011 04:51:41 +0100; 6min ago
           Where: /var/run
            What: /run
          CGroup: name=systemd:/system/var-run.mount
      The systemd rpm needs to make sure to add something like:
        mkdir -p -m0755 /run >/dev/null 2>&1 || :
      or it needs to be added to filesystem.rpm.
      Udev -git already uses /run if that exists, and is writable at bootup.
      Otherwise it falls back to the current /dev/.udev.
      Dracut and plymouth need to be adopted to switch from /dev/.run to run
  11. 09 Mar, 2011 1 commit
  12. 04 Mar, 2011 3 commits
    • Lennart Poettering's avatar
    • Lennart Poettering's avatar
      machine-id: typo fix · 9b4f818b
      Lennart Poettering authored
    • Lennart Poettering's avatar
      main: introduce /etc/machine-id · d7ccca2e
      Lennart Poettering authored
      This is supposed to play the same roles /var/lib/dbus/machine-id,
      however fixes a couple of problems:
      - It is available during early boot since it is stored in /etc
      - Removes the ID from the D-Bus context and moves it into a system
        context, thus hopefully lowering hesitation by people to use it.
      - It is generated at installation time. If the file is empty at boot
        time it will be mounted over with a randomly generated ID, which is
        not saved to disk. This is useful to support state-less machines with
        no transient or writable /etc configuration.