It doesn’t really matter for the average use though, most probably won’t really notice the app opening times and most Windows users will not care about the backend being closed source, coming from an entirely closed source OS. I will tend to recommend stock Ubuntu or Mint/PopOS at most because those actually bring some things to the table while being Ubuntu based, not being Ubuntu but with a different DE
I’ve been quite enjoying Mint as well. Granted, it’s been reeeal light use. But so far loving it. I’ve always enjoyed Debian distros. RHEL can kiss my butt. It was always frustrating to work with at work. I think Slackware was Debian? That was probably my first back in like 2004ish. Generally just works™
They all work in marketing. Except for the three guys who made Fortnite and Frank, who maintains the launcher. Don’t go into Frank’s office unannounced, he often forgets to wear pants.
The 23rd is the day before Christmas. We celebrate the eve here in the Nordics. The 25th is the relaxing day after Christmas when you eat leftovers and do fuck all all day.
Actually one day before Christmas in Finland and other Nordic countries. I don’t know if Linus still celebrates Christmas like that, having resided in the US for a long time already, but the big celebration is here always the 24th of December, and 25th–26th is mostly just resting after it.
You know how I know I've gotten better at using linux?
I saw the command and read it and figured out what it was although I've never been exposed to a fork bomb before in my life.
I was like okay, this is an empty function that calls itself and then pipes itself back into itself? What the hell is going on?
I will say that whoever invented this is definitely getting fucked by roko's basilisk, though. The minute they thought of this it was too late for them.
99.999% of that function’s effectiveness is that unix shell, being the ancient dinosaur it is, not just allows : as a function name but also uses the exact same declaration syntax for symbol and alphanumeric functions:
you can create them afterwards and move the stuff into the subvol. do it from a live usb and don’t forget to update fstab. be sure to use rsync with the flag to keep permissions etc
That’s simple, but it’s a completely unnecessary waste of I/O. You could create a writable snapshot of the btrfs root as a subvolume, edit the fstab and any other relevant files within that new subvolume, reconfigure the bootloader to specify that subvolume as the root filesystem (as a Linux kernel command line argument) instead of the btrfs root, and then reboot. After rebooting, the original btrfs root can be mounted, and everything unwanted from the original root (other than the new subvolume and its ancestor directories, obviously) can be deleted. Do not delete anything that you didn’t want to lose the changes to on the original root subvolume that you did after creating the snapshot, as the snapshot only remembers what you did before, as well as the changes made specific only to it (like the fstab).
If one wanted to create multiple subvolumes for different purposes, the above procedure can be modified. For instance, if one wanted a separate subvolume mounted at / vs /home, then one can create two writable snapshots, empty out the contents of home in new subvolume 1 (but not the /home directory itself because you want the directory to exist for something to mount onto it), empty out everything outside of home within new subvolume 2, move the contents of home therein up one directory and remove the /home directory itself. Now, one can edit the fstab in new subvolume 1 as appropriate (not forgetting to have new subvolume 2 mount at /home), edit any other relevant files, reconfigure the bootloader to tell the Linux to use new subvolume 1 as the root subvolume, then reboot. Finally, one can remove the unnecessary files from the original root.
Edit:
It is arguably better to manually specify the new root when booting in the Linux kernel command line, and not reconfigure the bootloader until you successfully boot. After success, (if the following is relevant to your system) use update-grub, and it should look at fstab to automatically reconfigure the bootloader accordingly to use the appropriate new subvolume as specified at fstab.
This is what I did years ago to one of my own systems, although I don’t know anything about Timeshift and how it requires things to be set up (I have my own backup scripts that are run by cron). I could have just snapshotted the btrfs root directly for snapshots, but I wanted the snapshots to be cleanly separated from the subvolume used as the Linux VFS root (except when I explicitly mount them).
You laugh but windows defender is awesome. People give windows shit but the reason it’s attacked the most is because of it’s market share being above and beyond leaps and bounds sun vs tiny fleck of dust in space os market shares that Linux and Mac os have. No one’s wasting time hacking the tiny stuff as much just because its a numbers game. Guarenfuckingtee you if Linux was number one market share OS it would be getting attacked way more often than any other OS as well. Dont kid yourselves.
macOS and Linux have additional security features at a system level, on Linux most software comes through controlled repositories or sandboxed flatpaks. There are also tons of multi million dollar companies that constantly try to find and fix kernel level vulnerabilities and a distro like Debian, which is very popular for servers, has had less major vulnerabilities than windows 7 throughout its entire lifecycle and Debian exists for other 30 years. So I’d say Linux is would have a few less (different) attacks
I vividly remember when a friend of mine who runs a small graphic design studio was sent an archive file macOS couldn't open natively and asked me for help. Never having used a Mac and without any clue as to which tools the stupid app shop (which was rather new at the time) held, I couldn't for the life.of me get the blasted thing to obey me, until I found a terminal. I then installed build utils and compiled the frickin' unpacker I needed myself since it only had Linux binaries. Worked like a charm.
I think it’s gotten better, but I still have a bad taste in my mouth from the countless times MacOS was too stupid to recognize a file type, and absolutely rejected all attempts to tell it what it was. I almost always found a way around it, but it would sometimes take dozens of minutes of fighting with the OS; these times almost made me long for Windows.
Apple’s position that users are fucking idiots may be usually justified, but they consistently violate the “… and make the uncommon possible” rule. The philosophy that the OS is always right is frustrating.
I can agree that fighting apples UI’s can get frustrating (i.e. playing the “try to find the right button” game). What makes me think macs are great is that you get all the freedom you could wish for in a terminal that is unix-compliant, while also getting the reliability of a hugely widespread OS that a bunch of good developers are paid to maintain. With the new macs you also get the apple silicon hardware, which is great.
I think most people that use macs indeed do need the safety rails, but at the same time they bother me. I know how to disable them within 15 mins of setting up my computer, but if I’m helping someone with an issue, I sometimes first need to spend some time disabling safety nets and installing the tools I need. Also: Shoving iCloud storage down my throat is shit. They should stop that.
linuxmemes
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.