

This but put the entries in /etc/fstab instead.
Hello! I am originally @[email protected] but moved to lemmy.blahaj due to the June 2025 shutdown of lemm.ee (o7)


This but put the entries in /etc/fstab instead.


Oh i haATE using the touchscreen during the winter. Absolute bollucks.


Car has one and it only controls dash lights but good call anyways :)


This looks pretty interesting. I have been passively looking for such a service. I will give this a whirl and try it out.


Agreed. Touchscreens are such a safety hazard. The idea of having a bloody oversized iPad controlling everything in your car is an absolutely shittastic design.
My current car has a stupid 7 inch touchscreen and its bright af even at the lowest bright/contrast settings. Yes it has dark mode. Yes it’s enabled at nighttime - which is when I do most of my driving - and YES it’s still wayy too fuckin bright. So i have it display off perma, no need for that shit to distract me whiel im driving.
Fortunately the touchscreen only controls radio, media, and settings. HVAC and other mission-critical shits are relegated to tactile buttons and knobs. Additionally, the steering wheel has media controls and other buttons, which basically make the touchscreen useless as the wheel does the same crap as the screen, except it doesnt blind me at night.
Unfortunately, it’s getting increasingly more difficult to find a car that doesn’t have this junk built-in, unless you get a used car from the mid-to-late 2000s or even the 2010s. (And then you have more shit to worry about, but at least its all mechanical vs computer in nature!)


Keeping it classy (obvs this is satire…)


Why not both?


Based off what you wrote - and the fact that I’m massively sleep-deprived - it all makes sense. The issue you describe and the fix applied are akin to what we see in the database world, where users complain about queries being slow or unresponsive after trying to force-kill. Only for us to find out, that they submitted queries with a COMMIT after the whole 10mil record transaction, which clearly the DB can handle, but it will take a significant amount of time to rollback vs if the COMMITs are broken up and submitted more frequent. Basically chunking up the data into more manageable pieces as to not saturate the db threads, not to mention the underlying REDO and transaction log files too. So hope this was truly a long-term fix vs just a short-term one. Either way, great write up.( Also, you may want to invest in some 2.5gb networking for later, not that 1GbE isn’t enough, but just more pipeline is great, although I don’t know how much upgradeability your Synology will have in that department, so YMMV)
I wanted to provide feedback for THIS part only. :) not for OPs issue. I would have responded to OPs post if that were the case…