about summary refs log tree commit diff
path: root/modules
Commit message (Collapse)AuthorAgeFilesLines
...
* modules/sternenseemann/sway: make $Mod+0 workspace 10sternenseemann2022-10-101-4/+9
|
* modules/sternenseemann/sway: cleanup portal config a little bitsternenseemann2022-10-101-3/+4
|
* modules/sternenseemann/sway: set qt5 theme to use gtk stylingsternenseemann2022-10-101-0/+2
|
* modules/sternenseemann/desktop-sway: check fontconfig for emoji fontsternenseemann2022-10-101-1/+2
|
* machines/sternenseemann: move desktop-sway.nix into profiles modulesternenseemann2022-10-102-0/+179
| | | | | | | | | | Making it a proper module with options allows us to selectively switch off stuff we don't need, e.g. saneterm. This should help keeping the closure of ludwig smallish. Additionally refactor font handling in the module: Instead of including fonts.nix and assuming Bitstream Vera is available, we check fonts.fontconfig.defaultFonts for the font to prefer.
* profiles/packages: Add mdbookdevhell2022-10-101-0/+1
| | | | | Mdbook has become really useful for writing lab material, so I'll introduce it permanently to my package collection.
* profiles/packages: Add timewarrior and wtfdevhell2022-10-101-0/+3
| | | | | | | | | | | I've been using taskwarrior a lot again lately, and this time I'd be interested in seeing how much time I actually spend on certain tasks, so I'm adding timewarrior to the mix. Unfortunately the hook requires that python3 is installed. WTF is a neat terminal dashboard that show information that I deem useful and would like to keep an eye on without having to manually check for stuff.
* profiles/workstation/git: Sort branches by dateaszlig2022-10-091-0/+1
| | | | | | | | When you have a lot of branches it's sometimes tedious to find out the ones you've been working on recently. Sorting the branches by committer date by default should make it more obvious. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/base: Add fix for i3 config validationaszlig2022-10-061-2/+12
| | | | | | | | | | | | | Quoting from https://github.com/i3/i3/pull/5173: A bug was introduced in https://github.com/i3/i3/pull/5118 in which configs with bar blocks will segfault during validation. They were copying the i3 font which is not set during validation. This PR simply checks that the load_type is not validated before copying the font. This fixes the Hydra build for the i3 configuration on my machines. Signed-off-by: aszlig <aszlig@nix.build>
* modules/core/tests: adapt to paperless module renamesternenseemann2022-10-011-2/+2
| | | | | | | | Ref. https://github.com/NixOS/nixpkgs/commit/0977227b8622daccb5a8435d3d4216eedf845973 Evaluating the vuizvui Hydra seemingly hit an infinite loop involving the rename warning for this change, so hopefully adapting to it makes it possible to evaluate it again.
* devhell/pkgs: Fix attribute name for virt-manageraszlig2022-09-261-1/+1
| | | | | | | | | | | The virtmanager attribute has been renamed a while ago[1] to its upstream name (virt-manager) and referencing the alias will now[2] throw an evaluation error. [1]: https://github.com/NixOS/nixpkgs/commit/5b640bfd089904bfe806606b8b2 [2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130 Signed-off-by: aszlig <aszlig@nix.build>
* Fix attribute name for iproute2aszlig2022-09-261-1/+1
| | | | | | | | | | | The attribute has been renamed[1] to iproute2 a while ago and recently the alias was converted to a throw[2], so let's do the rename on our side as well. [1]: https://github.com/NixOS/nixpkgs/commit/20a9caf0a474e182909ac850fa6 [2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130 Signed-off-by: aszlig <aszlig@nix.build>
* Fix attribute name for man-pages-posixaszlig2022-09-262-2/+2
| | | | | | | | | | | | The posix_man_pages attribute has been renamed in nixpkgs[1] to man-pages-posix to more closely match the upstream name. This now[2] results in an evaluation error. [1]: https://github.com/NixOS/nixpkgs/commit/4461230cc5e11952407f8ddd205 [2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130 Signed-off-by: aszlig <aszlig@nix.build> Cc: @devhell
* radare2: Add patch to default to AT&T ASM syntaxaszlig2022-09-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some personal history on this: I started to get used to AT&T syntax because it's the default in GDB and used that ever since until I one day starting to do some more reverse engineering using radare, which defaults to Intel syntax. Ever since then probably my most used command in GDB was "set disassembly-flavor intel" (because I was to lazy to add it to the config) because I constantly got confused by the source/destination operand swaps. This even happened during live reverse engineering at rC3 where I was confused about some function logic only to find out that I was viewing in AT&T syntax. Fast-forward to today: I'm debugging some application using WINE and winedbg uses AT&T syntax, which I didn't like at first. After reflecting on this for a while, I thought it would probably be better to get used to AT&T syntax again and switch everything to use AT&T for the following reasons: * Operands are more natural to read, since most libraries/APIs in higher level languages do it like this (well, except memcpy, strcpy, etc... maybe I now get confused by libc functions...) * AT&T syntax feels less verbose, for example "mov ecx, dword [eax]" is just "movl (%eax), %ecx" This very commit makes sure that radare2 now defaults to AT&T syntax instead of eg. ensuring that GDB uses Intel syntax by default. Signed-off-by: aszlig <aszlig@nix.build>
* workstation/packages: Add zbar to system packagesaszlig2022-09-111-0/+1
| | | | | | | | | | | Just had to scan the credentials for a Wi-Fi access point and they were only available via QR code, but was unable to make it available via Nix shell because I had (for obvious reasons) no access to the Internet. Adding zbar to all my machines will ensure that something like this won't happen again. Signed-off-by: aszlig <aszlig@nix.build>
* workstation: Use oldschool font pack from nixpkgsaszlig2022-09-051-11/+1
| | | | | | | | | 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>
* profiles/workstation: Use autoLogin on LUKSaszlig2022-09-051-19/+28
| | | | | | | | | | | | | | | | | 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>
* Use a font point size of 10 on hidpiaszlig2022-09-053-2/+7
| | | | | | | | | 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>
* slylandro: Add quirk for disabling D3cold on NVMeaszlig2022-08-263-0/+61
| | | | | | | | | | | | | | | | | | | | | | 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>
* modules/profiles/tvl: disable search domainsternenseemann2022-08-161-3/+0
| | | | This stopped working for me for some reason, so no point in keeping it
* machines + modules: Fix Nix option definitionsaszlig2022-08-153-20/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* profiles/workstation: Add perf to systemPackagesaszlig2022-08-151-5/+8
| | | | | | | | 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>
* core/tests: Remove nixos.docker-edgeaszlig2022-08-151-4/+0
| | | | | | | | 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>
* profiles/managed: Remove TLPaszlig2022-08-151-2/+0
| | | | | | | | | | | | | | 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>
* packages: Replace jwhois by whoisaszlig2022-08-151-1/+1
| | | | | | | | | | | | | | | | 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>
* profiles/base: Use XKB config for console keymapaszlig2022-08-031-1/+2
| | | | | | | | | | | | 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>
* programs/git: Fix path for sysdir.caszlig2022-08-021-1/+1
| | | | | | | | 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>
* core/tests: Don't access removed graphite optionsaszlig2022-07-141-2/+1
| | | | | | | | | | | | | | | 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>
* services/upower-minimal: use empty config by defaultProfpatsch2022-06-271-3/+1
| | | | | | I think the `null` still came from the nixpkgs module. Not sure whether upower will like an empty config file, but we’ll see.
* modules/hardware/thinkpad: Explicit libProfpatsch2022-06-261-9/+6
| | | | Yay static linting.
* modules/hardware/thinkpad: Default intel.updateMicrocode to trueProfpatsch2022-06-261-0/+5
| | | | | | | | 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.
* machines/legosi: add weechat-qwerkyProfpatsch2022-06-261-32/+51
| | | | | Changes the weechat setup so that I can have multiple instances, each gets their own unix user & separate weechat instance.
* modules/Profpatsch/weechat: Add the matrix scriptProfpatsch2022-06-261-1/+10
|
* modules/sternenseemann/sway: display »Kalenderwoche« in the status barsternenseemann2022-06-241-0/+6
|
* profiles/packages: Purge some unneeded stuffdevhell2022-05-311-3/+0
|
* profiles/base: Remove noisetorchdevhell2022-05-251-1/+0
| | | Which has apparently been compromised upstream. Yay.
* profiles/base: Fix deprecated SSH config optionaszlig2022-05-141-3/+3
| | | | | | | | | | | | | | | | | | This gets rid of the following warning: trace: warning: The option `services.openssh.challengeResponseAuthentication' defined in `.../modules/user/aszlig/profiles/base.nix' has been renamed to `services.openssh.kbdInteractiveAuthentication'. The option actually didn't make sense in the first place because it was an alias leftover from SSH 1. I also changed the priority for the OpenSSH options from 1000 to 500 to avoid any future conflicts should the upstream module use mkDefault one day. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Allow unraw via sysrqaszlig2022-05-141-0/+3
| | | | | | | | | | I just was forced to reboot my workstation while working on a program that sets the VT into raw mode but finding out that the unraw key now doesn't work anymore. This used to be the case but with the sysctl include that comes with systemd-coredump, the kernel.sysrq value defaults to only allowing sync (16). Signed-off-by: aszlig <aszlig@nix.build>
* profiles/packages: youtube-dlp -> yt-dlpdevhell2022-05-131-1/+1
| | | | Cos I'm an idiot at this time of night.
* profiles/packages: youtube-dl -> youtube-dlpdevhell2022-05-132-1/+3
| | | | `youtube-dl` is dead, long live `youtube-dlp`!
* profiles/packages: Remove musikcubedevhell2022-05-121-1/+0
| | | | With `termusic` in the repos there's no need for musikcube.
* profiles/packages: Add nixpkgs-reviewdevhell2022-05-111-0/+1
| | | | Hot-loading this is getting annoying, so I'll just add it.
* profiles/packages: Remove monkeysAudiodevhell2022-04-251-1/+0
| | | | | | I've not come across anyone actually using this. Additionally, it's not OSS, so there's not much reason to keep it around. Oh, and the build fails.
* profiles/packages: Remove cipherscandevhell2022-04-071-1/+0
| | | Was removed from nixpkgs upstream.
* profiles/packages: Add easyeffectsdevhell2022-04-031-0/+1
| | | | Gotta try all dat pipewire love.
* modules/zsh: Really fix evaluation this timeaszlig2022-03-241-3/+1
| | | | | | | Gosh, today my brain really doesn't work very well it seems, because I actually forgot to add the first hunk via "git add -p". Signed-off-by: aszlig <aszlig@nix.build>
* modules/zsh: Fix evaluation error and clean upaszlig2022-03-241-8/+8
| | | | | | | | | | | | | | Regression introduced by 25a077f90a0005b519db071a6b5b4d20bd6d2d45. I usually let Vim perform a syntax check on the Nix file I'm editing, which usually displays errors. However, given that the zsh module is one of my older modules where I did a big "with lib;" over the whole scope, a nix-instantiate --parse didn't find the missing pkgs argument. So apart from just fixing the error, I removed the "with lib;" and also moved from the old lib.overrideDerivation to package.overrideAttrs. Signed-off-by: aszlig <aszlig@nix.build>
* modules/upower-minimal: Fix option descriptionaszlig2022-03-241-1/+1
| | | | | | | | | Regression introduced by 652ac49da16123016c36537dc28331649a63bf7b. This breaks the build of the manual because the <literal/> tag wasn't closed. Signed-off-by: aszlig <aszlig@nix.build>
* programs/zsh: Add syntax highlightingaszlig2022-03-241-1/+46
| | | | | | | | | | | | | I'm already using zsh-fast-syntax-highlighting since weeks via the configuration.nix and I actually forgot why I used this implementation rather than one of the others out there. However, since I'm also using Nushell[1] on a regular basis, I got quite used to syntax highlighting so that's why I added it to zsh as well. [1]: https://www.nushell.sh/ Signed-off-by: aszlig <aszlig@nix.build>
* workstation/redshift: Lower nightly brightnessaszlig2022-03-241-0/+1
| | | | | | | I've been testing 0.5 for weeks now and already got sufficiently used to it so that I'd become blind if it would be the default value (1.0). Signed-off-by: aszlig <aszlig@nix.build>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-06 01:41:24 +0000