Maybe you can

There is no such thing as idiot-proof steps to tamper the registry. Most of those registry keys are not documented, and it’s very hard to be completely sure about what you are touching.

If you need a debloated experience, install LTSC.

It was the last remaining exam before my deletion from university. I wish I could attend the lectures, but, due to work, it was impossible. Also, my degree is not fully related to my work field. I work as a software developer, and my degree is about electronics engineering. I just need a degree to get promoted.

What models have you tried? I used local Llama 3.1 to help me with university math.

It seemed capable of solving differential equations and doing LaPlace transform. It did some mistakes during the calculations, like a math professor in a hurry.

What I found best, was getting a solution from Llama, and validating each step using WolframAlpha.

Sure, in many cases the dev’s computer is powerful enough to handle that.

However:

• The more the dependencies, the more likely it is to pull-off a supply chain attack. Any of those thousands modules can be compromised and infect either the user or the developer.
• Not all computers are optimized for working with so many tiny files. Have you ever worked in a company that uses McAfee Antivirus? Even Defender can be a massive performance hit in some cases.

I had read about it on another thread, which was about using old smartphones as servers (they used Termux).

Those old lithium batteries, although sometimes seemingly healthy, can catch fire any time. Having them connected to the charger 24/7 is only making matters worse.

I wouldn’t trust the battery of old devices. I would probably buy a used UPS (without battery) and slap a new battery to it. This would cost more, but it would allow me to also connect other important devices to it - like the router and some lights.

I have a Wyse 5010. Be careful with your SSD plans. Mine had an mSATA SSD. Luckily, after removing the chassis of a SATA SSD, and only keeping the board, it could fit in there.

I feel the importance of user privileges distinction, as I see it from a server perspective and organization managed devices. Some would argue the insignificance of this in the personal desktops.

However, I believe that the community structure of Linux is benefiting everyone. It is a general purpose kernel, that gets improvements from various different sectors. In the current space, where most servers run Linux and most desktops run Windows, desktops are not benefiting from filesystem or scheduling optimizations implemented for servers.

I had a look at Haiku some months ago. Its single user architecture is an interesting choice. I mean, you don’t need to worry about privilege escalation exploits, if you are always fully privileged /s

It’s the first time I see the concept of bootstrappability in the context of security.

Is it really worth the effort?

There are multiple ways to run a supply chain attack. With bootstrappability, one can be sure that the compiler is trusted, but what about the code that the compiler compiles? There was this recent attack to XZ utils, which shows that more attention is needed on the code being merged and compiled.

I think that this just creates a false sense of security.

Contrary to that, I had read about a BSD team (I think FreeBSD) that reviews all the code before each release. This way they have achieved ~5 RCE exploits throughout their entire history.

I don’t have any experience with guix, so I will not express any opinions towards that.

However, regarding NixOS:

• Yes, as a person with experience in the Nix language, I can confirm it’s awful
• The documentation of NixOS is a known issue, and there are currently efforts to improve it
• Talking about the trustability of binaries, by doing a quick search, I read that Guix builds are reproducible. This is true for NixOS as well. All upstreamed packages must have their version and the hash of the code (or artifact), to allow verification
• The community of NixOS is opting to maintaining flakes, because:
  • Some applications can simply not be built following the Nix guidelines. Examples are some electron apps (like Falkor) and apps that have weird toolchains (like bubblejail)
  • The reviewing process takes way too long, and PRs for upstreaming are often ignored. This forces a lot of people to just PR a flake.nix to the application, or maintain their own overlays (overlays are like overriding the available packages, while flakes are more like distributing Nix code in general)

I was literally reading your guide about bonfire moments ago.

For those who don’t have a problem with systemd, there is NixOS, which offers the same capabilities as guix, while having a larger community and way more available packages available in its repos.

Care to elaborate?

Wait until you learn about the Linux kernel and the plethora of modules and patches

I quickly went through the article, and I have a question: Why not Docker (or Podman) on NixOS?

NixOS has much larger community (although a bit toxic) and provides native tooling for managing OCI containers through Docker and Podman.

This guy is also a DJ. There is a Traktor console at the left.

In the search results, I think, the first file is Python (.py) and the other is React Typescript (.tsx)

You also need to ln -s /dev/null /dev/nul

In bash, when you redirect the output of a command to /dev/null, like cat /etc/passwd >/dev/null, you are silencing the output.

There are cases that this is useful, for example when checking if an application is installed:

node -v >/dev/null && echo "Node.js is installed"

This line tries to get the version of Node.js, but it silences the output. That’s because we don’t care about the version. We only care about whether the execution was successful, which implies the existence of Node.js in the system.

Point (5) is not about the arcs’ lengths. It’s about the angle they create with the center.

Also, I never said that COD * 2 = 2π. I said (inner COD) + (outer COD) = 2π rads