IsoKiero

I've ran into that with one shitty vendor (I won't/can't give any details beyond this) lately. They 'support' deb-based distributions, but specially their postinst-scripts don't have any kind of testing/verification on the environment they're running in and it seems to find new and exiting ways to break every now and then. I'm experienced (or old) enough with Linux/Debian that I can go around the loopholes they've left behind, but in our company there's not too many others who have sufficient knowledge on how deb-packages work.

And they even either are dumb or play one when they claim that their packages work as advertised even after I sent them their postinst-scripts from the package, including explanations on why this and that breaks on a system which doesn't have graphical environment installed (among other things).

But that's absolutely fault on the vendor side, not Debian/Linux itself. But it happens.

I don't know about homeassistant, but there's plenty of open source software to interact with odb2 at least for linux. With some tinkering it should be possible to have bluetooth enabled odb2 adapter where you can dump even raw data out and feed it to some other system of your choise, homeassistant included.

If you want live data from the drive itself you of course need to have some kind of recording device with you (raspberry pi comes to mind) but if you're happy just to log whatever is available when parking the car you could set up a computer with bluetooth nearby the parking spot on your yard and pull data from that. It may require that you keep the car powered on for a while after arrival to keep bus active, but some cars give at least some data via odb even when without the key being in ignition lock.

Wait a second. They used AMPRNet to manage these things? In here this kind of things are either hardwired to the internet or they use 3/4/5G uplink and while of course techinally possible either way to breach the system it's a bit more difficult to find out proper IP's and everything.

Once upon a time I had a task to plan a scalable system to display stuff on billboards and even replace printed ads on stores with monitors. The whole thing fell down as we couldn't secure a funding for it, but I made a POC setup where individual displays had a linux host running and managing the display with (if memory serves) plain X.org session with mplayer (or something similar, it was about 20 years ago) running on full screen and a torrent network to deliver new content to them with a web-based frontend to manage what's shown on which site. Back then it would've been stupidly expensive to have the hardware and bandwidth on a single point to service potentially few thousand clients, so distributing the load was the sensible solution. I think that even today it would be a neat solution for the task, but no one has put up the money to actually make it happen.

Why billboard system would have sane installed? I don't think Debian or derivatives install it by default. Vnstat is also a bit odd, but maybe that's just me. I assume they have multiple of these displays around and for them it would make more sense to use something more centralized, like zabbix, to monitor the whole network (obviously they could do that too).

5.2 for me. I got it as a gift, in a offical retail box. I think the box with manuals is still around somewhere, but I'm not sure where.

Most, but not all, do. So it might be as simple as setting a static address, or it may overlap in the future.

You could ask from ISP (or try it out yourself) if you can use some addresses outside of DHCP pool, my ISP router had /24 subnet with .0.1 as gateway but DHCP pool started from .0.101 so there would've been plenty of addresses to use. Mine had a 'end user' account too from wehere I could've changed LAN IP's, SSID and other basic stuff, but I replaced the whole thing with my own.

With plain linux that's a bit complicated to actually dualboot. When booting windows grub just throws the ball to windows bootloader and it manages things from that on, but with grub you'd need to have two separate grub-installations on different partitions so that changes made in Arch doesn't mess up stuff with PopOS (and other way round). It's very much doable, but I suppose (without any experience on a setup like that) that if you just go with default options it'll break something sooner or later and you need to pay attention to grub configs on both sides at all times, so it requires some knowledge. Basically you'd need a grub installed on (as an example) /dev/sda for the system to boot from bios and another grub instance at /dev/sda5 (or whatever you have) for second grub. They'd both have independent /boot directories, grub configs and all the jazz. It's doable, but as both systems can access either one of the confgurations you really need to pay attention on what's happening and where.

Mixing home directory with different distros can create issues, as things have slightly different versions of software and their underlying philosophy, specially when mixing different package managers, is a bit different and they might not be compatible with eachother. Personally I would avoid that, but your mileage may vary wildly on how it actually plays out.

For the partitioning, you can safely delete all the partitions, but you'll of course lose the data on the drive while doing it.

If I'd need such a system I might build a virtual machine to run all the dev stuff and just connect to it from a "real" desktop environment. Essentially mimic a two separate systems where you'll have a "server" for the dev things and a "desktop" to connect with it. Or if you want a clear separation between the two it's possible to run a different window manager for each of the tasks and just logout/login to switch between the two and with some scripting/tweaks you can even start/stop services as required when you switch between "modes". Depending on your needs it might be enough just to run development environment with a virtualbox and start/stop it as needed and adjust the actual desktop experience accordingly.

If I remember correctly, 1000Base-T standard has a requirement that device has to negotiate pinout on the fly. No matter which pin is connected to which. Obvioiusly just randomly wiring a cable up has other problems, like signal-to-noise, but in theory it should work even if you make a cable that's as unstandard as you can make it.

I’d first recommend that you think about what you need.

This is the absolutely correct option. I've set up way too many things without a use case and lost interest shortly after. If you have a real world use case for your project, even if it's just for yourself, you'll have the incentive to keep it going. If you're just setting things up for the sake of it the hobby loses it's appeal pretty quickly. Of course you'll learn a thing or two on the way but without a real world use case the things you set up will either become a burden to keep up with or they're eventually just deleted.

Personally, tinkering with things that are just removed after a while gave me skills which landed me on my current job, but it's affected myself enough that I don't enjoy setting things up just for the sake of it anymore. Of course time plays a part on this, I've been doing this long enough that when I started a basic LAMP server was a pretty neat thing to have around, so take this with a grain of oldtimer salt, but my experience is that setting up things that are actually useful on a long term is way more rewarding than spinning up something which gets deleted in a month and it'll keep the spark going on for much longer.

Seafile. I've used it for years, but I'm moving over to nextcloud as I could use other features it provides. They have paid options too, but unless you need LDAP or something more sophisticated for user management the community edition works just fine.

I personally like mikrotik routers. They have all the features you could wish for and then some and they're relatively cheap for the things they can do. I have RB4011iGS+ (I don't think that exaxt model is available anymore) and it's been rock solid. As I have fiber I just pulled the SPF-module from ISP's box and plugged it in on my own hardware, so the router ISP provided is just gathering dust right now.

But it depends on what you're really after. If you just need basic firewall/NAT/DHCP functionality and your connection speed is below 1Gbit pretty much any router will do. If you have fast connection and/or need for totally separate networks/VLAN/something else it's a whole another matter.

Generic answer for this is to get a refurbished corporate laptop. At least in here we have several companies which buy previously leased computers and give them a refurb (new hard drive, good cleaning, things like that) and sell them for pretty good price.

W, T or X series Thinkpads are pretty safe options, my T495 was 300€(ish) on sale. L and carbon are something I'd avoid, L (at least few years back) weren't built as well as T-series and X1 carbon doesn't have options to expand/swap out ram.