Update at least once a week. Use a mainstream distro like Ubuntu/ Mint/ Fedora no matter what anyone says. You don't need to learn everything thrown at you - learn how to do your stuff, as and when you are stuck - research and find solution. Don't waste your time learning things you will never need or use. The last tip has worked for me for almost two decades (I use Linux as my daily driver since early 2000s, Yet I am not a so called power user - but I can get it to work the way I want or solve issues as and when they arrive). My point is if I will never do bash scripting, why should I waste my time learning it ? This is something most advanced Linux users don't get while giving tips to noobs.
2 years ago
| 11
Backup your data. First install on a spare computer or a virtual machine and keep Windows around because you might need it (and keep your data available in a NTFS disk). Download a bunch of Live CDs copy them to a Ventoy usb drive and run then first in your hardware, if anything doesn't work don't try to fix it a first, jump hop to the next distro until you find the one where everything (or almost) works. Don't start with Arch, but keep the ArchWiki in your bookmarks. Find suitable replacements for your Windows-only software. After you settle on a distro learn how to use the package manager and start learning Bash, because the terminal is your friend. And did I mention BACKUP YOUR DATA.
2 years ago (edited)
| 6
Setting up timeshift (I would include snapper, but I don't think there's a begginer friendly implementation yet), I don't even wanna estimate the time I lost reinstalling from scratch after breaking my system beyond my ability to repair it. backup for personal data is a close second, even if just as a reminder, anyone on any operating system should have a backup
2 years ago
| 4
If you have a folder and want to temporarily view those files from another machine, you can open that folder in a terminal and run a simple temporary web server using a single command: python3 -m http.server 8080 & From the other device point a web browser at your computer's name or IP, appending port :8080 and you will get a directory listing. The server runs in the background but requests will be logged in real time on the terminal. You can continue to use the terminal though. This is another way to download files from your computer without installing anything, if python3 comes pre-installed. While it is not meant for continuous use you can use it to let a visitor have read-only access to a folder without authentication, and it can perfom fast enough for media playback depending on your network speeds. To quit the above server, press <Enter> (or <Return> until you get a prompt. jobs fg 1 CTRL+C jobs will list background processes and fg <n> will bring that process to the foreground so the CTRL+C can close it.
2 years ago (edited) | 1
Use the terminal at least for your regular system updates. This is very simple and you will lose your initial fears of the terminal. You don't need it all the time, but if there is some problem, and there will be, you should be able to find a solution online, that will probably include some sensible copy and pasting of some terminal commands. But you don't need to be a "hacking pro" to be comfortable with occasionally using the terminal.
2 years ago
| 4
Refresh mirrors on Pacman, Install Microsoft fonts, Configure/go through keyboard Shortcuts properly, Don't hesitate on running few commands if Solution is Verified 😁 (~ from a Fairly new Arch-Xfce user
2 years ago (edited)
| 3
Use a different administrative user account solely for the initial installation and for creating /deleting other users. Don't use that for everyday computing. Don't change other settings or install browser extensions. Maybe change the wallpaper to a different solid colour as a reminder though. That way if you mess up some user settings or need to reset user passwords you have that in reserve. Later on if something works for the installation user but not the regular user you know it is not a system-wide problem. I do the same on Windows anyway.
2 years ago
| 2
Avoid modifying /boot Practice a snapshot and restore process. Back up. Back up. Back up.
2 years ago
| 2
If you only have one internal drive, optionally create your partitions in a live environment before running the installer. Set aside enough space for 2 root OS partitions plus /home (plus EFI_System). In my case I would typically allow 20GB each for os_1 and os_2. Allow more space if you know you have bigger applications to install / re-install. When upgrading between LTS by doing a clean install I alternate between os_1 and os_2 so that I can always boot into the previous version if need be. If you don't do this, backup your /etc folder before upgrading to the next release or reinstalling. You can use an archive format like ZIP for this but you will need to create it as root/sudo. This way you can consult system settings from a previous installation.
2 years ago
| 0
If you cannot figure out how to quit any program it will also be listed in your graphical process monitor / task list thingy. If you want a semi-graphical interactive process monitor in your terminal install htop (similar tools exist). This has advantages if ever needing to check on processes remotely (via SSH for example) as well as locally.
2 years ago
| 0
Install openssh-server If you have Android devices on your home network, install FX File Explorer on those. https://play.google.com/store/apps/details?id=nextapp.fx FX can browse remote computer folders using SSH (SFTP) and can do 2 pane browsing for easy copy/paste to transfer files or folders. It also has a built-in WebDav server which you can activate as needed to share your Android's internal storage and SD card. Most file browsers on Linux can open also browse / mount folders using SSH (SFTP) or WebDav natively so this gives you file sharing in either direction without installing someone more complicated like Samba. Warpinator and similar are fine if you are just trying to needing to do one-off transfers but the above methods can support in-place editing or playback too without needing to keep multiple copies in sync.
2 years ago | 1
Use the package manager if possible, not some random installer from the internet
2 years ago | 1
Linux is not Windows. Expecting it to be a 1:1 clone sets you up for failure when something doesn't work the way you're thinking it will based on thinking it'll be identical to Windows. Take the time to learn it and not quit in the first 5 minutes or mistake.
2 years ago | 1
InfinitelyGalactic
What are some are some 'best practices' that you recommend to all new Linux desktop users? Just some casual research...
2 years ago | [YT] | 44