How did you install nixos? The labels for disks and partitions are usually set during creation.
If the KDE-spin installer did not need to reformat the disks (i.e. the partition sizes and formats didn’t change) it probably didn’t touch the partition labels.
You can change the label if it bothers you, just make sure fstab doesn’t use the old label :)
On macOS the version on /usr/bin/bash is very old (bash 3 I think?), so many users install a newer version with homebrew which ends up in PATH, which /usr/bin/env looks at.
Protip: I start every bash script with the following two lines:
sh
#!/usr/bin/env bash
set -euo pipefail
set -e makes the script exit if any command (that’s not part of things like if-statements) exits with a non-zero exit code
set -u makes the script exit when it tries to use undefined variables
set -o pipefail will make the exit code of the pipeline have the rightmost non-zero exit status of the pipeline, instead of always the rightmost command.
The best thing is to use a different device, period.
Since the company is lord and master over the device, in theory, they can see anything you’re doing.
Maybe not decrypting wireguard traffic in practice, but still see that you’re doing non-official things on the device that are probably not allowed. They might think you’re a whistleblower or a corporate spy or something.
I have no idea where you work, but if they install a CA they’re probably have some kind of monitoring to see what programs are installed/running.
If the company CA is all you’re worried about, running a browser that uses its own CA list should be enough.
Maybe your drive(s) fail and you want to reinstall.
Then you already have a setup with all your software and config files installed. Just reinstall NixOS and re-apply your configuration (or build your own Install ISO ).
And if you ever get a new laptop/desktop/VM/VPS you can do the same.
Don’t forget to take backups, regardless of your setup tho.
The reproducibility also leads to some surprise features, like being able to wipe your entire system on every boot. Since NixOS always puts the necessary files in the correct place, this is perfectly fine. If you then add some mechanism to persist specific data across reboots (a separate partition, or the Impermanence module), you will remove all kinda of randomly accumulated files on every boot.
This means I have very small backups, because I have three kinds of data: stuff that is wiped on every boot, stuff that is persisted but not backed up (/nix/store, all kinds of caches) and stuff that is persisted and backed up (documents, repositories, media).
None of my OS’s files are in the backups, which makes of them a lot smaller than my previous arch install.
Python development shouldn’t be that hard I think. You can just drop a shell.nix that imports your pyproject.toml and then you can run nix develop and have all your dependencies installed seamlessly with poetry2nix.
I’m using neovim so I can’t really help you with vscode, sorry.
That’s basically sort by controversial, no?