| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
The virtmanager attribute has been renamed a while ago[1] to its
upstream name (virt-manager) and referencing the alias will now[2] throw
an evaluation error.
[1]: https://github.com/NixOS/nixpkgs/commit/5b640bfd089904bfe806606b8b2
[2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
The attribute has been renamed[1] to iproute2 a while ago and recently the
alias was converted to a throw[2], so let's do the rename on our side as
well.
[1]: https://github.com/NixOS/nixpkgs/commit/20a9caf0a474e182909ac850fa6
[2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The posix_man_pages attribute has been renamed in nixpkgs[1] to
man-pages-posix to more closely match the upstream name. This now[2]
results in an evaluation error.
[1]: https://github.com/NixOS/nixpkgs/commit/4461230cc5e11952407f8ddd205
[2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some personal history on this:
I started to get used to AT&T syntax because it's the default in GDB and
used that ever since until I one day starting to do some more reverse
engineering using radare, which defaults to Intel syntax.
Ever since then probably my most used command in GDB was "set
disassembly-flavor intel" (because I was to lazy to add it to the
config) because I constantly got confused by the source/destination
operand swaps. This even happened during live reverse engineering at rC3
where I was confused about some function logic only to find out that I
was viewing in AT&T syntax.
Fast-forward to today: I'm debugging some application using WINE and
winedbg uses AT&T syntax, which I didn't like at first. After reflecting
on this for a while, I thought it would probably be better to get used
to AT&T syntax again and switch everything to use AT&T for the following
reasons:
* Operands are more natural to read, since most libraries/APIs in
higher level languages do it like this (well, except memcpy, strcpy,
etc... maybe I now get confused by libc functions...)
* AT&T syntax feels less verbose, for example "mov ecx, dword [eax]"
is just "movl (%eax), %ecx"
This very commit makes sure that radare2 now defaults to AT&T syntax
instead of eg. ensuring that GDB uses Intel syntax by default.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
Just had to scan the credentials for a Wi-Fi access point and they were
only available via QR code, but was unable to make it available via Nix
shell because I had (for obvious reasons) no access to the Internet.
Adding zbar to all my machines will ensure that something like this
won't happen again.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
Back then when I added the font pack in 0171f8d895efd46300ba01c6adeb7aa,
version 2.0 was not yet merged to nixpkgs. This has happened in the
meantime and the current version is version 2.2 and I also do not see
any reason to keep the 2.0 version in Vuizvui.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After countless boots with unlocking my LUKS containers and thereafter
logging in via lightdm I started to wonder whether it really makes sense
to do the latter.
All of my workstations are single-user, I usually don't switch my
session type (and even if, then via system configuration) and if someone
manages to unlock my LUKS containers, it's really trivial to circumvent
the user authentication.
So if I'm not forgetting about something big[TM], the only purpose this
additional auth serves is me being annoyed for no reason, so let's
disable it if the configuration indicates that LUKS is used.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
With my new laptop, a font size of 12pt is rather large and given that
hidpi displays usually have a quite large resolution (the name might
hint at that), we don't necessarily need to use embedded bitmaps anymore
which was one of the reasons why I used a point size of 12.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After resume from suspend the NVMe does not wake up again when the
device was put into D3cold. This is something that is worked around by
TUXEDO Tomte[1] via udev rules. However, I personally don't like this
approach and it can lead to race conditions when we're going into
suspend before udev is initialised.
Interestingly, the device does even go into NPSS via APST, but if
changing to D3cold while APST is enabled, the device does not wake up
again.
Right now I just added a new quirk to disable D3cold during device
probe for now, but we could maybe find a better workaround eg. by
disabling APST before D3cold and re-enabling it again. Not sure whether
this is feasible, but since I have limited time right now I can't dig
more into this.
[1]: https://github.com/tuxedocomputers/tuxedo-tomte/commit/2c8d71170868a2663705fbea6ac150eecb96e6ce
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
This stopped working for me for some reason, so no point in keeping it
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of the options in nix.conf are now exposed as a submodule with a
freeform type and since that change[1] got introduced, we get a bunch of
warnings during machine evaluation:
trace: warning: The option `nix.useSandbox' defined in `...' has been renamed to `nix.settings.sandbox'.
trace: warning: The option `nix.maxJobs' defined in `...' has been renamed to `nix.settings.max-jobs'.
trace: warning: The option `nix.buildCores' defined in `...' has been renamed to `nix.settings.cores'.
To shut them up, I went through all machines and modules and renamed the
remaining options that were not renamed back then when @devhell did some
renames in a0297bf921399c3243dcca99626d8697f0735abe.
This was done by looking through the output of:
$ git grep -A 10 '\<nix\(\.\| *=\)' machines modules
After that I tested the contents of the nix.conf of all the machines
against the changes this commit introduced via the following command:
$ nix-build --no-out-link -E '
with import <nixpkgs/lib>;
map (m: m.eval.config.environment.etc."nix/nix.conf".source)
(collect (m: m ? eval) (import ./machines))
'
I've sorted the resulting nix.conf files and diffed on that result and
the only difference that showed up was the following:
allowed-users = *
-auto-optimise-store = false
auto-optimise-store = true
builders-use-substitutes = true
cores = 0
This is because the previous way to generate the config was by
concatenating strings whereas the new way works on an attribute set, so
we get deduplication by design.
[1]: https://github.com/NixOS/nixpkgs/pull/139075
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
Cc: @Profpatsch
Cc: @sternenseemann
|
|
|
|
|
|
|
|
| |
I use perf on a regular basis and since it's dependant on the currently
running kernel version, it' just makes sense to have it available at all
times rather than "nix run" it with the right kernel version.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The package has been removed and we're getting the following eval error:
error: 'docker-edge' has been removed, it was an alias for 'docker'
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now we're getting an eval error like this:
Failed assertions:
- You have set services.power-profiles-daemon.enable = true;
which conflicts with services.tlp.enable = true;
Since the machines in question are for desktop environment users, TLP
doesn't make a lot of sense. Besides, the option should not be defined
in managed.nix anyway, because it's a hardware-specific option.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upstream project seems to be no longer maintained[1] and the last
release from 2005 contains a whole bunch of outdated NIC information
so that it became pretty annoying to use.
Back then jwhois was the only whois client packaged in nixpkgs, so this
might be the reason why it ended up in my setup in the first place.
The "whois" package on the other hand seems to be actively maintained
and works well for the domains I care about.
[1]: https://github.com/jonasob/jwhois/issues/32
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is mainly for having a consistent and central way to define our
keybord config. The main reason for doing so is because of Slylandro,
which comes with a keyboard that has a caps lock key atop the left shift
key and it drives me mad.
Since I'd like to keep things DRY, let's just use XKB for everything
keymap-related.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Since libgit2 version 1.5.0, sysdir.c is in a subdirectory called
"libgit2", which was made to distinguish the sources from the ones in
the CLI tool and util.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The options in services.graphite.api and services.graphite.beacon got[1]
removed[2] in nixpkgs because the upstream project doesn't seem to be
maintained anymore.
More information can be found at:
https://github.com/NixOS/nixpkgs/pull/180950
[1]: https://github.com/NixOS/nixpkgs/commit/1f18d441063208968f38bed0fe5
[2]: https://github.com/NixOS/nixpkgs/commit/ada1d87767b8826ea6233952279
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
I think the `null` still came from the nixpkgs module.
Not sure whether upower will like an empty config file, but we’ll see.
|
|
|
|
| |
Yay static linting.
|
|
|
|
|
|
|
|
| |
Not updating the microcode on thinkpads is kind of a death sentence
for some kernel updates, so let’s do it by default.
In case somebody uses it for an AMD thinkpad in the future, we might
have to check whether the option creates a problem.
|
|
|
|
|
| |
Changes the weechat setup so that I can have multiple instances, each
gets their own unix user & separate weechat instance.
|
| |
|
| |
|
| |
|
|
|
| |
Which has apparently been compromised upstream. Yay.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This gets rid of the following warning:
trace: warning: The option
`services.openssh.challengeResponseAuthentication' defined in
`.../modules/user/aszlig/profiles/base.nix' has been renamed to
`services.openssh.kbdInteractiveAuthentication'.
The option actually didn't make sense in the first place because it was
an alias leftover from SSH 1.
I also changed the priority for the OpenSSH options from 1000 to 500 to
avoid any future conflicts should the upstream module use mkDefault one
day.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
I just was forced to reboot my workstation while working on a program
that sets the VT into raw mode but finding out that the unraw key now
doesn't work anymore. This used to be the case but with the sysctl
include that comes with systemd-coredump, the kernel.sysrq value
defaults to only allowing sync (16).
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
Cos I'm an idiot at this time of night.
|
|
|
|
| |
`youtube-dl` is dead, long live `youtube-dlp`!
|
|
|
|
| |
With `termusic` in the repos there's no need for musikcube.
|
|
|
|
| |
Hot-loading this is getting annoying, so I'll just add it.
|
|
|
|
|
|
| |
I've not come across anyone actually using this. Additionally, it's not
OSS, so there's not much reason to keep it around. Oh, and the build
fails.
|
|
|
| |
Was removed from nixpkgs upstream.
|
|
|
|
| |
Gotta try all dat pipewire love.
|
|
|
|
|
|
|
| |
Gosh, today my brain really doesn't work very well it seems, because I
actually forgot to add the first hunk via "git add -p".
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regression introduced by 25a077f90a0005b519db071a6b5b4d20bd6d2d45.
I usually let Vim perform a syntax check on the Nix file I'm editing,
which usually displays errors. However, given that the zsh module is one
of my older modules where I did a big "with lib;" over the whole scope,
a nix-instantiate --parse didn't find the missing pkgs argument.
So apart from just fixing the error, I removed the "with lib;" and also
moved from the old lib.overrideDerivation to package.overrideAttrs.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
Regression introduced by 652ac49da16123016c36537dc28331649a63bf7b.
This breaks the build of the manual because the <literal/> tag wasn't
closed.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm already using zsh-fast-syntax-highlighting since weeks via the
configuration.nix and I actually forgot why I used this implementation
rather than one of the others out there.
However, since I'm also using Nushell[1] on a regular basis, I got quite
used to syntax highlighting so that's why I added it to zsh as well.
[1]: https://www.nushell.sh/
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
I've been testing 0.5 for weeks now and already got sufficiently used to
it so that I'd become blind if it would be the default value (1.0).
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
| |
Since the old URL had all sorts of issues ranging from no HTTP/2 support
to issues with XSRF protection, I decided to move the Hydra instance to
https://hydra.build/ - a domain that I had laying around since years but
didn't use so far.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
We should restart the service if its config changes. Since the service
file from the upstream distribution is used, we have to manually add a
trigger for that to happen.
|
|
|
|
|
| |
Upstream is dumb, but the tool is certainly useful, so let’s patch it
to make it workable and then also patch the nixos module …
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm particularly interested in `gurk-rs` as it's a Signal client that
runs in the terminal. It's in early development but it looks already
amazing and it doesn't rely on the Java library.
`termusic` is also a nice music player written in Rust that I've come to
enjoy when MPD doesn't make sense.
Lastly, `writedisk` is just mad awesome. It can write ISOs of all sorts
to USB stick, and it even knows how to deal with Windows ISOs. It writes
those ISOs really fast as well, so I'm guessing it somehow measures the
ideal block size. Either way, this is much more convenient than having
to invoke `dd` every time I have to write an ISO. Funny enough, this too
is a Rust application.
|
|
|
|
| |
Once again, I forget that some parts of my system still need this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I had some weird issues with the low-battery udev rule, mainly it not
triggering when it should. Usually, the event would only get processed
when the battery changed state, e.g. from Discharging to Charging.
Consequently, the laptop would hibernate when you'd save it from running
out of battery by plugging it in, but, if you forgot, it'd be content to
run out of battery.
I'll try upower instead now which is the “normal” solution used by the
major desktop environments. It's has some extra complexity, as it also
provides a d-bus API for other applications to use, but we'll see how it
goes.
|
|
|
|
|
|
| |
This kernel module is required for some operations supported by
TLP (e.g. tlp recalibrate), so we should enable it and be it to prevent
confusing error messages (as I encountered).
|
| |
|