| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Back then when I added the font pack in 0171f8d895efd46300ba01c6adeb7aa,
version 2.0 was not yet merged to nixpkgs. This has happened in the
meantime and the current version is version 2.2 and I also do not see
any reason to keep the 2.0 version in Vuizvui.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After countless boots with unlocking my LUKS containers and thereafter
logging in via lightdm I started to wonder whether it really makes sense
to do the latter.
All of my workstations are single-user, I usually don't switch my
session type (and even if, then via system configuration) and if someone
manages to unlock my LUKS containers, it's really trivial to circumvent
the user authentication.
So if I'm not forgetting about something big[TM], the only purpose this
additional auth serves is me being annoyed for no reason, so let's
disable it if the configuration indicates that LUKS is used.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
With my new laptop, a font size of 12pt is rather large and given that
hidpi displays usually have a quite large resolution (the name might
hint at that), we don't necessarily need to use embedded bitmaps anymore
which was one of the reasons why I used a point size of 12.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After resume from suspend the NVMe does not wake up again when the
device was put into D3cold. This is something that is worked around by
TUXEDO Tomte[1] via udev rules. However, I personally don't like this
approach and it can lead to race conditions when we're going into
suspend before udev is initialised.
Interestingly, the device does even go into NPSS via APST, but if
changing to D3cold while APST is enabled, the device does not wake up
again.
Right now I just added a new quirk to disable D3cold during device
probe for now, but we could maybe find a better workaround eg. by
disabling APST before D3cold and re-enabling it again. Not sure whether
this is feasible, but since I have limited time right now I can't dig
more into this.
[1]: https://github.com/tuxedocomputers/tuxedo-tomte/commit/2c8d71170868a2663705fbea6ac150eecb96e6ce
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
We only want to highlight #aabbcc-style hex colors and not every damn
hex value that happens to be 3 or 4 bytes, which is very annoying when
you're doing a lot of bit manipulation.
Additionally, I currently have a code base where "gold" is something a
player can have, so one doesn't need much imagination on how irritating
that is.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The config we're baking in by default relies on Nightly features, so it
only makes sense to actually use a rustfmt version that supports it.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
Seems like something got more strict about setup hook execution and the
relevant env vars for gi weren't set in checkPhase.
|
|
|
|
| |
This stopped working for me for some reason, so no point in keeping it
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of the options in nix.conf are now exposed as a submodule with a
freeform type and since that change[1] got introduced, we get a bunch of
warnings during machine evaluation:
trace: warning: The option `nix.useSandbox' defined in `...' has been renamed to `nix.settings.sandbox'.
trace: warning: The option `nix.maxJobs' defined in `...' has been renamed to `nix.settings.max-jobs'.
trace: warning: The option `nix.buildCores' defined in `...' has been renamed to `nix.settings.cores'.
To shut them up, I went through all machines and modules and renamed the
remaining options that were not renamed back then when @devhell did some
renames in a0297bf921399c3243dcca99626d8697f0735abe.
This was done by looking through the output of:
$ git grep -A 10 '\<nix\(\.\| *=\)' machines modules
After that I tested the contents of the nix.conf of all the machines
against the changes this commit introduced via the following command:
$ nix-build --no-out-link -E '
with import <nixpkgs/lib>;
map (m: m.eval.config.environment.etc."nix/nix.conf".source)
(collect (m: m ? eval) (import ./machines))
'
I've sorted the resulting nix.conf files and diffed on that result and
the only difference that showed up was the following:
allowed-users = *
-auto-optimise-store = false
auto-optimise-store = true
builders-use-substitutes = true
cores = 0
This is because the previous way to generate the config was by
concatenating strings whereas the new way works on an attribute set, so
we get deduplication by design.
[1]: https://github.com/NixOS/nixpkgs/pull/139075
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
Cc: @Profpatsch
Cc: @sternenseemann
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We no longer need to use extraPostFetch in order to append stuff to
the postFetch phase of fetchzip. Since this got fixed[1], we now get
appropriate warnings during evaluation:
warning: use 'postFetch' instead of 'extraPostFetch' with 'fetchzip'
and 'fetchFromGitHub'.
Neither do we like warnings nor do we like to use workarounds from the
past that got fixed, so let's fix it on our side as well :-)
[1]: https://github.com/NixOS/nixpkgs/pull/173430
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
I use perf on a regular basis and since it's dependant on the currently
running kernel version, it' just makes sense to have it available at all
times rather than "nix run" it with the right kernel version.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I already killed that machine on 2022-08-04:
tishtushi[~]0> cryptsetup erase /dev/sda2
WARNING!
========
This operation will erase all keyslots on device /dev/sda2.
Device will become unusable after this operation.
Are you sure? (Type 'yes' in capital letters): YES
tishtushi[~]0> cryptsetup erase /dev/sda3
WARNING!
========
This operation will erase all keyslots on device /dev/sda3.
Device will become unusable after this operation.
Are you sure? (Type 'yes' in capital letters): YES
Since some of the hardware was already broken (touchpad, keyboard, HDD,
SSD and webcam), I hardly doubt that I'll use it again so it makes sense
to remove the config here.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The package has been removed and we're getting the following eval error:
error: 'docker-edge' has been removed, it was an alias for 'docker'
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now we're getting an eval error like this:
Failed assertions:
- You have set services.power-profiles-daemon.enable = true;
which conflicts with services.tlp.enable = true;
Since the machines in question are for desktop environment users, TLP
doesn't make a lot of sense. Besides, the option should not be defined
in managed.nix anyway, because it's a hardware-specific option.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The machine no longer exists, so it doesn't make sense to continuously
build it on Hydra.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upstream project seems to be no longer maintained[1] and the last
release from 2005 contains a whole bunch of outdated NIC information
so that it became pretty annoying to use.
Back then jwhois was the only whois client packaged in nixpkgs, so this
might be the reason why it ended up in my setup in the first place.
The "whois" package on the other hand seems to be actively maintained
and works well for the domains I care about.
[1]: https://github.com/jonasob/jwhois/issues/32
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The amdgpu module is initialised at roughly the same time as the X
server, which sometimes leads into race conditions where X won't start
because the kernel driver is not yet loaded.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
This is a custom kernel module for TUXEDO laptops, which allows to
control the backlight. I haven't played around with its settings yet,
but having the module available helps with that.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
This is needed for the GPU and the WiFi adapter.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
I'm used to a TypeMatrix keyboard, where caps lock is only a small key
on the side instead of being prominently placed atop switch.
Slylandro's internal keyboard however has that pesky caps lock key
directly atop the left shift key and I'm constantly triggering it by
accident.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is mainly for having a consistent and central way to define our
keybord config. The main reason for doing so is because of Slylandro,
which comes with a keyboard that has a caps lock key atop the left shift
key and it drives me mad.
Since I'd like to keep things DRY, let's just use XKB for everything
keymap-related.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
This makes the screen readable again, but might get us into trouble when
switching to an external display. Again, similar to enabling bonding in
the previous commit, let's find out :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
This is mainly because I want to have a seamless transition between
both, at least in theory. Whether this will work out to be so smooth
when trying it on various networks out there remains to be seen, but
let's try it :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've already got a temporary laptop back then where I used the same name
and I introduced it in e73fcff03faed773df2500965cb9c4a4fcfbc04d and
subsequently removed it in 240378dcec205b78b32c329ff02eb9bea8af2c11.
With the new permanent hardware having arrived today, I decided to reuse
the name, because it sounds nicer than "tishtushi" (which is my crappy
laptop) and I also like the Slylandro Probes[1] a lot in Star Control.
The configuration here is pretty much bare-bones as we had before with
the temporary hardware and it's essentially a remix between dnyarri and
the old config, more to refine later...
[1]: https://wiki.uqm.stack.nl/Probe
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Since libgit2 version 1.5.0, sysdir.c is in a subdirectory called
"libgit2", which was made to distinguish the sources from the ones in
the CLI tool and util.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The options in services.graphite.api and services.graphite.beacon got[1]
removed[2] in nixpkgs because the upstream project doesn't seem to be
maintained anymore.
More information can be found at:
https://github.com/NixOS/nixpkgs/pull/180950
[1]: https://github.com/NixOS/nixpkgs/commit/1f18d441063208968f38bed0fe5
[2]: https://github.com/NixOS/nixpkgs/commit/ada1d87767b8826ea6233952279
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
See https://github.com/NixOS/nixpkgs/pull/177318 for the lovely change
that causes your locales to disappear.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
I don’t know how I missed this, but my deploy script didn’t actually
set up a system profile, so rebooting would lead to (very) old
generations being activated again.
Thanks to @sternenseemann for the nix-env trick (via
https://code.tvl.fyi/tree/ops/nixos.nix#n55 )
|
|
|
|
| |
No! bad subvolume! bad!
|
|
|
|
|
|
| |
I had them copied from the wrong module, of course this can’t work.
Since the kernel config & boot loader config is now in thinkpad, this
might just work (famous last words).
|
|
|
|
|
| |
Not sure about the boot loader config, but I guess it’s okay for now,
since it doesn’t diverge anyway.
|
| |
|
| |
|
|
|
|
|
|
| |
I think the `null` still came from the nixpkgs module.
Not sure whether upower will like an empty config file, but we’ll see.
|
| |
|
| |
|
|
|
|
|
|
|
| |
I use all of that on a regular basis.
Earlyoom makes sense for any kind of machine without swap, which is
all of my machines.
|
|
|
|
|
| |
I want to have a thinkpad-based server, which will need the
thinkpad-specific stuff but none of the workstation stuff.
|
|
|
|
| |
Yay static linting.
|
|
|
|
|
|
|
|
| |
Not updating the microcode on thinkpads is kind of a death sentence
for some kernel updates, so let’s do it by default.
In case somebody uses it for an AMD thinkpad in the future, we might
have to check whether the option creates a problem.
|
|
|
|
|
|
| |
Apparently one of its python dependencies went EOL and everything went
to fuck because python is a crapfest and nixpkgs policies around it
are stupid. yay.
|
| |
|
|
|
|
|
| |
This is not pretty, some of the code lives in vuizvui, some lives in
tvl depot. But at least it seems to work for now :)
|
|
|
|
| |
though the backup service is broken on the machine anyway, idk
|
| |
|