The question implies that the OP wants to create one giant filesystem with all of their data on it. This has its own issues, especially if it is in /home. For one, as someone else pointed out, it’s fairly difficult to run your system without /home mounted, and that makes it difficult to resize. Sure, you can set up an admin account with it’s home in the /root filesystem and then log into that - but that seems to be a lot of work in itself.

If it was me, I’d set up mount points for file systems that make sense. Maybe /data/Photos, or /data/Music, or data/AppData, or whatever. As much as possible, I’d just point whatever software I was using to those new directories to find the data. If that isn’t feasible, for whatever reason, then a symbolic link from /home/Photos to /data/Photos will work seamlessly in most cases.

As far as I’m concerned, after administering enterprise systems using Unix going as far back as the early 90’s, symbolic links are a key tool in managing disk space that you shouldn’t just dismiss because it’s “an unnecessary layer of complexity”. Having smaller, purpose designed, file systems allows you to manage them better. Sticking everything into /home is probably not the right answer for anyone.

Resizing partitons is often not necessary. Use a symbolic link to relocate a subdirectory to another file system. For 99% of use cases this is indistinguishable from expanding the partition.

I guess they figure that Linux users already know what they are doing when it comes to security.

That’s a little confused. From what I remember, it’s the server that matters, not the domain when being blocked. If you self-host this is a problem, but not if you use your own domain on a commercial service.

The “MX records and such” are all a function of domain management. You’ll have to do this whether or not you self-host.

I used KDE Connect on Ubuntu with Gnome. No issues.

Old school Unix guy here…vi,awk and sed are all that you need.

Thank God somebody got it.

“Intercourse!”

My first experience with this food was in Halifax decades ago. The Halifax Donair is a unique thing.

And it’s definitely Donair, not Doner.

Technically, he would have three drives and only two drives of data. So he could move 1/3 of the data off each of the two drives onto the third and then start off with RAID 5 across the remaining 1/3 of each drive.

Deal with the ethernet port issue by purchasing a 5 port ethernet switch. Maybe the rest of your issues go away?

For me Bazzera Magica and Baratza Vario grinder some time back. Better coffee than most cafes.

I looked and Python has the library support for the GPIO and to do background threading to poll pins. My preference would be to go with a JVM language like Kotlin, but then I’m a programmer. Python, from the little that I’ve mucked about with it is really just one step in complexity from scripting. Maybe even easier, because some things in shell scripts are super difficult to do.

Maybe then you need to move one stop up from scripting into something closer to actually programming. I’d be surprised if Python doesn’t have the library support on a Pi for dealing with both serial and GPIO I/O.

the end stop in external to the serial communication

Does this mean that you have some kind of other signals or pin-outs? If so, this is starting to sound like a great project for a Raspberry Pi, because the GPIO pin array can handle that.

Keep in mind that it has been decades since I last used Kermit, but I’m pretty sure the use case it was originally designed for was…

Connect to a serial port, which had a modem attached. Talk to the modem and get it to dial a number. Presumably, the remote end answered and the port attached to its modem would issue a login prompt. Negotiate the login and then issue a bunch of commands to change directories and then launch Kermit on the remote system. After that Kermit to Kermit communications took over until you terminated the session. Finally, log off the remote system and hang up the modem.

All of this stuff could be done via scripts. I seem to remember that it would actually wait for a response, and then parse the response in the script. I don’t remember ever doing polling loops.

If you’re on a *nix box of some type, it’s totally possible to open up a serial port for manual I/O even in something like a bash script. Even if you have to reverse telnet to a terminal server.

Kermit on top of FTP can work really well. Kermit has its own communication and transfer protocol, IIRC, but updates in the 1990’s allowed it to be used with TCP/IP and FTP. So you can write a script to log into a remote system, run some commands and then initiate a file transfer. The scripting allows you to wait for responses and act on them.

I never expected to see a compiler in this list, at least not in 2023.

Back in 1988 I realized how rubbish Microsoft was when I discovered Borland’s Turbo Pascal and Turbo C compilers. I’d previously used the MS compilers and they were multipass, multi-minutes to finish a compile. The Borland ones were single pass and FAST.

Back then, compile times could be huge, and everyone was publishing benchmarks on compiled program performance, which mattered on the hardware of the day. I never even think about that stuff these days.