FAQ | This is a LIVE service | Changelog

  1. 26 Sep, 2019 1 commit
  2. 13 Sep, 2019 4 commits
  3. 12 Sep, 2019 2 commits
  4. 02 Sep, 2019 4 commits
  5. 24 Jul, 2019 2 commits
  6. 10 Sep, 2018 1 commit
  7. 06 Sep, 2018 1 commit
    • Dr. David McBride's avatar
      Add --force option to MBR bootloader install command · e6651caa
      Dr. David McBride authored
      The install-mbr command checks to see if some modern version of the
      MBR (perhaps left behind by Windows 10?) is installed before
      overwriting.  If the modern MBR signature is detected, it refuses
      to proveed, to avoid rendering a local Windows installation unbootable.
      
      We have already determined by this point that no Windows install should
      exist, and failing to install an MBR under these circumstances renders
      a machine unbootable.
      
      Thus, unconditionally add --force to the install-mbr incantation.
      e6651caa
  8. 05 Sep, 2018 2 commits
    • Dr. David McBride's avatar
      Fix boot-time race-condition caused by incorrect file permissions · 1b06d938
      Dr. David McBride authored
      During boot, the network link will come up, and the Unbound DNS
      resolver will start.  If the Unbound daemon starts first, it will
      not be properly configured with upstream DNS server information -
      because, for reasons unknown, the executable permissions on the
      script that update it are missing.
      
      Fix those missing permissions.
      1b06d938
    • Dr. David McBride's avatar
      Add 01-reporting install script that enables high-performance options · c8c997e7
      Dr. David McBride authored
      A booted system isn't necessarily operating in the optimal mode for
      a speedy OS installation.  This script is intended to tweak available
      runtime options to speed up the install.
      
      In this initial version, it sets the CPU governor on each CPU to
      'performance'.  The kernel (or the Ubuntu-based distribution we're
      building on) may have set the CPU governor to 'ondemand' or similar
      as a power-saving measure.
      
      We may later wish to consider also changing the IO scheduler in this
      script, e.g. from 'cfq' to 'deadline'.
      c8c997e7
  9. 04 Sep, 2018 2 commits
  10. 03 Sep, 2018 1 commit
    • Dr. David McBride's avatar
      Use rsyslog to log host telemetry over syslog/TLS. · daa7bb3d
      Dr. David McBride authored
      This involves adding rsyslog to the bootstrap environment and configuring
      it appropriately, as well as updating the top-level installer to send all
      log messages to STDERR from the start via systemd, rather than using
      our own logging facility.
      
      It's important to make rsyslog only start up after the machine's hostname
      has been set; otherwise it will merrily log log messages using the hostname
      'localhost', which is not useful for disambiguating messages from different
      hosts!
      daa7bb3d
  11. 12 Jul, 2018 2 commits
    • Dr. David McBride's avatar
      Fix blank progress report box title. · 19b16cab
      Dr. David McBride authored
      The SCRIPT environment variable is used to hold the title printed
      in the whiptail progress reporting box.
      
      The function reposible for displaying APT progress,
      report_apt_progress(), never calculated this value, and was
      accidentally relying on this being set by other function calls in
      a script.
      
      With the restructuring of the installation process, the 50-install
      script now only reports on APT progress, and no-longer uses any
      of the other progress reporting functions.
      
      As a consequence, the SCRIPT environment variable value is no-longer
      being calculated, thus the whiptail reporting boxes generated by
      the 50-install script have blank titles.
      
      To fix this, enhance report_apt_progress() to also calculate the
      SCRIPT environment value.
      19b16cab
    • Dr. David McBride's avatar
      Apply upstream fix for Debian bug #829725. · 2a288b96
      Dr. David McBride authored
      This bug prevents debootstrap from working properly when operating
      against an upstream archive lacking InRelease files when run with
      the --debian-installer reporting flag.
      
      We had a previous fix that disabled some minor reporting functionality,
      however we now have a proper fix from upstream that addresses this
      problem fully.
      
      This commit replaces our fix with the official one from upstream.
      
      Many thanks are due to Patrick McDermott who implemented this for us!
      2a288b96
  12. 22 Jun, 2018 1 commit
  13. 19 Jun, 2018 1 commit
  14. 14 Jun, 2018 4 commits
    • Dr. David McBride's avatar
      Add gpg to the set of packages to install on a bootstrapped host · e0cb1b41
      Dr. David McBride authored
      Because we're now using the minimal variant when bootstrapping a host,
      it's now necessary to explicitly add gpg to the set of packages so
      installed; otherwise, it's not possible to run apt-key within the chroot.
      e0cb1b41
    • Dr. David McBride's avatar
      Stop installing login.defs prior to debootstrap · 376e77f9
      Dr. David McBride authored
      The login.defs file installed into /etc during the pre-configuration
      stage is no-longer required.  It's primary purpose was to ensure that
      newly created user accounts were allocated UIDs/GIDs in the reserved
      range 69000-69999, which doesn't collide with Jackdaw-allocated
      UIDs/GIDs.
      
      However, the adduser.conf file already installed is now sufficient,
      and pre-installing a login.defs file causes the unpacking of the 'login'
      package to fail at debootstrap time.
      
      (The tar invocation now used to unpack packages appears to abort in
       the event it tries to overwrite an existing file, unhelpfully!)
      376e77f9
    • Dr. David McBride's avatar
      Reorganise APT-related steps in preconfigure/installation/postconfigure · 6825a32d
      Dr. David McBride authored
      Because we're now installing a minimal bootstrap environment, we
      now need to install additional packages as part of the preconfigure
      install step before running the main installation.
      
      However, the previous installation scripts assumed that only it would
      need to install packages, and so the apt-setup steps took place there.
      
      Thus, to allow for installing additional packages in the /target chroot
      earlier (specifically to configure the timezone and locale of the new
      install), move the different steps in the above scripts around to
      make this practical.
      6825a32d
    • Dr. David McBride's avatar
      Use '--variant=minbase' when running debootstrap at install-time to avoid versioning error · f7fd5c80
      Dr. David McBride authored
      When running debootstrap inside the installation environment, it appears
      to automatically select an incompatible set of packages for automated
      installation.  (Specifically, the versions of python3-minimal and
      python3.6-minimal that it selects are mutually incompatible.)
      
      This appears to be caused by debootstrap running some relatively minimal
      package-selection code, and may be a consequence of running it against
      a mirror that contains multiple historical versions of the same set of
      packages.
      
      Work around this problem by passing the '--variant=minbase' argument
      to debootstrap, so that it only attempts to install the very minimum
      set of packages required.
      
      (So long as debootstrap constructs a minimal environment that can install
       additional packages, this is fine.)
      f7fd5c80
  15. 12 Jun, 2018 1 commit
  16. 05 Jun, 2018 4 commits
  17. 08 Sep, 2017 3 commits
  18. 06 Jun, 2017 1 commit
  19. 14 Mar, 2017 1 commit
  20. 25 Aug, 2016 2 commits