| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
I had these disabled because I prefer to actually press the touch pad.
Unfortunately I spilled liquid into the touch pad which causes the
"press" veent to no longer work. So let's bring back these annoying tap
buttons.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Now with even more upstream fixes:
https://github.com/NixOS/nixops/compare/d6631b6ea7...9076dbc722
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
Includes more fixes regarding "nixops ssh" which fix problems in
relation to TTY allocation.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
As all my important changes to NixOps so far have either been pushed by
me or merged in, this version now should contain all the fixes necessary
to do painless deployment for Hetzner machines.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
It got bumped to version 2.5.0 in NixOS/nixpkgs@f0d1766.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of merging all those PRs via the patches attribute, I've now
created a branch that has all those PRs merged, which are:
* NixOS/nixops#201: Use dedicated SSH keypair for "none" backend
* NixOS/nixops#348: Fixup and refactor Hetzner backend tests
* NixOS/nixops#349: hetzner: Don't create /root/.ssh/authorized_keys
* NixOS/nixops#350: Fix tests for the "none" backend
So our version of NixOps now should now correctly cope with
users.mutableUsers set to false.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
It's already in version 4.3-rc5, but the following patch seems to be
more correct:
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-August/096516.html
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This by coincidence is version 1.3.1 with our own patches (which still
apply).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Using -rc4 really feels rather old, so let's get it to latest upstream
master, which is exactly -rc5 without any additional commits at the
moment.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
Having to switch keyboards when I have my laptop at home is quite
annoying, so let's add the laptop (tishtushi) to the synergy config but
without setting a mouse region so it won't get more annoying than
switching keyboards ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
Having Menu/AudioPlay used for synergy isn't really a very good idea if
some applications actually use those keys, so let's move on to a similar
scheme as with my i3 config and use function keys to not collide with
Super+1, Super+2, ...
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts the following commits:
* 3b50260bb166a70a661634b3496e920d21a3ae3d
* d6e723dec33951120d8b8299fbb9e49e55cc1d91
The patch is no longer needed since the upgrade in NixOS/nixpkgs@5fee5c6
because the patch was already from upstream.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
Since the new BFQ patch, this option does no longer exist.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From the changelog:
* IMPROVEMENT: Changed BFQ to use the blkio controller instead of its
own controller. BFQ now registers itself as a policy to
the blkio controller and implements its hierarchical
scheduling support using data structures that already
exist in blk-cgroup. The bfqio controller's code is
completely removed.
* CODE IMPROVEMENTS: Applied all suggestions from Tejun Heo,
received on the last submission to LKML:
https://lkml.org/lkml/2014/5/27/314
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's actually v4.3-rc4 plus 34 commits ahead.
Also I'm being a bit lazy if it comes to the configuration here, adding
modules I probably won't need. That's because I currently don't have the
time to read more into the details.
Anyway, in the future I'd like to unify kernel configuration anyway, so
the laziness hopefully won't stay around for very long. :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
I'm going to remove legacy fbdev support from the kernel configurations,
so in order to still have terminals besides the X server we need to
enable this (also, kmscon allows more eyecandy if we want that).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
This reverts commit 6d823f636947701f98ee5943187f0a99f0827e72.
Second screen on dnyarri is back :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
We need to strip off one path component, because the patches generated
by Trac's diff viewer contain absolute paths.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
I could have added this to the upstream <nixpkgs>, but we only include
and support release versions. This fixes the following failed build for
VirtualBox:
https://headcounter.org/hydra/build/748430
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I was glad that the issues because of the longstanding GHC determinism
bug (https://ghc.haskell.org/trac/ghc/ticket/4012) happened less
frequently with GHC 7.10.
Unfortunately, they still happen, as reported by @Profpatsch at
headcounter/deployment#19 so we're going to override the GHC derivation
with an additional attribute that is exported into the environment of
the builder.
This attribute causes GHC and all dependant packages to be rebuilt on
the Headcounter Hydra. The original issue was because we're using the
official NixOS binary cache as well as building everything from source.
It's helpful for not needing to rebuild the entire world, but for
Haskell packages it's harmful until the mentioned GHC bug has been
fixed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were using environment.sessionVariables before, but
NixOS/nixpkgs@3f1354a added an option exclusively for this. It
internally still sets environment.sessionVariables, so it doesn't change
anything for us because we're overriding the full list anyway.
But should we switch from overriding to appending/prepending someday, we
could get unexpected behaviour, so that's why I'm switching to
nix.nixPath here.
Thanks to @devhell for bringing this to my attention.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
The option is no longer called services.virtualboxHost but now
virtualisation.virtualbox.host. See NixOS/nixpkgs@6440e9b for more
details.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here we have our actual implementation. Note however, that one can still
build an ISO image out of any machine by using:
nix-build machines -A machine.attr.iso.config.system.build.isoImage
However, none of these ISOs are built by default, except for kzerza,
which has vuizvui.createISO enabled.
The implementation has one little goof as it creates empty attrsets if a
particular machine doesn't have createISO enabled. But for our current
purposes that's okay "enough".
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
We only really need an ISO image for kzerza, as mentioned in the
previous commit, because that's the one that's really dd'ed onto an USB
stick.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
Includes changes for the new Rockfabrik dancefloor/stage setup.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts the following commits:
b0a2a69: profiles/base: Temporarily disable hinotify tests.
fc35a3d: profiles/base: Properly disable hinotify tests.
These are no longer needed as it has been quickly fixed upstream at
NixOS/nixpkgs@e75e0d9, thanks to @peti.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Using nixpkgs.config.haskellPackageOverrides isn't going to work for
NixOS configurations, because the other packageOverrides will override
the haskellPackageOverrides with a new instantiation of <nixpkgs>.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Build failure is here:
https://headcounter.org/hydra/build/722122/nixlog/1/raw
I'm overriding this in the base profile for now to get my main
workstations up to date ASAP.
Cc: @peti
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
It has been a long time (~2 months) since I've been back to my
workstations, so there was a new kernel release in-between.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@e3a5bca, signed binary caches are mandatory, so
let's set it in our default profile for vuizvui.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The current master version includes a few fixes I made for setting
default values for the Rockfabrik stage setup, which is to be used by my
machine called "kzerza" (booted solely via USB storage device).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
Since d2ff1a9, we now set a new NIX_PATH instead of patching <nixpkgs>,
which is way less error-prone and get less unexpecting results if we
evaluate against an unmodified <nixpkgs>.
So, patching <nixpkgs> is obsolete and thus removed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
We don't want the ExecStopPost action to run whenever GrandPA exits with
a failure state, because this would make debugging very nasty ("Noooo,
don't shut doooooooow... DAMN!"), especially on read-only media.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was the behaviour back then when NixOS still used upstart and after
some searching I found that ExecStopPost is what we want here, despite
its name (I'd imply that it is used in parts to stop the service rather
than executed after the service has stopped).
So in turn, it means that using Ctrl-Q within GrandPA shuts down the
whole system.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
We can't really do a "mkForce {}" or "mkForce null" on the submodule
type and the upstream module throws an error on null values, so we
simply define a dummy fileSystem with the noauto option set.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|