summaryrefslogtreecommitdiffstats
path: root/config/binary_local-hooks
Commit message (Collapse)AuthorAgeFilesLines
* Fix regression in time-based snapshots, introduced when adding support for ↵intrigeri2016-05-141-2/+4
| | | | tagged snapshots.
* Don't try to temporarily enable deb-src for torproject from tagged APT ↵intrigeri2016-05-141-2/+2
| | | | snapshots either.
* Don't try to fetch deb-src for torproject, bis.intrigeri2016-05-111-0/+2
|
* Merge remote-tracking branch 'origin/devel' into feature/jessieanonym2015-08-052-28/+94
|\ | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: features/images/I2P_router_console.png features/images/TailsInstallerNoDevice.png features/images/TorBrowserAddressBar.png features/images/USBSuggestsInstall.png features/images/UnsafeBrowserAdvancedSettings.png features/images/UnsafeBrowserEditPreferences.png features/images/UnsafeBrowserProxyRefused.png features/images/UnsafeBrowserWindow.png features/step_definitions/unsafe_browser.rb
| * Merge remote-tracking branch 'origin/bugfix/9748-revert-apt-amd64' into develanonym2015-08-051-28/+7
| |\ | | | | | | | | | Fix-committed: #9748
| | * Revert inclusion of syslinux:amd64 in the ISO.intrigeri2015-07-291-28/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was introduced (#9381) for reasons that ended up being wrong (#9594). Here, we also remove amd64 APT sources and dpkg's support for amd64 as a foreign architecture. We'll need them again when we want to ship Linux 4.x, but once we're there we can perhaps enable amd64 sources only for selected APT repositories, to avoid re-introducing #9381. Reverts: e9d2e345fc931c59e84ab8064306356a32e5f07b 181c6d268d0f43d7ca8869eab295887f2422036b e1d331aa9a06b4a115f9f2aee713ea6a40d3e3d8 Will-fix: #9748
| * | Merge remote-tracking branch 'origin/devel' into feature/8471-32-bit-UEFIintrigeri2015-07-071-9/+30
| |\ \ | | |/
| * | Load GRUB2 video modules at runtime, and set linux_gfx_mode.intrigeri2015-05-081-2/+2
| | | | | | | | | | | | | | | | | | | | | It's what Debian's default GRUB configuration does. This fixes screen freezing after the switch to inteldrmfb, at least on the Toshiba Encore 2 WT8-1 tablet. Refs: #8471
| * | Install a 32-bit GRUB EFI boot loader, with an initial hand-made configuration.intrigeri2015-05-081-0/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ideally: * either this configuration should be generated automatically from the syslinux one; * or, we should use GRUB's syslinux_configfile command (from the syslinuxcfg module) to load and interpret the syslinux configuration; * or, worst case, we should have a documented process to update the GRUB configuration whenever we change anything that affects the syslinux one. Also, this initial configuration has some drawbacks: * it has a security issue, see XXX in grub.cfg; * the failsafe mode is incomplete, because I currently need that one to debug stuff. Refs: #8471
| * | Revert "Also install the syslinux 32-bit UEFI boot loader."intrigeri2015-05-081-28/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 441892f6197efbe014cfb54fc6f9d43ed7e425bb. The two 32-bit UEFI systems I've tried booting on only support the fallback UEFI path, that's not an option for us with 32-bit syslinux UEFI, as explained in the commit we're presently reverting. I also tried, and failed, to convince GRUB2 installed in the fallback location (EFI/BOOT/bootia32.efi) to chainload into 32-bit syslinux UEFI. So I'm giving up with using syslinux for 32-bit UEFI. Refs: #8471
| * | Also install the syslinux 32-bit UEFI boot loader.Tails developers2015-05-081-7/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note that we install it in BOOT/TAILS32 (while the 64-bit boot loader lives in the BOOT/EFI fallback directory), since syslinux module files have the same name regardless of the architecture, so we cannot simply put them all in the same directory. The drawback is that some buggy UEFI firmware may pick the wrong bootloader, that's not made for their architecture. Or, that they present the user with confusing choice between "EFI" and "TAILS32". We'll see. Of course, alternatively we could try to rename the 32-bit module files, so we can put them in BOOT/EFI as well; this would require adjusting the configuration files accordingly, in order to 1. load the 32-bit modules when the UEFI firmware is 32-bit; and 2. convince syslinux to load a different configuration file depending on the UEFI firmware's architecture (*not* the CPU architecture, beware!). Refs: #8471
* | | Merge branch 'feature/9381-ship-amd64-syslinux' into feature/jessieintrigeri2015-07-041-9/+30
|\ \ \ | | |/ | |/|
| * | Include a syslinux 64-bit binary in the ISO filesystem.intrigeri2015-06-121-7/+28
| | | | | | | | | | | | Will-fix: #9381
| * | Make section headings in comments more visible.intrigeri2015-06-121-3/+3
| |/
* | Merge branch 'devel' into feature/jessieintrigeri2015-02-261-0/+2
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: auto/build config/chroot_apt/preferences config/chroot_local-packageslists/tails-common.list config/chroot_local-patches/gdm-background.diff features/images/UnsafeBrowserStartVerification.png features/step_definitions/apt.rb features/step_definitions/evince.rb po/POTFILES.in wiki/src/contribute/design/memory_erasure.mdwn wiki/src/support/known_issues.mdwn
| * Merge remote-tracking branch 'origin/bugfix/8756-repair-local-packages' into ↵Tails developers2015-02-101-0/+2
| |\ | | | | | | | | | | | | | | | devel Fix-committed: #8756
| | * Don't attempt to retrieve source packages from local-packages (Will-Fix: #8756).Tails developers2015-01-211-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | live-build does not include source packages in the index of locally available packages. This makes since, since we don't include deb-src lines for other repositories. And then, as reported on https://labs.riseup.net/code/issues/8724#note-12, whenever ones uses the config/chroot_local-packages feature, the build fails. Therefore, when we generate temporary deb-src entries, skip the repository that indexes locally available packages. This should only be problematic if one wants to provide the syslinux source package there, which is unlikely, and in any case way less important than repairing config/chroot_local-packages for the general case (binary packages).
* | | Merge branch 'bugfix/8715-build-system-independent-APT-sources' into ↵Tails developers2015-01-211-2/+0
|\ \ \ | |/ / | | | | | | feature/jessie
| * | Switch to tor+http:// APT sources at boot time instead of at build time ↵Tails developers2015-01-191-2/+0
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (Will-Fix: #8715). live-build expects to be the only one that manages APT sources. Since feature/8194-APT-socks was merged, we're breaking this assumption of its, by mangling APT sources under live-build's feet via chroot_local-hooks. More specifically, if: * $LB_MIRROR_CHROOT != $LB_MIRROR_BINARY or $LB_MIRROR_CHROOT_SECURITY != $LB_MIRROR_BINARY_SECURITY, as is the case when building with Vagrant or when following our manual build setup instructions accurately (live-build defaults to ftp.de.debian.org for some of its APT configuration), or: * one has dropped .deb's in config/chroot_local-packages, as contributors without write access to our APT repository may want to do, then after completing the chroot_local-hooks stage, lb_chroot_sources would rewrite APT sources to match what we have previously configured (see the check at lines 490-498 in live-build 2.x tree), and therefore the ISO image would have http:// URLs configured instead of the expected tor+http://. Therefore, let's mangle APT sources configuration at boot time instead.
* | Merge remote-tracking branch 'origin/devel' into feature/jessieTails developers2015-01-011-3/+2
|\ \ | |/ | | | | | | | | | | | | Conflicts: config/chroot_apt/preferences config/chroot_local-hooks/52-update-rc.d config/chroot_local-includes/etc/polipo/config config/chroot_local-patches/torsocks_gobby-0.5.patch
| * Adjust hook that includes syslinux in the ISO filesystem to APT being moved ↵Tails developers2014-11-031-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from HTTP to SOCKS. Don't run apt-get update in the chroot again after reconfiguring APT sources for runtime. This is broken by the move to torsocks. Back when we used a HTTP proxy, the HTTP_PROXY environment variable passed by the build environment was overriding the APT proxy configured for runtime. This is not the case anymore, and now that APT run tries to use both the tor+http shim and the HTTP proxy used in the build environment, which is rejected by torsocks. Besides, the build process works just fine without this "apt-get update" run, so let's just drop it.
| * Merge branch 'devel' into bugfix/7173-upgrade-syslinuxTails developers2014-08-251-0/+2
| |\
| * | Adapt syslinux EFI bootloader path to cope with changes in the Debian package.Tails developers2014-07-141-1/+1
| | |
* | | Remove/adjust a bunch of Wheezy-specific hacks and comments.Tails developers2014-11-201-1/+1
| | |
* | | Adjust syslinux.efi path to match the one in syslinux-efi 3:6.03~pre20+dfsg-4.Tails developers2014-09-271-1/+1
| |/ |/|
* | Disable runtime APT proxy configuration when using APT in binary_local-hooks ↵Tails developers2014-07-311-0/+2
|/ | | | | | | | | (Closes: #7691). If we don't do this, APT can't download lists from the Internet. And then, in some situations, it lacks the information needed to install dpkg-dev. I'm not sure why it can even work in some other cases, but in any case, this hook makes oh so much sense to me with this modification.
* Include syslinux.exe for win32 in utils/win32/ on the ISO filesystem.Tails developers2014-06-251-1/+21
| | | | | | | | The APT config mangling is made in the chroot, as that's where all keys corresponding to the configured APT repos can be found, and the APT pinning has been setup. Note that, when this hook runs, the SquashFS has been generated already, so modifying the content of the chroot at this point should not affect the resulting ISO much.
* Use Linux-specific variable names.Tails developers2014-06-241-3/+3
|
* Include the syslinux binary, and its MBR, in the ISO filesystem.Tails developers2014-06-131-0/+33
| | | | | This in turn allows Tails Installer to use this binary and MBR, which is critical for avoiding problems (such as #7345) on "Upgrade from ISO".
* Merge branch 'devel' into feature/uefiTails developers2014-04-071-0/+3
|\
| * Remove useless syslinux configuration files that break incremental upgrades ↵Tails developers2014-04-051-0/+3
| | | | | | | | on Wheezy (Closes: #7025).
* | Workaround syslinux menu display bugs in UEFI mode (Closes: #6576).Tails developers2014-02-271-0/+1
| |
* | Install an icon for rEFInd (Closes: #6529).Tails developers2013-12-211-0/+1
| |
* | Install some COM32 syslinux modules into the syslinux directory.Tails developers2013-12-211-0/+38
| | | | | | | | | | Else, with syslinux 6.x, the boot fails with "ldlinux.c32 not found" and similar.
* | Run 20-syslinux_detect_cpu with "set -e" too.Tails developers2013-12-211-0/+2
| | | | | | | | | | We do this for all our other hooks, and I have just seen a case when it silently broke.
* | Install the syslinux UEFI bootloader.Tails developers2013-12-211-0/+38
|/ | | | | | | | | | This requires to: 1. Copy files around for compatibility between live-build 2.x and syslinux 3:6.03~pre1+dfsg-1. Ugly, yes. 2. Install isolinux and syslinux-common explicitly, since it is the ones that ship isolinux.bin and the *.c32 modules in syslinux 6.x packaging, and are merely recommends.
* Use the 486 kernel on 32-bit CPU with PAE.Tails developers2013-12-121-1/+1
|
* Install amd64 kernel instead of 686-pae one: a 64-bit kernel will be ↵Tails developers2013-12-021-5/+5
| | | | required for UEFI boot on 64-bit hardware.
* Merge branch 'bugfix/make_paths_relative_in_syslinux' into develTails developers2012-10-261-0/+2
|\
| * Remove the last absolute path in our SYSLINUX configTails developers2012-10-261-0/+2
| |
* | Merge branch 'devel' into feature/multikernelTails developers2012-09-291-0/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | Conflicts: config/chroot_local-hooks/50-virtualbox config/chroot_local-hooks/52-update-rc.d config/chroot_local-includes/etc/init.d/tails-wipe-memory-on-media-removal vagrant/provision/assets/build-tails
| * | Catch more errors in local hooksTails developers2012-09-231-0/+2
| |/ | | | | | | | | Ensure that all local hooks start with 'set -e'. This should prevent errors to slip through the build process.
* | Install ifcpu64.c32 from live-build's chroot.Tails developers2012-09-111-1/+16
| | | | | | | | | | | | We don't want to install it from the build system since the syslinux versions may differ, introducing subtle desynchronization induced breakage.
* | Replace syslinux menu with entries that autodetects the best kernel and boot it.Tails developers2012-09-041-0/+87
|/
* syslinux: workaround bug #650979Tails developers2012-05-121-0/+7
|
* syslinux: custom menuTails developers2012-05-111-2/+14
|
* Remove syslinux language choosing menu.Tails developers2012-03-091-133/+0
| | | | | This branch is about using syslinux to select other kind of options. tails-greeter allows choosing a !English language.
* Append a space, after the locales settings, on the kernel command line.Tails developers2012-03-051-1/+1
|
* Better keyboard layout for Farsi.Tails developers2011-12-081-1/+1
| | | | This is according to an Iranian Tails user.
* Make the language selection menu's position and size adapt itselfTails developers2011-10-191-0/+5
| | | | according to the number of items in it.