calamares

Commit Graph

Author	SHA1	Message	Date
Adriaan de Groot	1a557804ab	REUSE: Remainder of data/ - AppImage example config: this is old AppImage configuration, basically unmaintained, but copied from the other example config files which are CC0-1.0 as well. - Sample Linux distro: The example Linux distro has a handful of trivial files, a bogus `/etc/issue`, that kind of thing. - The bash completions are GPL-3.0-or-later - FreeBSD packaging information is BSD-2-Clause	6 years ago
Adriaan de Groot	bba9651850	Create example distro squashfs (from build host) - Add a target 'example-distro' which must be manually invoked This creates an example.sqfs with a minimal binary distro based on the build hosts's /bin and /lib. The purpose is to provide a simple test image which the default configuration of the unpackfs module can use to create a system within which the other steps of the installation can run. Example files are some zoneinfo's (remember to choose an existing zone when using the example distro), groups and sudoers files, etc .. The example distro has a special /xbin which contains bogus binaries for many system-administration tasks (e.g. useradd which would otherwise come from /usr/sbin).	9 years ago

Author

SHA1

Message

Date

Adriaan de Groot

1a557804ab

REUSE: Remainder of data/

- *AppImage example config*: this is old AppImage configuration,
  basically unmaintained, but copied from the **other** example
  config files which are CC0-1.0 as well.
- *Sample Linux distro*: The example Linux distro has a handful
  of trivial files, a bogus `/etc/issue`, that kind of thing.
- The bash completions are GPL-3.0-or-later
- FreeBSD packaging information is BSD-2-Clause

Adriaan de Groot

bba9651850

Create example distro squashfs (from build host)

- Add a target 'example-distro' which must be manually invoked
   This creates an example.sqfs with a minimal binary distro
   based on the build hosts's /bin and /lib.

The purpose is to provide a simple test image which the
default configuration of the unpackfs module can use to
create a system within which the *other* steps of the
installation can run.

Example files are some zoneinfo's (remember to choose an
existing zone when using the example distro), groups and
sudoers files, etc ..

The example distro has a special /xbin which contains bogus
binaries for many system-administration tasks (e.g. useradd
which would otherwise come from /usr/sbin).

2 Commits (e4e041df7e3bf04f3a8b6a30a7ff40681764ac03)