| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2023-12-08 | delete configuration for old machines | Franck Cuny | 1 | -58/+0 | |
| These machines are gone, no need to keep the configuration around. | |||||
| 2023-05-02 | profiles/server: move boot loader configuration | Franck Cuny | 1 | -3/+0 | |
| 2023-05-02 | profiles/default: move stuff related to boot | Franck Cuny | 1 | -1/+0 | |
| 2023-05-02 | profiles: move things around for btrfs | Franck Cuny | 1 | -7/+0 | |
| 2023-05-02 | profiles/hardware: create a few profiles related to hardware | Franck Cuny | 1 | -2/+0 | |
| 2023-04-03 | hosts/carmel: reconfigure the host as a router | Franck Cuny | 1 | -0/+3 | |
| I'm not using it as a desktop, and the current router is getting old and will likely fail in the near future. It's also a debian machine configured manually, so let's reconfigure carmel as our new router. There are three NICs in the host: 2 are 10Gb and one is 1Gb. The 1Gb will be used as the upstream interface, and one of the 10Gb will be for the LAN. There are 2 VLANs to configure: one for IoT devices and one for guest. | |||||
| 2023-03-15 | hosts: it's time to switch to schedutil | Franck Cuny | 1 | -0/+2 | |
| 2023-03-14 | hosts/tahoe: set the consoleMode to "max" | Franck Cuny | 1 | -0/+3 | |
| 2023-01-10 | fix(hosts/tahoe): workaround md raid boot uuid issue in 22.11 | Franck Cuny | 1 | -2/+2 | |
| Due to md device uuid availability issue in initrd. Refs: - https://github.com/NixOS/nixpkgs/issues/196800 - https://github.com/NixOS/nixpkgs/issues/199551 | |||||
| 2022-04-08 | hosts: rename hardware-configuration to hardware | Franck Cuny | 1 | -0/+0 | |
| 2022-04-06 | enable AMD module correctly | Franck Cuny | 1 | -1/+1 | |
| 2022-04-06 | refactor configuration for AMD | Franck Cuny | 1 | -38/+39 | |
| 2022-03-05 | tahoe: new hardware configuratio | Franck Cuny | 1 | -21/+13 | |
| 2022-02-27 | hosts: add tahoe, the new NAS | Franck Cuny | 1 | -0/+70 | |
