You make it sound as if it’s a religion … UNIX isn’t a dogma handed down by an infallible being, just a piece of software that made sense for its time. Todays needs are different than the needs 40 years ago, so ofc things have to change.
Actually most of the money are just 1‘s and 0‘s in a computer, coming into existence from nothing and vanishing into nothing. Fiat money backed by “trust”. As Henry Ford once said:
It is well enough that people of the nation do not understand our banking and monetary system, for if they did, I believe there would be a revolution before tomorrow morning.
No, that’s a very bad idea. BTRFS has deduplication, without that the snapshots would take up way to much space. Also it’s too many writes since ext4 doesn’t use cow and would have to do distinct writes for every snapshot.
The 240 gb are plenty for a root system without /home and years worth of snapshots on a btrfs volume, only the changes take up space so the amount of snapshots hardly matters.
For /home either ext4, xfs or btrfs is fine. Personally I only use a single btrfs volume and put certain folders in their own subvolumes so they can have different settings for snapshots(no snapshots for /home, tmp and cache folders).
That 40 year old X protocol might be the issue here, use wayland for multi monitor with different resolutions.
Well the fact that you don’t understand the issue is part of it. See there are several ways disks can be partitioned and several ways a bios can go about finding kernels to boot on said disks, all of this applies to windows as well btw.
What you have is probably a mix of the two. It’s likely that one of your linux installs partitioned your disk as GPT while your your system still boots in bios legacy. The installer is now getting mixed signals, one one hand the bios is detected as legacy mode, on the other it’s looking at a GPT partition table. Now technically you probably could write the bootloader just like in option 1., but if you ever change your bios to uefi mode, which is required for modern operating systems like windows you would end up with an non bootable system. And not just in a “oopsie, I need to boot a rescue disk and fix this”-kind of way but a “we need to nuke the entire partition table and start over”-kind of way.
So what the Suse installer is telling you is that you really should use a /boot partition if installing on a GPT partition table.
Btw if you check the correct option at install time(the one about using the entire harddrive) it should automatically create a MBR partitioned disk for you which avoids this issue as it’s not a ungodly mix of 1. and 2.
This error isn’t a bug, it’s a feature pointing out a serious problem with your machines setup(the one below the OS level). Yes you can probably ignore it, as other distros might or might not, but it’s generally not a good idea. SuSE has a couple of these hang ups since it has an enterprise background and takes some things more serious than other distros. For example having closed ports for printers in the active on default firewall being one stellar example of this. It cause no end of issues for people struggling to setup their printers, that being said it is a security issue and opensuse decided it wasn’t going to sacrifice security of every system because some people want to use a printer.
You booted in bios legacy mode and tried to install to a gpt formatted disk without a dedicated /boot partition would be my guess.
It’s messed up, probably a bios setting related to uefi. Aeon is still in beta and doesn’t handle edge cases that well.
As for your second issue sounds like a waylaid issue with switching resolutions, usually simply relogging fixes that.
You make it sound as if these are distribution issues, these are either weird bios settings or post install issues with a very recent compositor version. Do you think opensuse ships its own drivers or window managers?
So it’s people borking it and not the “system itself”. You have control over which people are involved in the software on your system ne it affects the likelihood of it ending up borked.
Nope, it doesn’t. It always requires human assistance or random hardware failure. It’s either the user, the distro, package maintainer or upstream fucking up.
Personally I blame half on users for picking the wrong distro(not suited for beginners) and half on the linux community giving poor advice(use the terminal). Not everyone has the time or inclination to become a power user and if people wouldn’t be so thickheaded and recommending the same problematic distros over and over to these people it wouldn’t be such a mess.
I have a 80 year old neighbour whose old windows laptop was a mess and who was open to trying a new OS(because he couldn’t operate windows either anyway). I setup a MicroOS system for him, put a taskbar extension on it and showed him how to install software from gnome-software(which only has flatpaks). ZERO problems in half a year. He doesn’t have to do anything nor learn anything. He happily installed some card games, reads the few websites he follows and that’s it.
Try opensuse tumbleweed. It is a bit like arch(rolling release and such) but has more testing and less breakage. It has pretty good KDE support, a very good configuration tool and is one of the most secure distros in its base installation. Also good for gaming imho.
They are very very different, much more so than say arch and mint are different. Listing what makes nix better than mint would be just a list of features mint is missing, wether these are relevant for you or not would decide if they make nix better. However there are some objective technical points that are just flat out better:
One config file describing your system. You change that file, you change the system. The system always is in the state described in that file.
Complex system changes that would require many steps are trivial since you only have to describe the outcome in your configuration file instead of how to get there. For example I can declare in the config file that I want a system using the current stable linux kernel with zen patches and Nvidia drivers that have 32 bit support.
Every update is a (seamless) reinstall. The entire system gets rebuilt as if it was a fresh install, sans your home directory and the settings you made ofc.
Concept of generations. Every time I change my config file or rebuilt my system(update) it is a new generation with its own entry in the bootloader. Btw, the config file also controls which bootloader your system uses, you can just say grub or systemd and nix takes care of the rest.
‘nix-shell -p program’ that little command will open a shell with the specified applications installed in it, after you close that shell the programs are gone. This is great for trying out apps without cluttering your system with their dependencies, or quickly using a app you know you won’t need permanently.
Choice between release based updates or bleeding edge rolling. Concept of generations does still apply, you can quickly try out the rolling release channel and if it doesn’t work out you can easily go back.
Trivial to change midstack applications. With midstack I mean things like cinnamon, gnome-shell or plasma base files. For example what if you wanted to switch from gnome to kde? A single word changed in the nix config file will rip out all of the gnome stack and put the plasma stack in instead. As if you never had gnome on your system, a reinstall for all intents and purposes. Again, trivial to change back.
That’s just some of the advantages of nix.
This was refuted long ago. Systemd isn’t a single binary file doing everything, it’s a project that has many different binaries doing many different things. The only difference is that they are developed under one project to ensure they integrate well with each other. What your doing is like complaining that glibc tries to do everything, I mean it does open, read, write, malloc, printf, getaddrinfo, dlopen, pthread_create, crypt, login, exit and more… Xorg would be another example of a project that does many things instead of one very well.