about summary refs log tree commit diff
path: root/machines/aszlig
Commit message (Collapse)AuthorAgeFilesLines
* dnyarri: Add youtube-dl support to gPodderaszlig2020-07-281-1/+5
| | | | | | | | | | | | | | 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>
* machines/tyree: Fix evaluation of weboobaszlig2020-04-041-1/+1
| | | | | | | | | | | | One (or maybe more?) dependency of weboob requires Python 3 and hence using weboob from python2Packages isn't going to evaluate and instead result in this error: error: google-api-core-1.16.0 not supported for interpreter python2.7 Using weboob from python3Packages fixes the eval error. Signed-off-by: aszlig <aszlig@nix.build>
* machines/dnyarri: Provide luks.devices as attrsetaszlig2020-01-181-2/+3
| | | | | | | | | | | | | | | | The use of types.loaOf has been deprecated since quite a while and lately[1] there is also an appropriate warning in place if an option definition relies on types.loaOf to coerce the list to an attrset. In vuizvui we didn't rely on types.loaOf, but it turned out that dnyarri still relied on it in boot.initrd.luks.devices. Since we already use attrsets for defining the LUKS devices, it's rather easy to fix and we just need to return a nameValuePair in mkDevice. [1]: https://github.com/NixOS/nixpkgs/commit/03309899eb41e50ef65001f63d6a4f078e3d4556 Signed-off-by: aszlig <aszlig@nix.build>
* treewide: use `runCommandLocal` where applicableProfpatsch2019-12-081-1/+1
| | | | | | | `runCommandLocal` was added to nixpkgs in https://github.com/NixOS/nixpkgs/pull/74642 to speed up trivial `runCommand` derivations by always building them locally. We have a few places where that’s good to use.
* machines/brawndo: Add Visual Studio Codeaszlig2019-10-301-2/+2
| | | | | | | | | Unfortunately, this is a work requirement for the user in question, so while I'd (personally) prefer to pretty much stay on free software, the circumstances prevent this :-/ Signed-off-by: aszlig <aszlig@nix.build> Cc: @dwenola
* machines/aszlig: Explicitly set useDHCPaszlig2019-10-084-1/+4
| | | | | | | | | | | | | | | | | | The usage of DHCP is no longer global since a while[1] and we now have to explicitly enable it for the interfaces in question. This actually is a good thing and makes it far less problematic if we use tunnel interfaces and other more complicated networking configuration. I added the definitions for all machines where I actually know which interfaces are in use and disabled useNetworkd for shakti, because I don't know the interface names for that machine and the machine currently isn't in use anyway, so we can add it later if needed. [1]: https://github.com/NixOS/nixpkgs/pull/69302 Signed-off-by: aszlig <aszlig@nix.build>
* machines/brawndo: Use cnijfilter2 from nixpkgsaszlig2019-09-231-13/+1
| | | | | | | 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>
* machines/managed: Switch to libinputaszlig2019-09-073-5/+0
| | | | | | | | | | | | 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>
* machines/dnyarri: Fix allowUnfreePredicateaszlig2019-09-061-1/+1
| | | | | | | | | | | | | 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>
* machines/brawndo: Add cnijfilter2 version 5.70aszlig2019-06-121-1/+13
| | | | | | | | | | | | | | | | | 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>
* machines: Remove kzerzaaszlig2019-03-201-69/+0
| | | | | | | | 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>
* machines/dnyarri: Stop bcache during sleep/scrubaszlig2019-02-091-1/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* machines/dnyarri: Enable btrfs auto-scrubaszlig2019-02-091-0/+2
| | | | | | | | I had this in my local configuration.nix since a while and while it might be annoying when this runs every month, I think it's better to do it regularily rather than having a dying disk go unnoticed. Signed-off-by: aszlig <aszlig@nix.build>
* machines/dnyarri: Remove vault deviceaszlig2018-12-241-14/+1
| | | | | | | | Since quite a while, NixOS re-uses the passphrases from earlier devices, so there is no need anymore for such a device in order to unlock multiple containers with the same passphrase. Signed-off-by: aszlig <aszlig@nix.build>
* machines/dnyarri: Use close instead of luksCloseaszlig2018-12-241-1/+1
| | | | | | | The "luksClose" subcommand for cryptsetup has been deprecated for a while, so let's move over to "close". Signed-off-by: aszlig <aszlig@nix.build>
* machines/dnyarri: Enable bcache kernel moduleaszlig2018-12-241-0/+5
| | | | | | | | | | | | | | | Since I got a new SSD for the machine (thanks @cvdnext), I also had the opportunity to re-create my LUKS containers to LUKS2 with Argon2 key derivation alongside creating bcache backing devices. The change in order to support bcache is just a matter of adding "bcache" to availableKernelModules and we're done. However, as the storage configuration is not a very common one, I decided to add a test specific to that to make sure future NixOS updates won't prevent the machine from booting. Signed-off-by: aszlig <aszlig@nix.build>
* tishtushi: Remove mount for /nix/storeaszlig2018-12-121-10/+0
| | | | | | | | | | | | The internal SSD of the machine just died, so I reconstructed the Nix store on the spinning rust from the machine configuration and we're now left without the SSD. Maybe it makes sense to still use the SSD with bcache, depending on how failure-resilient it is, but for now, let's just remove it so we at least have a working system. Signed-off-by: aszlig <aszlig@nix.build>
* dnyarri: Drop override for podcastparseraszlig2018-10-251-17/+1
| | | | | | | | | | | The upstream version 0.6.4 was released 2 months ago and it recently hit nixpkgs[1], so we can finally drop the override as the new version now contains the fix[2] for the problem that affected me. [1]: https://github.com/NixOS/nixpkgs/commit/5e2590ba6fd352bc65b4cd7fd82 [2]: https://github.com/gpodder/podcastparser/pull/17 Signed-off-by: aszlig <aszlig@nix.build>
* machines/brawndo: Add Firefox to systemPackagesaszlig2018-07-251-1/+2
| | | | | | | | User is likely to switch, so let's add Firefox alongside to Chromium and eventually remove Chromium at some day. Signed-off-by: aszlig <aszlig@nix.build> Cc: @dwenola
* machines/brawndo: Add Python 3 to system pathaszlig2018-07-221-1/+1
| | | | | Signed-off-by: aszlig <aszlig@nix.build> Cc: @dwenola
* machines/tyree: Add auxiliary pkgs around KMyMoneyaszlig2018-05-061-1/+2
| | | | | | | | Those are useful for HBCI/FinTS support and scraping other banking websites. KGPG is for encrypting the ledger. Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* Revert "machines/tyree: Add Microsoft Core Fonts"aszlig2018-05-061-3/+1
| | | | | | | | | | This reverts commit d813e5de7f84ad57d25b5c0ec95c2098204e976b. Turns out that the machine's owner has found an alternative font already installed on the system, so we don't need proprietary fonts, yay! Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* machines/tyree: Add Microsoft Core Fontsaszlig2018-05-061-1/+3
| | | | | | | | | | I thought about whether this would be a good idea to generally add this to the managed profile, but didn't do so because we don't want to encourage users to use proprietary fonts if possible. If requested we can still add it on a by-machine basis. Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* machines/tyree: Add KMyMoney to systemPackagesaszlig2018-05-061-1/+1
| | | | | | | This has been on the machine for a while and it's now in nixpkgs master. Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* machines/tyree: Enable libinputaszlig2018-04-251-0/+1
| | | | | | | | | | This has been in the configuration.nix for a while and it seems to be working. It might be a good idea to add it to the managed profile, but we first have to test whether this really works for other machines than tyree. Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* machines/tyree: Impose a size limit on journaldaszlig2018-04-251-0/+2
| | | | | | | | | The machine doesn't have a lot of MMC space, so putting a whole lot of logs which we probably won't need for such a long time isn't a good idea. Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* machines/tyree: Add options for encryptionaszlig2018-04-251-0/+18
| | | | | | | | | The new installation of this Laptop uses encryption and so far these options have been residing in the local configuration.nix, so let's get it over to Vuizvui. Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* machines/tyree: Switch from Chromium to Firefoxaszlig2018-04-251-1/+1
| | | | | | | | The machine's user already has switched to Firefox since quite a while, so let's actually add it to systemPackages. Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* machines/shakti: Provide EDID informationaszlig2018-04-231-0/+15
| | | | | | | | | | | | | | The monitor reports back EDID via DVI but the HDMI->DVI adapter seems to not handle that correctly. Also the monitor has weird resolutions, so using the fallback modes provided by the kernel also doesn't seem to work and the monitor stays blank. While hardcoding the EDID information isn't a very good idea for this machine in general (because it might be connected to a different monitor), for now this is the easiest workaround because I don't have access to that machine. Signed-off-by: aszlig <aszlig@nix.build>
* machines/dnyarri: Switch to latest kernelaszlig2018-04-231-1/+2
| | | | | | | | | Similar to 8562389f5e13e42329fc26ca53e9cf54ac0e541e but now for dnyarri. I grew a bit tired recently to fix up kernels, so let's actually run the latest release version instead. Signed-off-by: aszlig <aszlig@nix.build>
* tishtushi: Remove fbcon and usb-storage modulesaszlig2018-04-211-1/+0
| | | | | | | | Not sure why I added them in the first place, but it was probably because they were listed in the hardware config generated by nixos-generate-config. Signed-off-by: aszlig <aszlig@nix.build>
* machines: Remove unneeded crypto modules in initrdaszlig2018-04-213-13/+0
| | | | | | | These were needed a few months ago but they're now automatically added if boot.initrd.luks.devices is non-empty. Signed-off-by: aszlig <aszlig@nix.build>
* machines/tishtushi: Use latest release kernelaszlig2018-04-211-2/+3
| | | | | | | I'm a bit tired of constantly running into regression from release canidate kernels, so let's switch to released kernels for now. Signed-off-by: aszlig <aszlig@nix.build>
* machines/tishtushi: Remove discard option in /nixaszlig2018-04-211-1/+1
| | | | | | | We no longer write directly to the physical block device, so let's not try to TRIM a mapper device. Signed-off-by: aszlig <aszlig@nix.build>
* tishtushi: Change to new partitioning schemeaszlig2018-04-211-16/+43
| | | | | | | | | | | I had to recover tishtushi while on the road because I have used zstd compression, which GRUB doesn't support. So instead of just adding a boot partition I decided to actually do what I long wanted to do, which is to actually encrypt the disks, so the new partitioning reflects that. Signed-off-by: aszlig <aszlig@nix.build>
* machines/shakti: Add file systemsaszlig2018-04-131-6/+27
| | | | Signed-off-by: aszlig <aszlig@nix.build>
* machines/shakti: Add Firefox to systemPackagesaszlig2018-04-121-0/+1
| | | | Signed-off-by: aszlig <aszlig@nix.build>
* profiles/managed: Move Chromium to machinesaszlig2018-04-122-2/+2
| | | | | | | The new machine (shakti) is going to use Firefox, so let's make sure this is machine-specific. Signed-off-by: aszlig <aszlig@nix.build>
* machines/shakti: Enable deluge serviceaszlig2018-04-121-0/+2
| | | | Signed-off-by: aszlig <aszlig@nix.build>
* shakti: Add dropbox to systemPackagesaszlig2018-04-121-2/+2
| | | | | | At least for now until the owner gets rid of it. Signed-off-by: aszlig <aszlig@nix.build>
* machines: Add new machine "shakti"aszlig2018-04-121-0/+39
| | | | | | This is only a placeholder right now so we get Hydra builds. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/managed: Move updateMicrocode to machinesaszlig2018-04-122-0/+3
| | | | | | | | This is clearly something that is specific to the actual hardware, so even though both brawndo and tyree share the same CPU vendor, we will have a third managed machine that is going to be different. Signed-off-by: aszlig <aszlig@nix.build>
* machines: Remove arilouaszlig2018-04-031-42/+0
| | | | | | | | | | Why do I fix up a machine that doesn't exist anymore? This was from a time where I had no laptop and was travelling around with an USB stick in order to have a working environment on other machines, but that's no longer the case. Signed-off-by: aszlig <aszlig@nix.build>
* machines/arilou: Use correct modulesPathaszlig2018-04-031-3/+1
| | | | | | | | | | | Since I wrote the config for that machine, the modulesPath attribute is actually a thing in NixOS modules, so let's use that one instead. Besides, I really tend to like that even more restrictive restrictive evaluation mode, because it allows us to get rid of all those references to the Nix path. Signed-off-by: aszlig <aszlig@nix.build>
* dnyarri: Remove gpodder derivation attrs overrideaszlig2018-02-261-11/+1
| | | | | | | | | | | I've put in an assertion back then to make sure that once gpodder 3.10.1 is released, we get a failure so we don't stay behind forever. With NixOS/nixpkgs@4d1e72cfbb8de0d8adf2c047aad14f29eb4f77bf, not only the version is bumped but also the icon theme is added back, so we can drop the whole override of the attributes. Signed-off-by: aszlig <aszlig@nix.build>
* dnyarri/gpodder: Add hicolor_icon_themeaszlig2018-02-181-0/+3
| | | | | | | | | | | | This is needed in order to correctly display icons if someone doesn't use a full desktop environment. I'm not sure why NixOS/nixpkgs@bff6d624e05c53777a9d2fd85872884983f74313 removed this (in particular gnome3.defaultIconTheme, but hicolor_icon_theme should be enough anyway), but let's re-add it for our configuration until this is sorted out. Signed-off-by: aszlig <aszlig@nix.build>
* dnyarri: Use latest master for podcastparseraszlig2018-02-181-4/+20
| | | | | | | | | | | | | | | | Seems that 543ca6580d6f52d58caf975c0ed583956aa08b39 was not enough to fix the actual issue, because the real issue was in podcastparser. The upstream issue is gpodder/gpodder#394 and the pull request fixing this is gpodder/podcastparser#17. Instead of just updating podcastparser, I also updated gpodder to latest master, because it contains a few more fixes. I've tested whether this fixes my issue and it did (feed items now have the correct date). Signed-off-by: aszlig <aszlig@nix.build>
* machines/aszlig: Use zstd compression for btrfsaszlig2018-02-044-5/+5
| | | | | | | I've been using this for a while and got better results than zlib and lzo, so let's actually use this for all my machines. Signed-off-by: aszlig <aszlig@nix.build>
* Revert "machines: Remove tyree"aszlig2018-02-021-0/+47
| | | | | | | | | This reverts commit dfd3d86562f09d812b330893cec053ab3d371bdf. The machine is back on NixOS again :-) Signed-off-by: aszlig <aszlig@nix.build> Cc: @brokkoliberta
* dnyarri: Override gpodder to use latest masteraszlig2018-02-021-1/+11
| | | | | | | | | | | This is mainly to get gpodder/gpodder@c937184987431427dfcf8ac9bc098ce0ac but there are other fixes in the current master version, so instead of just patching the single fix, I'm heading for master directly instead. I've also added an assertion on the version attribute so that whenever there is a new upstream version, we can revert this. Signed-off-by: aszlig <aszlig@nix.build>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-25 12:46:48 +0000