| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Now that the scheduler is in mainline, I think there is nothing now to
stop us from unleashing it to end users :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
The service and test has been broken for a long time now and nobody
really has any interest in using it or even fixing it, so I'm removing
it to decrease the amount of crap we have in there.
If somebody still wants to use this someday we can still bring it back.
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I previously wrote that patch in a hurry, so I thought it would be
enough to set CONFIG_DEFAULT_IOSCHED to "bfq". But in block/elevator.c
the actual default for blk-mq is a constant and can't be configured via
CONFIG_DEFAULT_IOSCHED.
So we're now patching just that constant and nothing more.
Also, I've enabled CONFIG_DM_MQ_DEFAULT, because the DM devices need to
be switched to blk-mq as well and for example on dnyarri I'm actually
using the device mapper for LUKS.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
| |
A simple script to gather DNS & download speed data.
|
|
|
|
|
|
|
| |
We no longer need to use linux_testing, because kernel 4.12 is stable
since yesterday.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can now safely drop the sound, sdio and drm patches, because they all
have been applied upstream already and after some testing the T100HA
works quite nicely.
One exception however is a small part from the drm patch, which is the
PMIC hack which I originally introduced in
e8861698f019eb218be451e444898a1cb5577d21 as a separate file which it's
now again, but rebased against kernel 4.12-rc6.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
The option value was missing a .host, which caused the evaluation to
fail because of a missing attribute.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|\
| |
| |
| |
| |
| |
| | |
This merges pull request #15 and thus also introduces @devhell as a new
member of vuizvui.
Changes were approved by @devhell via XMPP.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This introduces another profile module called "packages", which contains
all the package configuration (including overrides) of all the machines
in the devhell namespace.
The machine-specific configuration is now merged into the machine
configurations the same way as we've done previously with the services.
One major difference here is that the haskellPackages workaround is no
longer needed in the package configuration, as it is handled by vuizvui.
Tested this by evaluating all machines and all evaluations succeeded.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
IMHO this module is really too small to factor it out into its own
profile module, so I'm putting it into the base profile as it's really
common among all of devhell's machines.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I've added another profile called "services", which now resembles the
services_common.nix from the previous configuration.
The machine-specific definitions now reside directly inside the
machine's Nix expressions for now, until they're properly refactored.
Most of these machine-specific values can be easily modularized,
especially the xrdb config, for example having one base xrdb module
and only small machine-specific definitions if stuff needs to be
overridden.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is from network/network_common.nix and it really affects all of the
machines, so it makes sense to add it to the base profile.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In his configuration he had machine_common.nix which was imported from
the other machine_*.nix files. However in order to start modularizing
I've converted machine_common.nix into a proper NixOS module which now
resides in modules/user/devhell/profiles/base.nix and can be simply
activated via:
vuizvui.user.devhell.profiles.base.enable = true;
Apart from that I've removed the following configuration definitiens
from machine_common.nix:
nix.binaryCaches = [
"https://headcounter.org/hydra/"
"https://cache.nixos.org/"
];
nix.requireSignedBinaryCaches = true;
nix.binaryCachePublicKeys = [
"headcounter.org:/7YANMvnQnyvcVB6rgFTdb8p5LG1OTXaO+21CaOSBzg="
"cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY="
];
nix.nixPath = lib.mkOptionDefault [
"nixpkgs=/home/dev/git/remote/other_github/nixpkgs"
];
The reason for removing them is because we already handle that via the
vuizvui core modules (modules/core/common.nix).
I've tested this by evaluating the machines by temporarily setting
"allowUnfree = true" (which is part of another module I didn't migrate
yet) and it succeeds.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| | |
This option does no longer exist in current Nix 1.12 and has been
removed in NixOS/nix@0afeb7f51e3465c7c27bc5a83017e9ffde8c6725.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
The mainline kernel only allows switching schedulers via sysfs and for
each individual device. I don't want to do that so let's do this with a
small patch so we can set BFQ as the default blk-MQ scheduler.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We're using kernel 4.12 and the BFQ scheduler is included there as a
blk-BQ scheduler, so instead of the patch, let's just use a config where
we set BFQ to be used as the default scheduler.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
| |
| |
| |
| |
| |
| | |
Nix 1.12 already contains "nix repl" and as I'm using Nix 1.12 on all of
my machines the nix-repl package is obsolete.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|/
|
|
|
|
|
| |
There is no <path/> tag and what I wanted back then is called
<filename/>.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
It’s just annoying otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new version of the "TRAVIC-Sign" extension that's used by the
Santander bank now relies on native messaging, so it's much much easier
for us to sandbox and also easier to integrate.
For more information about native messaging see:
https://developer.chrome.com/extensions/nativeMessaging
So the upstream only contains a Firefox extension, but it doesn't
deviate very much (at least since the new non-XUL API) from the Chromium
extension API, so we only need to patch the manifest (where we also
constrain the sites that the extension is allowed to run) and refer to
the Wine wrapper in the native messaging host configuration file.
Right now, the Chromium version that we have in <nixpkgs> still refers
to /usr/share/chromium/extensions in order to search for system-provided
extensions, so we need to fix that as well.
In our workstation profiles we now no longer have the santander package
in lazyPackages, because it's also no longer a binary.
Previously the main reason why I added it to lazyPackages was that the
whole santander package had a closure size of several hundred megabytes
because of the Wine prefix. The latter now is essentially empty.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The way xrandrHeads are addressed has changed with the following
upstream merge commit:
NixOS/nixpkgs@9dca737d6269759745c9e68ea462446cde4d9be9
Now xrandrHeads are no longer a list of strings but a list of attribute
sets, but we new do have even more information about a particular head.
So apart from fixing this, we new also set --primary whenever applicable
in "xreset".
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This is a follow-up to b703865f1757d716954aa31f1fbaabc52ed4e3b3, because
I forgot to actually remove it from my own profile.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
| |
This is because `enableAllFirmware` now contains a new entry that is unfree.
Other machines probably want to move as well, cc @aszlig @sternenseemann.
|
|
|
|
|
|
|
|
| |
This is for the time being until either NixOS/nixpkgs#21671 has been
resolved or the next major version of Gajim has been released, because
the latter no longer uses pycrypto.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This already has started in e0abe1dbbda54c1f048b5d38df05e1a3289216a6
with @Profpatsch putting his packages into its own namespace, so let's
continue on that and move my crap into my own namespace as well.
The only difference in my approach is that I'm now also using a new
function called callPackageScope, which declutters pkgs/default.nix a
bit and moves the individual callPackage invocations into
aszlig/default.nix.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
A lot of crap has been accumulated there over the years, so I'm removing
at least the stuff that I have introduced.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes sense to put into the core module here, because we already
have the public key in there as well and if we want to use the binary
cache outside of a channel it's a good idea to provide it here by
default.
Being a default of course also means that users can easily override this
using:
nix.binaryCaches = mkForce [ "something else" ];
I've also removed the redundant setting of that option in all of the
machine configurations.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @sternenseemann
|
|
|
|
|
|
| |
Added in NixOS/nixpkgs@dc87b5587e3fb39e96e6b965a26f324daf7508f8.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nix 1.12 already got rid of most of the Perl stuff so the Perl script
backing taalo-build doesn't work anymore because Nix/CopyClosure.pm is
no longer available.
One way to fix this properly is to part the backend to C++ and use the
new ssh-ng store backend. This would also have the advantage that we
don't need to hardcode protocol internals here anymore.
Unfortunately, Nix 1.12 isn't stable yet and we would break Nix 1.11 if
we use the new store API.
So that's why I'm pinning the backend to use Nix 1.11 instead and leave
that ugly Perl script until Nix 1.2 is stable.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously in d6848012b86088cbfd70666a0cfae95c567e7199 I've just rebased
the patch I had against 4.10 against kernel 4.11, but that didn't work
out so well.
So this is now a rebase against the new branch from Paolo Valente at:
https://github.com/linusw/linux-bfq/tree/bfq-v8
Hopefully this time it will compile ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
I'm fed up with fixing up Chromium beta and currently the included GN
doesn't bootstrap as well. So for now let's run with Chromium stable
until I'm masochistic enough to dig into Chromium again.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's basically only a very small change, because block/Makefile now
contains objects for block-MQ schedulers (one of these will also include
BFQ in possibly the next mainline kernel) and thus the patch no longer
applies.
Having that potch here in the source tree is a lot of crap lying around,
so we better get rid of it ASAP.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Compiling nix-repl with Nix 1.12pre5152_915f62fa will only work by
enabling support for ISO C++ 2014, because nix/util.hh uses includes
from <experimental/*>.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New tests as of NixOS/nixpkgs@b0179351036a870da8c1a89c991a359a73aab0e2:
* containers-restart_networking
* nginx
* pgjwt
* postgresql (now with subtests per package)
* sddm (now with subtest "autoLogin" and "default")
* wordpress
The following tests were renamed:
* kde5 -> plasma5
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Fixes evaluation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the attributes accordingly to the following two upstream
commits:
* NixOS/nixpkgs@f21d4d00152726c02f870cb20faba4aca18ef49a
* NixOS/nixpkgs@8eb4d2afbc1d61d316073f25f5885a46ccb37ea2
The first renames desktopManager.kde5 to desktopManager.plasma5 and the
second one removes the kde5 attribute from the top-level packages set
and puts applications in kdeApplications instead.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
| |
Non-laptop machines should not connect to the wifi automatically (they probably
don’t even have a wifi module …)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Haha, so that's what I got from introducing callSubTests in
NixOS/nixpkgs@b3337edd0b77f04d0abe4a29642a5e4fdb4ad692.
While in general this is an improvement, it makes it harder for vuizvui
to gather tests that were added or removed.
Maybe we should write an updater for this soon.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New tests as of NixOS/nixpkgs@b207bf523b8c49b037a4a87456d61f63043cd2c6:
* containers-extra_veth
* containers-hosts
* containers-macvlans
* containers-physical_interfaces
* containers-tmpfs
* glance
* hound
* keystone
* leaps
* mongodb
* nat.firewall-conntrack
* pam-oath-login
* samba
* sddm
The following tests were removed:
* kde4
* panamax
I've also added a few checks on whether containers are actually enabled,
because some tests like containers-bridge would run if containers with a
bridge were defined but enableContainers was false.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
| |
The function invocation apparently got less lenient, the function name *must*
come first now, before any arguments.
|
|
|
|
|
|
|
|
| |
Most of these packages I don't need for daily work and thus only clutter
up the closure paths of those systems, so let's put them into
lazyPackages.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows to add packages to vuizvui.lazyPackages which then aren't
directly installed onto the system but instead built by the Hydra and
only fetched from it as soon as a binary of one of these packages is
executed.
Doing this only within a NixOS module however isn't enough, because by
default gc-keep-outputs is false, so a garbage collect on the Hydra
instance would remove the packages we wrap in vuizvui.lazyPackages.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit a93b7583084ff9084d73873d80d8dc428406593c.
The issue isn't completely resolved but most of the packages should have
been fixed that tripped the nondeterministic behaviour, see:
https://ghc.haskell.org/trac/ghc/ticket/4012#comment:232
After having done some tests in the past I didn't stumble on this
problem anymore so far, so let's give it a try.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
We inject our own declarative config into Gajim by patching the source,
which unfortunately kills a few tests which assume the default
configuration, especially in terms of the GUI (for example the Vuizvui
config has a single window GUI).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Since NixOS/nix@21948deed99a3295e4d5666e027a6ca42dc00b40
nix::Pid::wait() no longer takes a boolean argument and is now blocking
by default.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|