| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Who'd have thought. Work has finally embraced a way of printing no
matter what OS one runs. What a time to be alive.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I already have this running in writethrough for long enough so that I'm
pretty confident that a disaster like last time[1] should not happen
anytime soon so that hereby I'm making this permanent in the machine
configuration.
The reason why I set this to writearound initially instead of
writethrough, was that I just wanted to go with the most conservative
option first.
Of course, during scrub, we still disable all caching, so we should not
generate too much wear on the SSD.
[1]: 15008e69542774c441e388ad4c2e28a2d27f9ba0
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
I'm finding myself use containers more and more these days, primarily
for testing stuff, so it's useful to have the tools installed.
|
|
|
|
|
|
| |
Trying to figure out a better, more consistent approach to theming my
terminals and terminal programs, so let's start from scratch and remove
as much as possible.
|
|
|
|
| |
Let's see if this does anything good.
|
|
|
|
|
| |
As I move from one machine to another I'll be removing SpaceVim and
enabling my Vim.
|
|
|
|
|
|
| |
This is in preparation of me leaving SpaceVim behind and not having to
rely on external sources for certain programs, such as Vim, when
installing a new machine.
|
|
|
|
|
| |
I really love the screensavers, but unfortunately more often than not
it's hugely distracting for my mode of work.
|
|
|
|
|
| |
We've finally arrived in the 21st century and don't require a proxy
anymore. Hurrah!
|
|
|
|
|
|
|
|
|
|
| |
IWD seems to have an issue with the re-configured eduroam I frequently
use. Every other OS has no issues with the new configuration, only IWD
does. They did some background work on the CA cert, and even gave me the
public CA PEM to integrate in the configuration directly, and yet IWD
complains of `bad_certificate`. I don't have time to dig deeper, so I'm
switching to `wpa_supplicant` again until I have time to test it again
with a newer version of IWD.
|
|
|
|
|
|
|
|
|
| |
alock is really bad locking software. It is slow, it becomes
transparent, it even crashes sometimes. All the things a good lock
screen should never do.
i3lock is the trusted “standard” featureless locksceen, so this switch
has been procrastinated for way too long.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was one of the places where types.loaOf was still in place and it
got removed a while[1] ago and this in turn causes evaluation to fail
for quite a few machines:
The option value `boot.initrd.luks.devices' in `...' is not of type
`attribute set of submodules'.
I've not only changed all the machines to use attribute sets but also
fixed the check in core/tests.nix, because comparing against a list when
the actual type is an attribute set will result in all the LUKS tests to
be part of *all* channels, no matter whether you're actually using LUKS.
[1]: https://github.com/NixOS/nixpkgs/commit/20d491a317d9956ddca80913f07
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
Cc: @sternenseemann
|
|
|
|
|
|
|
|
| |
I've had this laying around in my configuration.nix since quite a while,
but today is one of those days where I can't stand all the cruft piling
up there anymore and decided to add it here.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
A bit more cleanup.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a step towards a saner deployment for these machines.
The NIX_PATH is fixed, so that everything on the running system always
uses exactly the nixpkgs version the system was deployed with.
The deployment is done by copying the system closure and switching to
it via the `bin/switch-to-configuration` script.
Uses the reference to pkgs.path, and applies filterSourceGitignore on
the directory, since I often deploy from a local checkout which is
half a GB without the gitignore filter.
|
|
|
|
| |
used for access to /data/seeding
|
| |
|
|
|
|
| |
I've grown quite fond of this colorscheme. At least for now.
|
|
|
|
|
|
| |
Explicitely set default fonts for (sans)serif, monospace and emoji.
Add Noto Color Emoji as emoji font.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm using gPodder to follow a bunch of YouTube channels and the internal
extractor/downloader tends to be pretty unreliable.
On the other hand, youtube-dl is regularily updated and supports a ton
of different formats.
To make sure we can actually use the extension, gPodder needs to have
access to the youtube_dl Python module, so we need to add it to the
propagatedBuildInputs.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also add the service to legosi so I can use it from the weechat user.
|
| |
|
|
|
|
| |
No libpurple for just XMPP, phew.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While it's fine to use <nixpkgs> on most systems, we deliberately want
to avoid the use of <nixpkgs> to make sure that whenever we for example
run <nixpkgs/nixos/lib/eval-config.nix> with a custom "pkgs" argument we
are guaranteed that we get the version we specify.
So this is one of the reason I used <nixpkgsSrc> on Hydra instead of
<nixpkgs>, so that whenever we have such occasions where we can't
guarantee such things, the evaluation will fail.
And right now, it does:
in job 'machines.profpatsch.legosi':
file 'nixpkgs/nixos/modules/profiles/qemu-guest.nix' was not found in
the Nix search path (add it using $NIX_PATH or -I), at
.../machines/profpatsch/legosi.nix:12:5
Fortunately, there is modulesPath, which refers to
<nixpkgs/nixos/modules> of the nixpkgs version passed via "pkgs".
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
| |
Small Hetzner qemu virtual server.
|
| |
|
|
|
|
| |
Using the wrapper rather than normal.
|
|
|
|
| |
Kinda forgot that just adding the packages is probably not enough.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recently, the way to add scripts to the mpv wrapper has changed[1] and
instead of using .override, there is now a dedicated wrapMpv function
that can be used to compose the wrapped mpv derivation, similar on how
it's done for wrapFirefox and wrapNeovim.
The change also introduced the following evaluation error when using the
old mpv-with-scripts package:
Use wrapMpv for editing the environment of mpv
Since this evaluation error essentially blocks Vuizvui channel
generation, I decided to fix this, even though I usually try to avoid
touching other people's machine configurations.
[1]: https://github.com/NixOS/nixpkgs/commit/f93918bdc387d353285f458c06c6a111ae90b7b2
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
| |
We'll need these to replace docker.
|
|
|
|
| |
Still a continuation of some housekeeping.
|
|
|
|
|
| |
I think I'll switch to `podman` now. I was never a fan of docker needing
a daemon to begin with.
|
|
|
|
|
|
| |
This reverts commit 5557cd782a1ce6bcee0c907ba6349c13da2f82db.
Massive brainfart.
|
|
|
|
|
|
| |
Upstream changed `virtualisation.docker` to
`virtualisation.oci-container` in [1], so naturally we'll need to rename
it here too.
|
| |
|