Just disable score in your profile settings, man. That’s what I did. Score has no point, really. If someone disagrees with you, they can either ignore you or expose their reasoning. Votes are useless.
My local backups are handled by rdiff-backup to a mirror set of disks. That means my data is versioned but easily accessible for immediate restore, and now on three disks (my SSD, and two rotating rust drives). It also makes restores as simple as copying a file if I want the latest version, or an easy command if I want an older version. And testing backups is as easy as a diff command to compare the backup version with the live version.
Having your files just be files in your backup solution is very handy. At work I don’t mind having to use an application like Veeam, because I’m being paid to do that. At home I want to see my backups quickly and easily, because I’d rather be working on my files than wrestling with backup software…
Remote backups are handled by SpiderOak, who have been fine for me for almost a decade. I also use them to synchronise my desktop and laptop computer. On my desktop SpiderOak also backs up some files in an archive area on the rotating rust mirror set - stuff that’s large and I don’t access often, so don’t need to put on my laptop but do want backed up.
I also have a USB thumbdrive that’s encrypted and used when I’m travelling to back up changes on my laptop via a simple rsync copy - just in case I have limited internet access and SpiderOak can’t do its thing…
I did also have a NAS in the mix once, but I realised that it was a waste of energy - both mine and electricity. In normal circumstances my data is on 5 locations (desktop SSD, laptop SSD, desktop mirror set, SpiderOak’s storage) and in the very worst case it’s in two locations (laptop SSD, USB thumbdrive). Rdiff-backup to the NAS was simply overkill once I’d added the local mirror set into my desktop, so I retired it.
I’d added the local mirror set because I was working with large files - data sets and VM images - and backups over the network to the NAS were taking an age. A local set of cheap disks in my desktop tower was faster and yet still fairly cheap.
Here’s my advice for your consideration:
Simple is better than complicated.
How you restore is more important than how you backup; perform test restores regularly.
Performance matters; backups that take ages are backups you won’t run.
Look to meet the 3-2-1 criteria; 3 copies, on 2 different storage systems, with at least 1 in a different geographic location. Cloud storage helps with this.
⬆️ for rdiff-backup since it keeps the last backup easily readable.
I had before (and I think I’ll implement it again) snapshot capable filesystem where to I rsynced my stuff. Then once a day did a snapshot of the backups. It has the advantage of all the backups being easily readable as long as your backup filesystem is intact and your kernel can mount it.
I think opinionated is different from being for a non-power-user.
Click ‘brave’ is not opinionated, because I could click chromium instead. “There is a web browser (and it is Firefox)” is more opinionated, and easier at first, then harder if you happen to need a chromium-based browser.
Prefer using Wayland over Xorg. Xorg’s design predates modern security practices and is considered insecure by many. For example, Xorg applications may record keystrokes while inactive.
If you must run Xorg, it is recommended to avoid running it as root. Within Wayland, the Xwayland compatibility layer will automatically use rootless Xorg.
I mean… “who needs features in 2022” is onto something. But I use both, for various Nvidia and laziness related reasons, and have a dim idea what they do inside, as probably most flamers on the topic.
From what I can tell it’s a compositing window manager for wayland (the potential successor to X11, in case you didn’t know). It does make things very neat and pretty though.
To add to this: Wayland is a bit different than X11. In X11 you had split responsibilities: Compositing, X Server and Window Manager. Wayland only refers to the protocol and compositors implement that protocol. The compositor has a lot more responsibilities in wayland since it needs to do everything itself which in X11 was split across different applications.
Desktop environment is like traditional windows desktop, everything included. It has stuff like notification daemons, advanced settings, toolbars, task manager and so on.
Window manager let’s you manage windows but often doesn’t have it’s own toolbar, notification demon, task manager and other things. People who run window managers are picking their own toolbar software, their own notification daemon and so on. They want a much more customizable personal experience, often heavily themed as well. Usually a window manager is also faster than a desktop environment since it does less things.
Compositor is what gives drop shadows, transparency and other visual effects. Its often built into desktop environments but is often missing from window managers, but not always. When it’s missing, people install one of their own. There are a few popular choices.
Examples of desktop environments: Gnome, KDE Example of window managers: Sway, Hyprland, i3, xfce, awesome wm
I’ve recently started using proxmox -backup-client. Works well. Goes to my backup server along with my vm image backups. Works nicely with full deducing and such. Quite good savings if you are backing up multiple machines.
1993 or so with some Slackware CDs, i bought, because I had no internet back then. Took ages to compile, and never got past the black x on the checkered background when I tried to startx. Console worked nicely though and I loved the bash (?) experience with command history and all that. However, no games, very little software, and I didn’t program back than. It took quite some time to be able to use those things productively as a user.
I used to be on Majaro for awhile, years ago but I wouldn’t recommend it now. It doesn’t have any of the advantage of an Arch based distro. Their own repo has issue. I would recommend Endeavour OS
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.