In the world of electronics, especially PCs, it is fashionable to call an outdated piece of equipment a "potato". My PC absolutely qualifies, but what makes it interesting is that you can trace its descent from a potato several generations older. This is a neat testament to what's possible to do cheaply with AMD stuff since they keep announcing new processors on old sockets. Here's what it's in and what's in it now:
I have recently got a 2008 Versa Note S, also known as a C11 or Tiida, and I've been driving it to work. It has been disintegrating a bit (the front suspension is very sloppy now) but okay, I'll deal with that, it's a 15 year old car. But what I couldn't deal with was the stereo, which was an in-dash 3 CD changer with no aux input.
I just rearranged some of my storage and wanted to automate this, and I was pleased enough that it worked exactly how I thought it should work that I thought I'd just share. This goes in /etc/profile.d on most Linux systems today.
I use a 1GB tmpfs on my Linux system, which causes problems with some installs which write their temporary files to /tmp. Here's a way to somewhat gracefully set TMPDIR for every user logging in:
Wow, some people try to make this crazy hard. Here it is from the CLI. Or as a .reg file:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"AutoAdminLogon"=dword:00000001
"DefaultUserName"="user"
"DefaultPassword"="password"
This seems to be available from at least Windows 8.1 on.
I have just recently installed Samba as an Active Directory Domain Controller on my Linux system, and I'm still trying to sort out the details. I have never really gotten into Kerberos, and this is a good learning opportunity. One of the things you have to do to enable the use of Kerberos tickets for authentication for services is to add the Service Principal Names, sometimes called "service principals", to the computer's Kerberos account.
I've been playing around with creating a kind of all-in-one, "loaded for bear" Drupal 10 configuration, with a coherent set of compatible and cooperative modules. My goal is to make deployment and expansion simple regardless of your goals.
I like to play games well into their sunset years, which is great because it saves me a lot of money on GPUs. I had Fallout 4 back when it was relatively new, but having tired of my other options, I decided to see how it ran on modern Linux. As it turns out, the answer is that it runs about as well as it does on Windows, maybe even slightly better in the graphics performance department. I started out with a steam deck howto and worked the rest out from there. These instructions assume you have all of the DLC.
I recently started playing Fallout 4 again, because I own it already and it runs well on my potato, even under Linux. The last time I played I had dual nvidia GTX 950 cards in SLI under Windows 7, and now I have a single 1070 under Linux. The performance is as much better as you would hope. The game is just about as reliable on Linux as it is on Windows, which is not very. However, my current configuration lets the game start up pretty quickly, and liberal use of the quicksave feature keeps me from losing too much progress in the inevitable explosions.
composer config repositories.asset-packagist composer https://asset-packagist.org
composer config --json --merge extra.installer-types '["bower-asset", "npm-asset"]'
composer config --json --merge 'extra.installer-paths.web/libraries/{$name}' '["type:bower-asset", "type:npm-asset"]'
(From https://www.drupal.org/project/drupal/issues/3198245#comment-13997741)