Bus 004 Device 002: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
And I don’t know if a live CD is the best method for this, due to the how I intend this to be something I can just keep files on for a while. While I do have small persistence .dat files for Debian, Fedora, and Ubuntu, it seems like a bandaid for what would be easiest, an installed distro where I can run the package update commands for, without juggling iso files.
That’s a good chip. As a rule of thumb, Realtek = best, Asmedia = good, JMicron = garbage. JMicron adapters run super hot and draw a lot of power, leading to low speeds and dropped connections.
The reason I suggested a Live CD with persistence is that they are better at autodetecting stuff on the host machine. You can definitely install an actual system on the SSD but it will make assumptions about things like the GPU for example – won’t expect to have to swap it at boot, you’ll have to do it manually. Or you can run your desktop environment with a pure software driver but that may get a bit annoying at times, depending on what you want to do with it.
I used to use Amarok, but now I have a subscription to Youtube Music. It gives me a lot of flexibility on running it in a browser or on Android without worrying about syncing.
You can use syncthing. Set it up and forget about it, you’ll have the same dotfiles anywhere. I have it on my phone so that changes are always synced to it if all other computers are offline.
Plexamp all the way, easily the sexiest music player I’ve found so far. All my music is FLAC pulled from Deezer, and since I’ve got a very large list of artists tracked, it’s super easy to discover new music with the radio and sonic analysis features. It’s also got a last.fm integration, which gives me more data than Spotify would about my listening habits.
The only feature I’m really missing in it is collaborative playlists. I can share playlists out to anyone on my Plex server, but they can’t add or remove songs.
As long as you’re not going to store sensitive data in there, I’ve just been using GitHub. I’ve got a Private Repository setup with my configs (.bashrc as well as WM configs and other dot files) and I just commit/push it up and heave an update script pull it down elsewhere. Then it’s also version controlled.
I think I maybe phrased it horribly, my question was more like, what do I need to learn in order to modify myself the .bashrc by myself instead of using a programme. Does it make sense?
You need to learn bash scripting. Also, there are a few default files that the .bashrc uses which can be helpful to compartmentalize the custom things you do to it so that it's easier to undo if you screw something up. To do that, just add this to the bottom of your .bashrc
if [ -f ~/.bash_custom ]; then
. ~/.bash_custom
fi
What that will do is check if the .bash_custom file exists and then run the .bash_custom file in your home directory and apply anything in there. Also, you can call the file whatever you like, but bash does have some defaults that it will check for and run them without editing the .bashrc at all. It's kind of hard to find a list of the the files that it automatically checks for, but I know that .bash_aliases is one of them, and I think it checks .bash_commands as well, but I'm not entirely sure. Either way, you can force it to check your custom one by using the code above.
Then you can create the file and add any custom things in there that you like. For example, I like to frequently update through the terminal but running sudo apt update && sudo apt upgrade && sudo apt autoremove && flatpak upgrade was a bit tedious and I wanted a bit less feedback so I made a custom alias for my personal use.
Which hides most of the text from updating and just gives me feedback on what it's currently doing if I don't really care to know all of the details. So now I just run update in the terminal and plug in my password and it updates and upgrades everything in a human readable way.
There's a lot that can be done with bash scripting, like editing files, iterating over files and directories, setting environment variables. It's basically a full programming language so the limits are mostly your imagination.
Use chatgpt. Take the first line of your bashrc file and ask it to explain it. Than the second line etc. Won’t be always perfect but for bashrc it shouldn’t be a problem and you can learn a lot from it.
Yes. Running anything as root is potentially dangerous. And a browser is a complex and big piece of software with many security issues that can be (potentially) triggered remotely. So it’s bad because of two reasons.
Btw a desktop environment also is a complex and big piece of software with potential issues. Running the whole desktop as root is another thing you wouldn’t do for extra security.
The proper way is to just create a user account and run the desktop and browser as a user. Open a terminal and ‘su’ or ‘sudo’ to limit root rights to the operations that actually need those permissions.
Just running everything as root certainly works. But you do away with all the extra layers of security and end up with something as secure as MS-DOS or a Windows in the 90s or early 2000s.
I recommend unplugging all disks with important data beforehand. Piece of mind about not being able to wipe all data (and having to restore from your backup) is great. Having used fdisk or parted is a good experience to have in case it’s actually needed on some server.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.