| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
These are now blocked by university's network. *sigh*
|
|
|
|
|
|
|
| |
https://github.com/NixOS/nixpkgs/pull/58399 has been merged a few hours
ago, so we no longer need to use our manual override.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@466f5e534688049be2ed6e75ae5659633016b45e, libinput
is enabled by default for Plasma 5, so we no longer need to explicitly
enable it anymore.
Furthermore, there was brawndo as the only machine still using
Synaptics and it's about time it's using libinput as well, so I
subsequently removed synaptics there.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@c814d72b517bb201c8bbbfc64e386c7023352886, a lot of
packages now no longer have a name attribute but instead use pname, so
when checking the package name within allowUnfreePredicate we need to
make sure that we fall back to a default if the name attribute is not
present.
This fixes evaluation of the machine, however I didn't check if it
actually builds.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
I'm not really using it.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Most machines are Intel, but not all, therefore we must now apply CPU
microcode updates to different manufacturers explicitly. Something that
needs DRYing, yet again.
|
|
|
|
| |
Let's stick with Cloudflare's primary and secondary resolvers.
|
|
|
|
|
|
| |
Unfortunately gunnr can't access syncthing from its network, and so
there's no point in having it run. Looks ugly and needs to be DRY-ed at
some point in time, but that'll have to wait.
|
|
|
|
|
|
|
| |
Compton has been bumped to version 7, and with it the nix definition has
changed. Additionally to adopting the new options I'm also moving
compton to the overall services and have removed compton references from
each machine.
|
|
|
|
|
| |
Now that my shiny new TypeMatrix has arrived, we'll be using the
superior dvorak layout.
|
|
|
|
| |
This is better controlled via browser proxy settings.
|
|
|
|
| |
Never mind. This doesn't work, of course.
|
|
|
|
|
| |
When one travels with one's laptop, one does not wish to be disturbed by
having to manually configure a TZ. How plebish.
|
|
|
|
|
|
|
|
| |
I can't keep `offlineimap` as a service that applies to all, simply
because `gunnr` will never be able access IMAP from its network.
There's therefore little point in having it try to connect. So, instead
I've moved the service to all machines that are expected to be able to
access emails.
|
|
|
|
| |
Still not working properly.
|
| |
|
|
|
|
|
|
| |
Now that my machine landscape also includes AMD, having a blanket
`thermald` service running makes no sense. All Intel-based machines now
have a `thermald` service explicitly enabled instead.
|
|
|
|
|
| |
I've been wanting to test ZFS for a while now, and since 0.8 we have
stable encryption and TRIM support for SSDs.
|
|
|
|
| |
Everything is locked down, but thankfully we have an NTP running. Phew.
|
|
|
|
| |
Otherwise keyboard-controlled volume won't work.
|
|
|
|
|
| |
Makes little sense on this machine and only provokes weird behavior
obviously. Don't know why I even put it in the first place.
|
|
|
|
|
| |
Fails some tests on hydra right now and it's not very important for me
to have at the moment.
|
| |
|
|
|
|
| |
Brainfart.
|
|
|
|
|
|
|
| |
I'm bored of the names my machines have. Luckily NixOS makes changing
names as easy as changing underwear! So, let's use Valkyrie names
instead. Also, change the console font to something nicer, like the
default `Lat2-Terminus16` font!
|
|
|
|
|
|
| |
This is a new work machine. The configuration is based off of `titan`
and `skunkworks`. I expect there to be plenty of changes in the future
as I get accustomed to it and shape it to my needs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't recall the exact model which was used for that machine, but it
was definitely one that required version 5.70.
Now I made a pull request for nixpkgs a while ago[1], which hasn't been
merged and as I didn't have the chance to test it by myself I didn't
merge that pull request yet.
Since the user asked about that printer driver again, I decided to give
version 5.70 a shot in vuizvui only and merge it upstream, once the user
reports that the driver is working.
[1]: https://github.com/NixOS/nixpkgs/pull/58399
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Generates a wireguard configuration based on
https://nixos.wiki/wiki/Wireguard and sets up the iptables firewall in
a way that only enables forwarding between `eth0` and the `wg`
interfaces.
The standard NixOS firewall configuration allows `FORWARD` between all
interfaces, and `networking.nat.enable` enables the `ip_forward` rule
in the kernel, meaning packages can suddenly hop interfaces without a
firewall that `DROP`s forwards by default.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I've had these packages in here disabled in case I'd ever have to get
back to them. I've not had to for, what feels like, an eternity.
Additionally to slimming the config down, removing them will also
somewhat slim down closure size since Nix will build them anyway even
though they're not actively used.
|
|
|
|
|
|
| |
The previous commit was wrong in that it was not the correct way to
include the 'light' package. According to the manual, this is the
correct way.
|
|
|
|
|
|
| |
Since the 'modesetting' driver does not work with 'xbacklight' we have
the choice of either 'light' or 'backlightctl'. For now we'll choose
'light' and see how it goes.
|
|
|
|
|
| |
The release notes for NixOS 19.03 state that the 'intel' driver has
been superseded by the 'modesetting' driver.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This machine was used for controlling the LED lighting bars at
Rockfabrik. I no longer work there and the machine has subsequently been
replaced by something else, so I don't need kzerza anymore.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I did have a major outage this week, because I was using bcache with
writeback mode on a RAID10 backing storage. Fortunately, I was able to
recover 99.9% of the data (only the most recent stuff wasn't
recoverable), but I certainly don't want this to happen again in the
future.
While I did use bcache with hibernate and writeback, the interesting
part is that the caching device went bonkers after a "normal" shutdown
rather than a suspend/hibernate, with "normal" being "with a bunch of
kernel warnings about zswap". Also, this happened around a btrfs scrub,
so the inconsistency was all over the place.
So first of all, I'm now going with writaround mode rather than
writeback mode for the time being. Although it's slower than writeback,
the chances that I need to do such a recovery again is close to 0% with
writethrough and writearound because all writes are synchronous.
Second, this very change makes sure that whenever the machine goes to
sleep or a scrub is started, the caching is disabled and afterwards it's
re-enabled. That way we shouldn't have lots of trash on the caching
device.
Signed-off-by: aszlig <aszlig@nix.build>
|