1. 16 May, 2012 2 commits
    • Tails developers's avatar
      vagrant: Add task to create our squeeze basebox · aa541fd8
      Tails developers authored
      As we use Veewee to automate the creation of the basebox, we are forced to back
      up on the "do not execute Vagrant manually" stance. This is due to the fact that
      Veewee is quite hackish and itself calls `vagrant` directly. So we move our
      monkey-patching from the Rakefile to the Vagrantfile itself.
      
      In order to support an HTTP proxy, the `preseed.cfg` file that Veewee need is
      created beforehands in another Rake task. Proxies bound to localhost will
      result in a failure and an explicit error messages.
      
      Note: it is unfortunately not possible to use `definitions.rb` to add
      `mirror/http/proxy` to the installer command-line. As the defined proxy is
      set by network-preesed, it will prevent the installer from retrieving
      the preseed file provided by Veewee on a local interface.
      aa541fd8
    • Tails developers's avatar
      vagrant: Start a Rakefile to drive builds · 39737699
      Tails developers authored
      Build based on Vagrant will be drived using `rake`. This has the
      definite advantage that we can easily isolate Vagrant related files
      in the `vagrant` subdirectory while providing an easy access to build
      functions.
      
      This will also allow easier local customizations to Vagrant itself,
      as we will be able to mangle stuff in Rake before handing commands to Vagrant.
      
      The Rakefile currently only wraps a few Vagrant commands, it will be extended
      later on.
      39737699
  2. 25 Mar, 2012 1 commit
  3. 15 Dec, 2011 1 commit
  4. 09 Jul, 2011 1 commit
    • Tails developers's avatar
      Build and install documentation into the chroot. · 4cb04c88
      Tails developers authored
      Rationale: our static website cannot be copied to a FAT32 filesystem
      due to filenames being too long. Changing this would be a pain.
      Hence building and installing it into the chroot (-> filesystem.squashfs)
      rather than into the binary_local-includes (-> iso9660 / FAT32 filesystem).
      
      This means the documentation cannot be browsed offline from outside Tails.
      However, our installer creates GPT hidden partitions, so the doc would not be
      browseable from outside Tails anyway. The only usecase we really break by doing
      so is browsing the documentation while running a non-Tails system, from a Tails
      CD.
      4cb04c88
  5. 29 Apr, 2011 1 commit
  6. 28 Apr, 2011 1 commit
  7. 15 Apr, 2011 1 commit
  8. 01 Oct, 2010 1 commit
  9. 25 Sep, 2010 1 commit
  10. 22 Sep, 2010 1 commit
  11. 01 Jun, 2010 1 commit
  12. 04 Feb, 2010 1 commit
  13. 26 Jan, 2010 1 commit
  14. 08 Dec, 2009 1 commit
    • amnesia's avatar
      more improvements on boot time from CD · 2fdfe20a
      amnesia authored
       * Move boot profiler execution from runlevel S to initramfs to also gather
         files used during those many `live-bottom` scripts.
       * Make the boot profiler provide a ready to use sort list, now in
         /var/log/boot-profile.
       * Implement readahead. That needs real world tests before deciding if it's
         actually an improvment.
       * Backport bootchart from Ubuntu to get accurate measurements. Binary packages
         needs to be manually copied to be used.
       * Update sort list.
       * Update documentation.
      2fdfe20a
  15. 29 Nov, 2009 1 commit
  16. 24 Nov, 2009 1 commit
  17. 25 Aug, 2009 2 commits
  18. 24 Jun, 2009 1 commit
  19. 20 Jun, 2009 2 commits