| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
I now experienced the crash for the second time whenever my machine
starts swapping. The details about the crash(es) and the corresponding
fix can be found at:
https://bugs.chromium.org/p/chromium/issues/detail?id=822360
When the patch lands in mainline and stable, we can revert this very
commit.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Even though these options are rather opinionated rather than generally
useful, it makes sense to have an option for that because I'm going to
use it for my managed machines as well.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The patch no longer applies with this kernel version because the patch
context has changed.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The patch for <= 4.14 no longer applies, because elevator_get() now has
an additional argument.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
The change dropping the SCSI_MQ_DEFAULT option has been reverted in
torvalds/linux@cbe7dfa26eee4819db7b5846181d56fd0cece0ea, so while the
release canidate versions didn't have this option, the final release
however does have it again.
So we need to wait until 4.14 for it to become removed hopefully.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This has been removed upstream and is no longer needed, see commit
torvalds/linux@5c279bd9e40624f4ab6e688671026d6005b066fa.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This dissolves the user.aszlig.system.kernel module, which was not only
to stay on the latest bleeding edge kernel but also to enable BFQ. The
latter has been factored out already a while ago already.
Originally, I had a fully custom kernel config for mmrnmhrm and dnyarri,
but it's no longer the case and thus the user.aszlig.system.kernel
module is now no longer needed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
Not everybody likes to have the latest release canidate kernel, so we
now have an option called vuizvui.system.kernel.bfq.enable, which *only*
enables the BFQ scheduler per default.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We already have a directory just for hardware-specific configuration
options and the module option already says "vuizvui.hardware", so it
should better be consistent with the directory layout.
Tested using:
nix-instantiate release.nix -A machines.profpatsch.katara
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Building ISO images for all machines really doesn't make sense if we
only have _one_ machine at the moment, where we really use it (kzerza).
So we now have an option which can be defined for a particular machine
configuration, which is then going te be excempted from the ISO building
process.
The latter isn't yet implemented however, only the option is here right
now.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
This reverts commit fc53a72f48ae6b567e7bf9901a2bd3657853633c.
Applied upstream at NixOS/nixpkgs@224ed7e.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
This is very useful if you're running a lot of the same instances of
particular applications. For example virtual machines or even lots of
terminals.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|