First of all: Do you need reproductibility? I.e. having the exact same system on multiple machines? If not NixOS might be a lot more complex than what you need.
Secondly: Instability does not mean what you think it means. People read instability and think the system will break, when instability actually means your system will be updated. In the context of a server, an update can be destructive, for day-to-day users it’s very rarely so.
Finally: why Arch or Nix, why not Ubuntu, Mint, Pop or any of the other dozens of distros that are usually recommended for new users?
I have also switched to Colemak and my advice is to just not do that. Just learn Colemak without looking at the keyboard, it’ll make you a better typist anyway and you can get comfortable with it within a few weeks. In particular you don’t want to move the little knobs on the index finger keys (F and J).
For everyday tasks, I think a Fedora distrobox works fine, but you would have to upgrade it eventually and I admit I’m not sure how you do that under distrobox. Still, I initially used it and still have a Fedora distrobox I use for doing stuff for my job, as well as one I use for running a game modding program that requires Java, and they both work fine.
I’ve also had success with a Debian distrobox, which I used to compile Render96ex. Debian is pretty universal, so it’s much easier to follow compile instructions using it than a Fedora distrobox ^^’
Python is easy on NixOS, you just need to use python venvs and you can use pip like normal
(python -m venv .venv) to create the venv (only need to do once per project)
.venv/bin/activate to enable the venv (Vscode should do this automatically if you create the venv through the python extension)
Then just pip install to your heart’s content
(Probably a good idea to pip freeze > requirements.txt every time you install a new library too to make it reproducible
Also you should probably add the venv directory to gitignore if you’re using git as it’ll add a lot of crap to source control that can be easily regenerated from the requirements.txt
I think Docker is a tool, and it depends on how you implement said tool. You can use Docker in ways that make your infra more complicated, less efficient, and more bloated with little benefit, if not a loss of benefits. You can also use it in a way that promotes high uptime, fail-overs, responsible upgrades, etc. Just “Docker” as-is does not solve problems or introduce problems. It’s how you use it.
Lots of people see Docker as the “just buy a Mac” of infra. It doesn’t make all your issues magically go away. Me, personally, I have a good understanding of what my OS is doing, and what software generally needs to run well. So for personal stuff where downtime for upgrades means that I, myself, can’t use a service while it’s upgrading, I don’t see much benefit for Docker. I’m happy to solve problems if I run into them, also.
However, in high-uptime environments, I would probably set up a k8s environment with heavy use of Docker. I’d implement integration tests with new images and ensure that regressions aren’t being introduced as things go out with a CI/CD pipeline. I’d leverage k8s to do A-B upgrades for zero downtime deploys, and depending on my needs, I might use an elastic stack.
So personally, my use of Docker would be for responsible shipping and deploys. Docker or not, I still have an underlying Linux OS to solve problems for; they’re just housed inside a container. It could be argued that you could use a first-party upstream Docker image for less friction, but in my experience, I eventually want to tweak things, and I would rather roll my own images.
For SoC boards, resources are already at a premium, so I prefer to run on metal for most of my personal services. I understand that we have very large SoC boards that we can use now, but I still like to take a simpler, minimalist approach with little bloat. Plus, it’s easier to keep track of things with systemd services and logs anyway, since it uniformly works the way it should.
Just my $0.02. I know plenty of folks would think differently, and I encourage that. Just do what gives you the most success in the end 👍
It’s the only option I know but thankfully it is easy as piss. Just figure out your key to enter bios (usually ESC or f12, you may need to try the Fn key and f12 for obvious reasons), restart and enter the bios, slide around until you find the option, select, change, F10 to save and exit and you’re good. May even want to set a bios password while you’re in there, why not? Should take like 10-15min.
To the folks who posted useless comments instead of actually helping: Thanks for nothing.
I don’t know what you expected. There’s no need to be rude. Installing a Flatpak for example is a very valid answer and would definitely solve the problem.
And initially you didn’t even say how did you install brave, which is quite relevant in order to find a solution.
Edit: You put the error in a screenshot which leaves it rather useless for searching the error in the web. In general, I’d say that you have very little error solving skills and instead of thanking for “nothing” you should be thankful that people even bothered to answer.
“Installing a Flatpak for example is a very valid answer and would definitely solve the problem” That wasn’t a useless comment. Although it would not have helped, it was still in the right direction. Useless comments are those claiming that I should stop using brave and just stick to firefox.
“You put the error in a screenshot which leaves it rather useless for searching the error in the web” I put the screenshot so that nothing is missed and I have seen this previously.
“In general, I’d say that you have very little error solving skills” I would say that you have very weak probabilty and statistics skill, if you can generalise the entire sample space with just a singleton event.
“and instead of thanking for “nothing” you should be thankful that people even bothered to answer.” Again, not directed to people who gave technical help or asked questions but only to those suggesting I just stick to FF or give up Brave.
Going to sound like a boring pleb but… if your OS takes less than 1h to install and setup (which is my experience with Debian/Ubuntu on a SSD with a fiber connection, or even on a RPi with a modern microSD on an ADSL connection over WiFi) then it doesn’t matter much what you use. You grab a mug of coffee, click here or there from time to time and if your /home partition is saved you are good to go faster than most people even respond to an email.
I should add if you want to tinker “shallowly” containers are amazing. If you need to tinker deep, using a VM proper or even another physical machine (with a KVM or another keyboard and monitor) while your main machine remains untouched, it should NOT affect your uptime.
I think the funniest part of this is I was recently preparing some laptops for work with Windows 10 and it literally took 6 hours thanks to slow updates, one laptop corrupting the keyboard and touchpad driver so completely it required a full reinstall (on a fresh install mind you) and other impressively terrible snags. Granted it would’ve been more like 1-2 hours if I started with an install image that wasn’t about 2 years old, but it was still impressive how much of a time sink it was
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.