| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Most of the initial development is done on this laptop and it's going to
get into production mode. So having a Laptop with autologin is kinda
pointless, especially while you're travelling.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
Unfortunately, this is a requirement for Steam and other 32bit games, so
let's make sure it's available.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
This reverts commit bafb5933654cdb7e35f0c54418bdd0dcb999f98c.
We can finally drop that patch, because the issue has been fixed
upstream already.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Follow-up for #2c44e94b5ffacc291c6eb1d554d61500ec0e4ac8.
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit decd0f04f517e832e2479ec2543141399cc87c80.
Since NixOS/nixpkgs@9f0acda, the containers-imperative NixOS test is
succeeding again, so we don't need this workaround anymore.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
For now the containers-imperative tests are failing and containers
aren't used on this machine either, so let's just disable them.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 3f0a9e8002802e5a772b7582f8254c92d7a2a4d5.
It's now possible to disable support and tests for containers simply by
using config.boot.enableContainers in the machine config, because that's
the super option that enables all the container-related services and
tools in upstream NixOS and it's also enabled by default.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
New tests are since NixOS/nixpkgs@4f796c28d57887cc9812190bc99fb45b2a.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
This was a copy & paste error by me, because I copied the options out of
an existing configuration, which contained the CONFIG_ prefixes. Within
extraConfig of the generic kernel builder, we only use the names without
prefixes.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 9d4575855bf1ae2136d85a2d0aa7b5ede50cfc67.
The upstream issue systemd/systemd#3735 has been fixed and it got
included in systemd version 331.
Since NixOS/nixpkgs@51871dfb3777 we're also on version 331, so we
no longer need this patch in Vuizvui.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts the following commits:
4f4c778e424e72d51242dbfadde0a2a806efb68b
22fac6bad53e797ca84d7c7ac7e0fca3c0a912c8
We can now move Tomahawk back to the corresponding profiles/machines,
because the build has been fixed in f7e934e74595a0d7524159d6faa1b2bb5d.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the build for Tomahawk because some of these dependencies
were already refactored in upstream <nixpkgs> and hence we can simply
specify the dependencies directly.
Alongside of this, I've broken out some of the buildInputs into
nativeBuildInputs, so this will stay safe for cross compilation.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
This reverts commit 267b8363695190f2d0834892b4b1159d7918d447.
Issue NixOS/nixpkgs#15498 is already fixed upstream, so this ugly
workaround isn't needed anymore.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
Let's enable the options that *should* work with this kind of hardware
regardless whether it's currently working in mainline. It doesn't make a
huge difference to the kernel configuration prior to this change, but
let's better compile in these options rather than wondering why some
hardware isn't working.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
| |
Okay, that didn’t do what I thought it would.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Testing if that improves streaming.
|
| |
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I've copied the notsure config, which wasn't an EFI system, so let's
actually use systemd-boot here, shall we? ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This is to get a first working channel for bootstrapping. Fixing the
test is the long-term goal of course, so this is only temporarily.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
Unfortunately, this is currently necessary for the Broadcom wireless
drivers.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
Hardware-specific info largely from nixos-generate-config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
Just because it doesn't build at the moment and just temporarily.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This one more or less shares the same profile as "notsure", but I'm too
lazy right now to consolidate and/or modularize everything properly.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
It hasn’t been merged into nixpkgs yet.
|
| |
|
|
|
|
|
|
|
| |
Due to bandwidth constraints I'm not using Tomahawk at the moment and I
don't have time to investigate the current build failure.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Gah, yes, I'm still waking up and my eyes are not working already...
Accidentally copy & pasted tho wrong hash in there.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
Nothing very scary here, just getting things up to date.
This also reflects on my choices of kernel options, most of them
probably are unnecessary but I'm going to rip apart the whole kernel
config very soon[TM] anyway.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I no longer use VirtualBox on any of my machines anymore, so let's
remove it for good :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
I hate you, gpg-agent. Go die in a fire.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
i3bar seems to close the FD for stderr, so conky will get a broken pipe
error when writing error messages to stderr.
Of course in the long run it's better to log these errors somewhere
where they can be inspected later.
But for now, it's better than terminating i3bar altogether, because
that's really annoying ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This seems to be related to this bug:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434986
The problem here is a race condition, because NetworkManager is trying
to pick up the device _before_ the renaming and then fails to correctly
identify it.
Another solution would be to reorder the service unit after the networkd
service, but that would only work well if the interface is plugged in at
boot time and if it's pluggen in/out afterwards we likely have the same
problem again.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|