| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I had this laying around locally for a year now and I'm still not really
happy with some things, for example not having yet full source builds of
the extensions and a few config options not yet managed by Nix (eg.
search engines).
However, since Firefox takes a while to build it's a bit tedious to
always do it directly (and locally) after I update my machines. Having
this part of my workstation profile should make sure that my version of
Firefox is available at all times.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
When you have a lot of branches it's sometimes tedious to find out the
ones you've been working on recently. Sorting the branches by committer
date by default should make it more obvious.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quoting from https://github.com/i3/i3/pull/5173:
A bug was introduced in https://github.com/i3/i3/pull/5118 in which
configs with bar blocks will segfault during validation. They were
copying the i3 font which is not set during validation. This PR simply
checks that the load_type is not validated before copying the font.
This fixes the Hydra build for the i3 configuration on my machines.
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|
|
|
|
| |
Even more packages are being renamed.
|
|
|
|
| |
More packages have been renamed recently.
|
|
|
|
|
|
|
|
| |
Due to unnecessary renames in
https://github.com/NixOS/nixpkgs/pull/161146
I replaced the packages with the ones the error messages mentioned, I
have not checked whether they are actually a no-op replacement.
|
|
|
|
|
| |
pulseaudioLight has been the same as pulseaudio for a while (apparently
since 2018). The alias has finally been removed now.
|
|
|
|
|
| |
This has been renamed upstream at some point and subsequently produced
eval errors.
|
|
|
|
|
|
|
|
| |
Since I regularly use this for recovering data from various hard drives
and it's also a good idea to have it at hand with no Internet connection
in case something bad[TM] happens, let's make it available everywhere.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm already using this config since a few months and since I'm slowly
getting used to it, let's try to make it the default for my workstation
profile.
Unfortunately, libgit2 uses the Git configuration from /etc, but our
configuration is directly patched into Git and not in /etc but in
"${pkgs.git}/etc", so we need to patch libgit2 to use the right
configuration file.
Another goof is that we can't use ${pkgs.delta} directly in our Git
configuration because it would introduce a circular dependency between
Git itself and delta (which uses libgit2 which in turn refers to
"${pkgs.git}/etc"), so for the time being I'm relying on $PATH for
delta.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
While ncurses already has support for detecting direct color terminals,
a lot of applications out there do not yet query terminfo but instead
rely on some shady COLORTERM environment variable. While I don't really
like that approach, patching XTerm to set that variable currently is
better than patching all the applications to query terminfo.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far, the TERM environment variable has been set to xterm-256color,
but in reality newer XTerm versions already supported 24bit colors so
setting this to xterm-direct results in using the right terminfo entry
for our terminal.
To make sure this is really the case, let's explicitly set directColor
to true, because while it is enabled in nixpkgs by default it is however
a compile-time option and could possibly be disabled.
Additionally, Vim is now looking pretty gruesome because my colorscheme
so far has used colors for 16-color terminals and I don't particularly
like the GUI colors. I added a few fixups for the color scheme to
address that.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
I haven't used the alias since a long time as it is probably apparent
due to the hardcoded "14.04" version of NixOS and given that I didn't
update the alias also speaks volumes about how useful it is altogether.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using vimdiff3 as the merge tool for a long time, but while it
has worked fine for most conflicts, using diff3 makes the original lines
visible which I always viewed in a separate shell rather than inline in
the editor.
Switching this to diff3 should hopefully make merge conflicts more
convenient to solve from now on.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In RFC-0042[1], the structural settings are exposed via a "settings"
attribute, while in our module it's called "config". To make this less
ambiguous (since there is already a "config" attribute passed to
modules) and more in line with best practices, I renamed it accordingly.
Additionally, the configuration file is now generated via *defining*
another (read-only) option, which can be used by other modules to
reference the path. The previous way this has been done was using the
apply attribute to mkOption, which makes it really hard to access the
original attributes for these settings.
[1]: https://git.io/JcXmU
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
A few things have changed since the recent NixOS 21.05 release. Mostly
naming stuff, so nothing dramatic.
|
|
|
|
|
|
|
|
|
|
|
| |
The previous commit introduced a few new eval errors, for example:
cannot find attribute `vuizvui.programs.flameshot'
This is because the actual attribute path is
vuizvui.aszlig.programs.flameshot and not the one above.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The PSI and Flameshot tests so far weren't part of the channels of the
machines where I use both programs, so if one of those tests would have
failed the channels would have advanced regardless of that.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
After all the goal was to move all hardware specific stuff to the actual
machine definition, which includes the boot loader.
Since GRUB is enabled by default but with a higher priority value, we
now no longer need to mkForce-disable the option for machines using
systemd-boot.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The new hardware for dnyarri no longer contains an Intel CPU, so apart
from switching the microcode updates to AMD I also removed the setting
from the base profile because it clearly doesn't belong there.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
So far I've almost exclusively used scrot for screenshots, but most of
the time I used an image manipulation program to pixelate stuff, add
descriptions or draw arrows.
Flameshot combines this in a single application, so I expect that from
now on I can spam-post screenshots in even a higher rate than before ;-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
nixpkgs has removed flash support in chromium without replacement in
d55603f11d36ae38ca76dec8d95bc55d2115f104 following the removal in
upstream chromium M88, so I'm disabling it completely in
vuizvui.user.aszlig.profiles.managed to fix the evaluation of shiki
and brawndo.
cc @aszlig
|
|
|
|
|
|
|
|
|
| |
The kdeApplications attribute got removed from the top-level a while
ago, so the machines using the "managed" profile no longer evaluate.
Instead, the plasma5Packages exposes the same set of packages.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
I no longer use this plugin and since evaluation currently is broken
upstream (blocked by [1]), let's make sure that at least the rest of
Vuizvui continues to evaluate.
[1]: https://github.com/NixOS/nixpkgs/pull/109679
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
I no longer use Taskwarrior and since my config.patch fails to apply in
the most recent release, I think it's time to finally remove it from my
workstation profile.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a common pattern I encounter on a daily basis, which involves
copy & pasting the store path of a failed build to "nix log".
Now the same is just a matter of running "nlast" and we get rid of the
useless copy & paste.
The way we do this does have a small goof: Using mtime (or really any
time, other than atime, which commonly is disabled) is not going to work
if we *repeat* an older Nix build, since this will only change the log
file but the prefix directory will be unchanged.
Since addressing this goof would most likely result in iterating through
*all* log files, I'm not doing it since I think it doesn't occur very
often in practice. If I happen to be wrong on that, we could still go
for the heavyweight solution.
Also, I went for implementing this in Python instead of a shell script,
because the latter would not only be less readable but also way slower
since we need to either fork out for every stat command or use ls and
head to figure out the newest file.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the "cryptography" Python library is marked as insecure I'd have
several options here: Add an excemption for the library, switch to
NixOps 2.0 or entirely remove it.
I chose to do the latter, since on all of my deployments I currently use
a heavily patched NixOps version which is somewhat of a mix between 1.5
and 2.0 and the version used here in the workstation profile is unused
since ages anyway.
In case I really need to use nixops on any of my workstations again, I
could still resort to "nix run".
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
The option has been renamed since a while[1] ago, so to get rid of
annoying warnings, let's actually switch to the new option name.
[1]: https://github.com/NixOS/nixpkgs/commit/c99bd9bedf7291390c28eddb31f
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The option has been removed upstream[1] and it only has been true by
default for a very small time frame in 2014[2] and I believe even
earlier (before the nixos -> nixpkgs merge) there was another occasion
where it defaulted to true.
However, with the option gone, this is now no longer necessary.
[1]: https://github.com/NixOS/nixpkgs/commit/aebf9a4709215c230e5841d60e2
[2]: https://github.com/NixOS/nixpkgs/commit/b792394119b8ffc4a2fd34a6704
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using this configuration since years already but so far it has
been residing in ~/.muttrc and I copied to new machines accordingly.
The reason why I didn't add it here was because the config was too ugly
and I never got so far as to properly re-do it.
Unfortunately, the config is still ugly as hell, but at least we now
generate it from a structured Nix format and also the IMAP/SMTP user and
server infos are now retrieved via gopass instead.
This also includes my small prank multipart/alternative filter, which
should hopefully "encourange" recipients to disable HTML
parsing/rendering.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The DOSEMU fonts we were using so far for CP437 were bitmap fonts only
and with no unicode support.
Luckily there is https://int10h.org/oldschool-pc-fonts/ - which is a
really cool font pack containing all the cool oldschool fonts that I
remember from my childhood and still use today for creating ASCII art.
Since we recently* hit the 21st century, I think it's about time that
even I should start having terminals with proper Unicode support. The
latter is already the case, but the glyphs just didn't display
correctly.
The font that I switched to (MxPlus IBM VGA 8x16) is using embededd
bitmaps, so I also enabled useEmbeddedBitmaps option, so that the font
still looks as crisp as the old DOSEMU font.
To make sure it really is the same font, I compared screenshots of all
the CP437 characters with the new font and they match the old font 1:1.
I also removed the liberation_ttf font, since it's already included by
the default NixOS font configuration.
* -> Your mileage may vary, but hey, the 90ies were yesterday, right?
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I regularily keep things in nix-env to see whether I keep using them and
"entry" is one of the little tools I ended up using quite regularily.
The program monitors a set of files via inotify and runs a command
whenever one or more of them change, which makes it quite useful for a
"change code, compile, run" cycle.
Upstream URL: https://eradman.com/entrproject/
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From the release notes of Git version 2.27.0:
* "git pull" issues a warning message until the pull.rebase
configuration variable is explicitly given, which some existing
users may find annoying---those who prefer not to rebase need to
set the variable to false to squelch the warning.
This is exactly the warning which is annoying me all the time now, so in
order to get rid of it, let's explicitly set the default behaviour
(which is doing a recursive merge).
Just to be sure that I really want the default behaviour, I analysed my
shell history for invocations of "git pull" and only around 20% of the
invocations were with --rebase, 14% were with an explicit URL (but no
rebase) and the rest were recursive merges.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
I've had this in my configuration.nix for a while and since I got used
to it, I think it's a good idea to enable both Nix Flakes and the "nix"
command by default for all my machines.
Signed-off-by: aszlig <aszlig@nix.build>
|