| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This is a feature useful for nixos-remote and other installation tools
that try to identify if the remote machine has been successfully booted
into an installer.
|
|
… as suggested by @NiklasGollenstede in:
https://github.com/NixOS/nixpkgs/pull/206951#issuecomment-1369020601
This simplifies the user experience for logging into and
debugging the machine and also simplifies the instructions for
shutting down the machine gracefully.
|
|
This is preferable because it prevents things like disk corruption (requiring the user to delete the disk image when starting up) that I consistently ran into.
|
|
I was considering the broader context of stateVersion, but the
macos builder does not enable documentation, making this paragraph
a distraction.
|
|
The `system` argument is usually implied, and not hard to figure out.
Co-authored-by: Gabriella Gonzalez <Gabriel439@gmail.com>
|
|
|
|
See the discussion starting here:
https://github.com/NixOS/nixpkgs/pull/206951#issuecomment-1364760917
The `darwin.builder` derivation had a gratuitous dependency
on the current Nixpkgs revision due to
`config.system.nixos.revision`. Setting the revision explicitly
to null fixes this problem and prevents the derivation from being
rebuilt on every change to Nixpkgs.
|
|
The script was being mistakenly being built for the guest
system instead of the host system
|
|
See: https://github.com/NixOS/nixpkgs/issues/108984#issuecomment-1364263324
Before this change the supported platforms were unspecified, so
it would default to being only built on `x86_64-linux`. This
fixes that so that hydra.nixos.org builds and caches the Darwin
build products instead
|
|
Fixes https://github.com/NixOS/nixpkgs/issues/108984
This originates from:
https://github.com/Gabriella439/macos-builder
… which in turn originates from:
https://github.com/YorikSar/nixos-vm-on-macos
|
|
|
|
|
|
|
|
|
|
nixos/profiles/base: install vim w/nix-syntax plugin
|
|
Considering that you most likely edit Nix code in the installer, that
seems like a useful thing.
The size of the ISO I got from
nix-build nixos/release.nix -A iso_minimal.x86_64-linux
is still at 877M.
|
|
nixos/*: apply some lints from statix and nil
|
|
profiles: add HP Smart Array RAID scsi driver to all-hardware.nix
|
|
|
|
This saves about 25M from the closure size of:
$ nix build -f nixos system --arg configuration '
{ imports = [ ./nixos/modules/profiles/minimal.nix ];
fileSystems."/".label="root";
boot.loader.grub.device = "nodev";
}'
|
|
Fixes: 4cdda329f06 ("nixos/modules/profiles/base.nix: omit zfs if unavailable")
|
|
The `boot.zfs.enabled` option is marked `readOnly`, so this is the only way to
successfully build a NixOS installer image for platforms that zfs does not build
for.
Co-authored-by: Alyssa Ross <hi@alyssa.is>
|
|
This is image media, so use the override level designed for it. As
detailed in the definition for mkImageMediaOverride:
> image media profiles can be derived by inclusion into host config,
> hence needing to override host config, but do allow user to mkForce
|
|
|
|
profiles/all-hardware.nix: add reset-raspberry for USB on RPi 4
|
|
|
|
|
|
nixos: Installer tests for systemd stage 1
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
reduces size by about 1M
|
|
This is needed for USB to work on RPi 4. Kernel's defconfig demoted the
module from built-in to module in 5.14. See [1].
[1] https://lore.kernel.org/linux-arm-kernel/ab43364b-55cc-08e6-a647-6e50a1743f03@gmail.com/
|
|
|
|
The wpa_supplicant service in the NixOS installer is unusable because
the control socket is disabled and /etc/wpa_supplicant.conf ignored.
The manual currently recommends manually starting the daemon and using
wpa_passphrase, but this requires figuring out the interface name,
driver and only works for WPA2 personal networks.
By enabling the control socket, instead, a user can configure the
network via wpa_cli (or wpa_gui in the graphical installer), which
support more advanced network configurations.
|
|
nixos/systemd|filesystems: mount and evacuate /sys/fs/pstore using systemd-pstore
|
|
|
|
nixos/modules: add "sdhci_pci" to availableKernelModules
|
|
As described in issue #81138, the Install section of upstream units is
currently ignored, so we make it part of the sysinit.target manually.
|
|
|
|
Namely, early KMS on raspberry pi
|
|
|
|
|
|
While it's being brought in implicitly by the other analogix driver,
let's be explicit, in case things change.
|
|
But not exclusive to rockchip
|
