| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
The standard functins in `malloc.h` are exported by `stdlib.h`, and
`malloc.h` is highly linux-specific.
See
https://stackoverflow.com/questions/56463049/should-mac-osx-have-a-malloc-h-file/56463133#56463133
and
https://stackoverflow.com/questions/12973311/difference-between-stdlib-h-and-malloc-h
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@466f5e534688049be2ed6e75ae5659633016b45e, libinput
is enabled by default for Plasma 5, so we no longer need to explicitly
enable it anymore.
Furthermore, there was brawndo as the only machine still using
Synaptics and it's about time it's using libinput as well, so I
subsequently removed synaptics there.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@c814d72b517bb201c8bbbfc64e386c7023352886, a lot of
packages now no longer have a name attribute but instead use pname, so
when checking the package name within allowUnfreePredicate we need to
make sure that we fall back to a default if the name attribute is not
present.
This fixes evaluation of the machine, however I didn't check if it
actually builds.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
I'm not really using it.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Most machines are Intel, but not all, therefore we must now apply CPU
microcode updates to different manufacturers explicitly. Something that
needs DRYing, yet again.
|
|
|
|
|
|
|
|
|
|
|
| |
This option has been moved to a more generic "location" option in
NixOS/nixpkgs@c4de0bf49289bc6b1448420dea39d7a5b0f3c374, so in order to
fix evaluation for all our machines, let's switch to the new option
instead, which is equivalent in functionality to
services.redshift.provider.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A recent change[1] that has been merged to nixpkgs master has factored
out the generation of the options in (among others like JSON) DocBook
format into pkgs.nixosOptionsDoc and subsequently also changed the path
of the XSL files.
Ideally, the generation of the manual on our side would also just use a
single function that is provided via nixpkgs for generating the *full*
manual. The nixosOptionsDoc function however provides *only* the option
list in DocBook format, which is useful to *some* extent but doesn't
deduplicate the extra params we give to DocBook (eg. style sheets for
syntax highlighting).
This and the fact that I only have limited time at the moment is why I
left all the other crap we duplicate on our side as-is and only change
the path to the XSL files.
[1]: https://github.com/NixOS/nixpkgs/commit/5cfd034af0afe55e4d25748ec986c71b3bfbe3dd
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Both strace and xt are trace log formats, so imposing my own distaste
for overly long line length won't make a difference, as they won't
change their "coding style" ;-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Unfortunately these days I have to debug a lot of PHP code, so having
syntax highlighting (even though the syntax file is pretty terse) and
being able to fold Xdebug traces is quite useful to have.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
Let's stick with Cloudflare's primary and secondary resolvers.
|
|
|
|
|
|
| |
Unfortunately gunnr can't access syncthing from its network, and so
there's no point in having it run. Looks ugly and needs to be DRY-ed at
some point in time, but that'll have to wait.
|
| |
|
|
|
|
|
|
|
| |
Compton has been bumped to version 7, and with it the nix definition has
changed. Additionally to adopting the new options I'm also moving
compton to the overall services and have removed compton references from
each machine.
|
|
|
|
|
|
| |
So, instead of using polybarFull, which has issues and doesn't suit me
in its new incarnation anyway, I'm just expanding the super with the
options I want.
|
|
|
|
|
|
| |
This reverts commit 3343afb7c0734dbbd6953eb0cbd6558f8b81b119.
Turns out this isn't working after all.
|
|
|
|
|
| |
Now that my shiny new TypeMatrix has arrived, we'll be using the
superior dvorak layout.
|
|
|
|
|
| |
polybarFull has everything I want (and didn't even know of), so let's
install that instead.
|
|
|
|
|
| |
Turns out, it's actually really good for writing chapter drafts in
Markdown.
|
|
|
|
| |
This is better controlled via browser proxy settings.
|
|
|
|
| |
Never mind. This doesn't work, of course.
|
|
|
|
|
| |
With this set the timezone should be automatically set as promised by
services.localtime.
|
|
|
|
|
| |
When one travels with one's laptop, one does not wish to be disturbed by
having to manually configure a TZ. How plebish.
|
|
|
|
|
|
|
|
| |
I can't keep `offlineimap` as a service that applies to all, simply
because `gunnr` will never be able access IMAP from its network.
There's therefore little point in having it try to connect. So, instead
I've moved the service to all machines that are expected to be able to
access emails.
|
|
|
|
| |
What would we do without Arch Linux' wiki, I wonder.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Besides using the default value from options, I could have just used
mkOptionDefault back then when I was writing this, but fortunately using
the default attribute from the option itself now resulted in an eval
error.
Had I used mkOptionDefault, the value just would have been silently
changed to the default value, since in
https://github.com/NixOS/nixpkgs/pull/63810 the default value now has
priority 1000 instead of 1500 (mkOptionDefault).
So since there is no longer an option default, we now can just set our
binary cache in a singleton list (with priority 100) and be done.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
Still not working properly.
|
| |
|
|
|
|
|
|
| |
Now that my machine landscape also includes AMD, having a blanket
`thermald` service running makes no sense. All Intel-based machines now
have a `thermald` service explicitly enabled instead.
|
|
|
|
|
| |
I've been wanting to test ZFS for a while now, and since 0.8 we have
stable encryption and TRIM support for SSDs.
|
|
|
|
| |
Everything is locked down, but thankfully we have an NTP running. Phew.
|
|
|
|
| |
Otherwise keyboard-controlled volume won't work.
|
|
|
|
|
| |
Makes little sense on this machine and only provokes weird behavior
obviously. Don't know why I even put it in the first place.
|
|
|
|
|
| |
Fails some tests on hydra right now and it's not very important for me
to have at the moment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After using Gajim for years now, I got really frustrated by all its
warts, which mainly boil down the lack of type safety and its
interactions with its plugins.
Of course, I could also rip apart the plugin mechanism and Nixify them,
but in the end, the issues would still persist without a myriad of
tests that I don't have time right now to write.
After discovering a while back that Psi development has gained some
activity I decided to take a look into it a few weeks ago and while
there is certainly always things I don't like about some detail, it's
IMO a way better base for my future XMPP client.
So goodbye Gajim and hello Psi :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
This is supported by the Stratagus/Wargus engine and it's using the data
files from the GOG version.
I had this laying in the repository for a while but didn't commit and
push it yet, so let's call it done by now :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is from the current 2.0 development version and has most of my own
configuration preferences built-in.
Right now, the theming is pretty much a work in progress and the chat
input currently shows black text on dark grey background, which is quite
a nuisance to use.
Another thing that's currently not working (or just for a very short
amount of time) are window manager urgency hints.
Nevertheless however, I'm already using it as my main XMPP client
despite these issues.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
| |
Brainfart.
|
|
|
|
|
|
|
| |
I'm bored of the names my machines have. Luckily NixOS makes changing
names as easy as changing underwear! So, let's use Valkyrie names
instead. Also, change the console font to something nicer, like the
default `Lat2-Terminus16` font!
|
|
|
|
|
|
| |
This is a new work machine. The configuration is based off of `titan`
and `skunkworks`. I expect there to be plenty of changes in the future
as I get accustomed to it and shape it to my needs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't recall the exact model which was used for that machine, but it
was definitely one that required version 5.70.
Now I made a pull request for nixpkgs a while ago[1], which hasn't been
merged and as I didn't have the chance to test it by myself I didn't
merge that pull request yet.
Since the user asked about that printer driver again, I decided to give
version 5.70 a shot in vuizvui only and merge it upstream, once the user
reports that the driver is working.
[1]: https://github.com/NixOS/nixpkgs/pull/58399
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When chomping the cache set UUID introduced in
6ae9056a5a82dd16b745188a7ee6122ed27239f0, this actually has brought a
bug to surface, because when the UUID wasn't chomped the cache device
hasn't been attached at all, because the resulting command looked like
this:
echo f994bcca-8e52-4b54-9c96-5f5af0711b55
> /sys/block/$bcache1/bcache/attach
Yes, that's a newline after the echo, so it's just echoing the UUID and
then writes *nothing* into /sys/block/$bcache1/bcache/attach.
Chomping the UUID now results in an error, because the attach is made
directly after creating the device.
So all we need to do here is wait until the cache device was registered
and then do the attach.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is basically a wrapper around ResidualVM, which I also patched so
that we can inject a basic config file from the Nix store that contains
the basic game information.
The ResidualVM build is pretty minimal in that we only use those
dependencies that we actually need for the game.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
|
|
|
|
| |
This is just a minor nitpick and doesn't actually change a lot in
functionality, but I chomped all the other occasions, so let's be
consistent here as well.
Signed-off-by: aszlig <aszlig@nix.build>
|