1. 31 May, 2011 1 commit
  2. 22 May, 2011 6 commits
  3. 21 May, 2011 4 commits
  4. 19 May, 2011 6 commits
  5. 12 May, 2011 3 commits
  6. 10 May, 2011 1 commit
  7. 09 May, 2011 1 commit
  8. 07 May, 2011 3 commits
  9. 30 Apr, 2011 5 commits
  10. 26 Apr, 2011 1 commit
  11. 25 Apr, 2011 1 commit
  12. 24 Apr, 2011 4 commits
  13. 23 Apr, 2011 4 commits
    • Dave Reisner's avatar
      Use Makefile to replace install.sh · a2b48109
      Dave Reisner authored
      If we're going to use a Makefile for minilogd, we might as well use it
      for everything. This has some moving pieces:
      * fix minilogd rule: minilogd.o is a target dep not a build rule
      * rename adjtime.cron => adjtime
      * fixup PKGBUILD to account for changes
      Signed-off-by: default avatarTom Gundersen <teg@jklm.no>
    • Tom Gundersen's avatar
      remount root very early · 5fcb5afe
      Tom Gundersen authored
      This remounts root read-only as early as possible.
      In FS#23845 we saw an example of what might happen if we boot with
      root mounted rw and something manages to opens a file read-write
      on root before we remount read-only.
      Signed-off-by: default avatarTom Gundersen <teg@jklm.no>
    • Tom Gundersen's avatar
      create /run/lock · eda191cf
      Tom Gundersen authored
      This allows /var/run and /var/lock to be symlinked to /run and
      /run/lock, respectively. This would be the final step in fixing
      With /run/lock created early in boot it would be possible for tools
      like mdadm and lvm2 to use this directory for their locking, and
      maybe avoid the --sysinit parameter. This would have to be implemented
      in the respective packages though.
      Finally, /run/lock is created 1777 just like /var/lock is now.
      For the future, it might make sense to follow systemd's lead and make
      it 0755, and then create a subdir /run/lock/lockdev owned by root:lock
      with permissions 0755. This would improve security and fend agains DoS
      attacks, but we would have to check carefully what packages are affected.
      Signed-off-by: default avatarTom Gundersen <teg@jklm.no>
    • Tom Gundersen's avatar
      bootlogd: log messages to console during early boot · a5bdefd4
      Tom Gundersen authored
      This saves all the output during boot to /var/log/boot, which makes
      debugging boot problems much simpler.
      The logfile contains all the control (color) characters from boot, so
      some post processing is in order before the log can be read in a nice
      format (e.g. less should be able to show this nicely in raw mode).
      Start bootlogd as soon as the required /dev/pts is mounted.
      When boot is finished (either at the end of rc.multi or rc.single)
      create the required lof file (/var/log/boot) if it does not exist. This
      causes bootlogd to flush the log to disk.
      Finally, send SIGTERM to bootlogd and clean up after it.
      Idea-and-original-patch-by: default avatarSøren Poulsen <nikorpoulsen@gmail.com>
      Tested-by: default avatarDavid Goldstein <djg1971@gmail.com>
      Signed-off-by: default avatarTom Gundersen <teg@jklm.no>