| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a write extension for making a package that can be used to
install the produced system. Ideally we'd instead have Baserock
everywhere to do the deployment, but we need to support this workflow
until that is possible.
It gets configured with a script templates that get filled in with the
paths to the rootfs tarball as @@ROOTFS_TAR_PATH@@, script directory as
@@SCRIPT_DIR@@ and copied boot-files as @@IMAGE_DIR@@.
Scripts to include are specified as a relative path to your morphologies
repository, separated by : characters in the INCLUDE_SCRIPTS variable.
If another separator is convenient, it can be specified in the
INCLUDE_SCRIPTS_SEPARATOR variable, which has the same semantics as the
shell IFS variable.
Other files needed to create the disk image, such as bootloader image
files can be specified in BOOTLOADER_BLOBS, relative to the root of the
rootfs, separated with similar rules to INCLUDE_SCRIPTS.
The name of the rootfs tarball, the scripts subdirectory and the
bootloader blobs subdirectory can be changed with the ROOTFS_TAR,
SCRIPT_SUBDIR and IMAGE_SUBDIR variables, but the default should be
sufficient.
The compression of the rootfs tarball, and the package tarball can be
specified by specifying a shell command that reads the uncompressed
tarball from stdin and writes to stdout in the ROOTFS_COMPRESS and
OUTPUT_COMPRESS variables.
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 3e73cebdb2ef8df99f416696d040e797b856cd24.
This patch was accidentally pushed without review as part of the
previous branch.
|
|\
| |
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
|
| |
| |
| |
| |
| | |
This is necessary for git.baserock.org, whose TROVE_PREFIX and TROVE_ID is
'baserock' but whose hostname certainly isn't.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Many users will have downloaded images from git.baserock.org and set them
up manually, so do not have an existing cluster morphology to upgrade with.
This gives them a hint on how to use the Baserock upgrade mechanism.
You can only use this mechanism from Baserock 14 onwards.
|
|\ \
| |/
|/|
| |
| | |
Reviewed-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
Reviewed-by: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| | |
|
|/
|
|
|
| |
This worked for busybox's grep, since it treats all files as text anyway
and ignores the option.
|
|\
| |
| |
| |
| |
| | |
Reviewed-By: Richard Ipsum <richard.ipsum@codethink.co.uk>
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Lars Wirzenius <richard.maw@codethink.co.uk>
|
|/
|
|
|
|
|
|
|
| |
This makes it easier to merge changes between /etc when doing upgrades.
Lorry and Mason config goes into local-config.git, not in /etc, so this
still needs to be done at first boot when we can run Gitano commands on
the target. For this reason the /etc/trove-setup.sed file is still
stored in the resulting system.
|
|
|
|
|
| |
The tarball repo is out of date and too old for the version of cxmanage
that we use.
|
|
|
|
| |
The 'install-files' extension can achieve the same thing.
|
|
|
|
|
|
| |
While Calxeda seem obsolete, we still need to manage their kit.
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
|
| |
|
|
|
|
|
|
|
| |
This produces a shell installer blob, like shar or makeself, which
extracts the rootfs and configures it to use libraries inside the target
directory, rather than the host's, so it should work independently of
what the user has installed.
|
|
|
|
|
|
|
|
|
|
| |
This has a different stratum for tools required for the SDK that aren't
part of the toolchain, to keep the dependencies low, since there's other
tools required on the horizon, and building the cross compiler has fewer
dependencies than patchelf.
I will fix the repo and ref for patchelf after merge to be from
git.baserock.org
|
| |
|
|
|
|
|
|
|
|
| |
The generated /etc/trove-setup.sed script, used to set up site
configuration for a deployed Trove on first-boot by trove-early-setup,
did not specify the 'g' (global) flag which meant that lines with more
than one occurance of a placeholder such as ##TROVE_HOST## were not set
correctly.
|
|
|
|
|
| |
This works as a chroot you can cross compile binaries to armv7lhf from,
provided you don't minimal tooling.
|
|\
| |
| |
| | |
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| |
| |
| |
| |
| |
| | |
It's hard to spot the 'reboot' command at the bottom of the list of
commands and it's a non-standard thing to do. This change should make it
more obvious what goes on during Trove first boot.
|
| |
| |
| |
| |
| |
| | |
If /var is a subvolume then we cannot access it until local-fs.target
has completed, and certainly we can't expect it to be around when systemd
is deciding what units to execute.
|
|/
|
|
| |
The trove-early-setup configuration tool is for initial deployment only.
|
| |
|
|\ |
|
|/ |
|
|
|
|
| |
This is the new canonical ordering.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Merge Dan Firth's branch to make all local repos and refs be 'null',
which means 'look in the local repository'.
Reviewed-By: Lars Wirzenius (on IRC)
|
| |
| |
| |
| | |
repo:null respectively
|
|\ \
| |/
|/|
| | |
Reviewed-by: Lars Wirzenius
|
| | |
|
|/ |
|
| |
|
| |
|
|\ |
|
|/ |
|
|\
| |
| |
| |
| |
| | |
Reviewed-by:
Ben Brown
Daniel Silverstone
|
| | |
|
|\ \
| | |
| | |
| | | |
Reviewed-by: Daniel Silverstone
|
| | | |
|
| |/ |
|
|\ \
| |/
|/| |
|
|/
|
|
| |
upstream tags
|
|\
| |
| |
| | |
Reviewed-by: Lars Wirzenius
|
| | |
|
|/ |
|
|\ |
|