| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
these changes were generated with nixq 0.0.2, by running
nixq ">> lib.mdDoc[remove] Argument[keep]" --batchmode nixos/**.nix
nixq ">> mdDoc[remove] Argument[keep]" --batchmode nixos/**.nix
nixq ">> Inherit >> mdDoc[remove]" --batchmode nixos/**.nix
two mentions of the mdDoc function remain in nixos/, both of which
are inside of comments.
Since lib.mdDoc is already defined as just id, this commit is a no-op as
far as Nix (and the built manual) is concerned.
|
|
lxd-container-image: set mode of configuration.nix
|
|
|
|
|
|
nixos/lxd: use networkd for DHCP/RA
|
|
I am actively working on bringing back Amazon Images for 24.05.
Please track progress in https://github.com/nixos/amis
|
|
Enables networkd instead of dhcpcd for DHCP/RA. It offers a solid base
for network configuration, that is much more extensible than dhcpcd and
also better maintained than our bespoke `networking.interfaces` modules.
Closes: #287269
|
|
before:
```
[root@nixos:~]# ls -la /etc/nixos
total 16
drwxr-xr-x 2 root root 4096 Feb 8 00:51 .
drwxr-xr-x 16 root root 4096 Feb 8 00:51 ..
-r--r--r-- 1 root root 605 Feb 8 00:51 configuration.nix
-rw-r--r-- 1 root root 150 Feb 8 00:51 lxd.nix
```
after:
```
[root@nixos:~]# ls -la /etc/nixos
total 16
drwxr-xr-x 2 root root 4096 Feb 8 00:50 .
drwxr-xr-x 16 root root 4096 Feb 8 00:50 ..
-rw-r--r-- 1 root root 605 Feb 8 00:50 configuration.nix
-rw-r--r-- 1 root root 149 Feb 8 00:50 lxd.nix
```
|
|
|
|
openstack-image-zfs and make-single-disk-zfs-image: optionally specify qemu instance memory
|
|
|
|
Otherwise it results in <nixpkgs/nixos/modules/modules...> being loaded
|
|
Increase 'ramMB' to avoid OOM errors when building images.
Signed-off-by: Sirio Balmelli <sirio@b-ad.ch>
|
|
Use modulesPath so we don't have to magically rewrite paths in activation script,
set stateVersion to the one this was built with (which should approximate "first install")
|
|
We should really have the user set it, or at least have a warning.
|
|
|
|
|
|
|
|
|
|
Add image configuration for Oracle Cloud Infrastructure and scripts to
build and upload the image as a Custom Image.
|
|
|
|
aarch64 no longer fits in 2GB, blocking channel updates
|
|
|
|
With lib is bad: removes `with lib;` occurrences - part I
|
|
|
|
|
|
|
|
|
|
instead of qemu (all arches)
|
|
qemu (all arches)
|
|
According to the Unicode Standard, you should use U+2019 RIGHT SINGLE
QUOTATION MARK for apostrophes [1]. Before this change, some of the text
in this repo would use U+2018 LEFT SINGLE QUOTATION MARKs instead.
[1]: https://www.unicode.org/versions/Unicode15.0.0/ch06.pdf#G12411
|
|
|
|
Paravirtualized EC2 instances haven't been supported since 2017.
It's safe to remove this now.
|
|
most of these are hidden because they're either part of a submodule that
doesn't have its type rendered (eg because the submodule type is used in
an either type) or because they are explicitly hidden. some of them are
merely hidden from nix-doc-munge by how their option is put together.
|
|
conversions were done using https://github.com/pennae/nix-doc-munge
using (probably) rev f34e145 running
nix-doc-munge nixos/**/*.nix
nix-doc-munge --import nixos/**/*.nix
the tool ensures that only changes that could affect the generated
manual *but don't* are committed, other changes require manual review
and are discarded.
|
|
|
|
Add all currently available AWS regions
|
|
- Make tests/lxd.nix use NixOS's lxdMeta & lxdImage to avoid relying on
3rd party containers such as Alpine Linux for testing purposes.
- Merge tests/lxd-image.nix into tests/lxd.nix, since now both have a
similar structure.
- Extract duplicated inline LXD configuration into a separate file,
- Add passthru.lxd-nftables & passthru.lxd-image-server.
|
|
expressions down
|
|
Drops the wrong expandOnBoot option (defaults to all) and mark ZFS as enabled.
|
|
|
|
|
|
|
|
|
|
iteration time
|
|
Format and remove unnecessary `with lib;`.
|
|
The `nix.*` options, apart from options for setting up the
daemon itself, currently provide a lot of setting mappings
for the Nix daemon configuration. The scope of the mapping yields
convience, but the line where an option is considered essential
is blurry. For instance, the `extra-sandbox-paths` mapping is
provided without its primary consumer, and the corresponding
`sandbox-paths` option is also not mapped.
The current system increases the maintenance burden as maintainers have to
closely follow upstream changes. In this case, there are two state versions
of Nix which have to be maintained collectively, with different options
avaliable.
This commit aims to following the standard outlined in RFC 42[1] to
implement a structural setting pattern. The Nix configuration is encoded
at its core as key-value pairs which maps nicely to attribute sets, making
it feasible to express in the Nix language itself. Some existing options are
kept such as `buildMachines` and `registry` which present a simplified interface
to managing the respective settings. The interface is exposed as `nix.settings`.
Legacy configurations are mapped to their corresponding options under `nix.settings`
for backwards compatibility.
Various options settings in other nixos modules and relevant tests have been
updated to use structural setting for consistency.
The generation and validation of the configration file has been modified to
use `writeTextFile` instead of `runCommand` for clarity. Note that validation
is now mandatory as strict checking of options has been pushed down to the
derivation level due to freeformType consuming unmatched options. Furthermore,
validation can not occur when cross-compiling due to current limitations.
A new option `publicHostKey` was added to the `buildMachines`
submodule corresponding to the base64 encoded public host key settings
exposed in the builder syntax. The build machine generation was subsequently
rewritten to use `concatStringsSep` for better performance by grouping
concatenations.
[1] - https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md
|
|
|
|
This is important since legacy bios mode is still the default for Intel
and AMD based instances on AWS. That is, even if your image is setup to
use UEFI on the OS level, the AMI will still use BIOS unless the boot
mode is explicitly set during registration.
|
|
|
