leisesprecher

In very short, I have a NixOS install with an /etc/fstab using UUIDs. However, my bulk drive died. I have backups, the data is not the problem.

But I can't boot NixOS without the drive. It throws me into an emergency shell, in which I can't edit /etc/fstab (read-only FS) and since I'm in emergeny mode, nixos rebuild doesn't work either (seems to be mostly a network issue).

So, what's the best, non-reinstalling way to fix that?

I'm working on small nix flake to standardize the developer environments at my job.

What I'm still missing, however, is a way to clean up after leaving the shell. Some hook to call a shell script, when the shell is closed.

Is there something like this? I thought about wrapping the actual nix develop call inside a bash script and waiting for nix to terminate, but that seems rather hacky.

I'm trying to get an old Windows game running for a friend.

It seems to be a 16bit macromedia app and I kind of got it running in a Win 98 VM using Virtualbox. DOSBox seems to get confused by it being a Windows app.

Thing is, the friend is very much not good with tech and I want to set everything up for him to "just work". Installing VBox might be a bit too much.

Apparently, you can install Windows inside DOSBox, but is that really stable and usable for layman? Are there any other approaches?

I have a small homelab running a few services, some written by myself for small tasks - so the load is basically just me a few times a day.

Now, I'm a Java developer during the day, so I'm relatively productive with it and used some of these apps as learning opportunities (balls to my own wall overengineering to try out a new framework or something).

Problem is, each app uses something like 200mb of memory while doing next to nothing. That seems excessive. Native images dropped that to ~70mb, but that needs a bunch of resources to build.

So my question is, what is you go-to for such cases?

My current candidates are Python/FastAPI, Rust and Elixir, but I'm open for anything at this point - even if it's just for learning new languages.

I asked a while ago, how to build an automatic light switch and finally got around to actually building it.

My board is an ESP8266 mini D, and ignoring all the sensor parts, my problem right now is powering the actual light.

It's just a small LED array and I connected it directly to the 5V and GND pins (controlled via a transistor).

Measuring from the wall (so including the PSU), this whole setup pulls about 3W (so far expected), however, one small component close to the USB connector gets uncomfortably warm, and I'm not sure, whether that's ok.

The hot component is one of the two small thingies circled in the picture. I thought the 5V get pulled directly from the USB plug, so I'm not sure, why there is any circuitry involved.

I'm trying to build a very simple, stupid light switch for my grow light. Essentially, I want to turn on the light, if it gets too dark outside, so that my plants can survive the northern winter.

Since I'm a software guy, my first thought was an ESP32, but that seems excessive.

My current approach would be something like this: https://www.ebay.com/itm/313561010352 In conjunction with a relay, both powered by a USB-PSU.

If the light level is low enough, the logic DO pin should send a signal and that should be enough to trigger a small relay, so that the relay then closes the circuit to switch on the lights.

Is that idea completely stupid? With electronics, I'm usually missing something very obvious.

The lights themselves are already just usb powered and only draw 5W, so that shouldn't be problem.

What I'm concerned with is the actual switching. Is the logic signal "strong" enough to activate a relay? Would simple transistor maybe sufficient?