About twenty seconds from ‘power button’ to ‘desktop’ on my laptop, about two minutes on my desktop, mainly because it’s got about 9 disks in it in various RAID patterns, and a discrete graphics card and fancy USB audio and all that shit needs initialised. Doesn’t matter much, they both sleep / hibernate and rarely need restarted
We’re talking seconds, but on top of ‘twenty seconds’ then it’s a large fraction of the total. The real problem is mounting disks in RAID for me, though - takes quite a while.
I use both on gentoo for some obscure or proprietary stuff that is not packaged in portage, like filebot, authy desktop, discord, steam and foobar2000 (including wine in 1 bundle to avoid dependencies and switching all portage packages to 32bit abi). It works well and opens me up to loads of stuff. It's freedom in some way.
Snap or flatpak makes no difference to me, they're just different backends for kde discover
A lot of big companies use RHEL because they are afraid of FOSS and assume that paying for something is better than getting the same thing for free. I’ve spoken with people in my org who have a RHEL contract, and it always sounds like the RH people never tell them anything that anyone who knows Linux couldn’t have told you.
Nope. None of this affects Fedora. Fedora is upstream from RHEL, meaning code from Fedora is contributed towards Redhat Enterprise Linux, and not the other way around
Changing the label should also work during operation.
For example, it should be sufficient to run sudo btrfs filesystem label / newlabel to change the label of the root partition (/) to newlabel.
If I’m not mistaken (can’t test it right now), you have to specify the mountpoint when the partition is mounted. And in unmounted state the device (e.g. /dev/sda).
So, you move to community-run distros, and you start getting used to Debian, or Nix, or whatever else for your own stuff, you want to use that at work as well, and if you’re in a position to push that, you’ll do so.
Except in the long run this also hurts Linux. Because if Red Hat starts making less money, they’ll hire less people, and contribute less to the linux kernel, GNOME, systemd, and other various systems
There are companies that provide commercial support for debian (and probably nix), if iirc.
The problem of systemd is that it hasn’t been just a replacement of init as they initially claimed, and now deny they ever did. Things like Mono, Gnome and systemd are bad for the ecosystem long term.
An init done by constructive people wouldn’t be a problem at all.
The problem of systemd is that it hasn’t been just a replacement of init as they initially claimed
Apart from the PID 1 part of systemd, almost all tools are optional.
Although I have a positive opinion about the systemd project, I used netctl instead of systemd-networkd for a long time without any problems. And even today I don’t use systemd-resolved because I use a combination of unbound and Pi-Hole in my private LAN. And so on.
So you can’t say that the systemd project has replaced various solutions in such a way that you don’t have a choice anymore.
Honestly, that looks like a fairly short list and half of the tools interact closely with useful functionality that didn’t even exist at all before systemd came around.
@gronjo45 The big question here is; what do you mean by "learn linux"?
If you really want to learn and understand what you're doing, here's a solution that will not leave you empty handed. No matter if you decide to call it quits half way through, you still have a great deal more knowledge than you'd get from simply installing a distro that does all the hard work for you.
No one ever listens when I say it but I'll say it again; follow the #gentoohandbook cover to cover doing a stage3 install. When you encounter something you don't understand, go read about it, usually links are included. Once you've gotten to any graphical environment, wipe it and start again. Repeat this process until you only reference the handbook to verify you're doing it correctly.
I would also advise doing this on metal, as the VM approach will likely give you no hardware problems to solve along the way. You'll never learn how to fix what never breaks. ;)
Installing something that just works, or where you only need to click next in the installer only gets you a working system. It offers you absolutely nothing in the way of knowledge or understanding. What good to you is a working linux system if you know nothing about it? The method I propose will ensure you have all the basic skills and knowledge you need to be a (mostly) self sufficient linux user.
If you do take my advice and have any questions along the way, feel free to send me a direct message. I'd be happy to help.
I’d say it’s all up to whether your desire to distance yourself from Red Hat and it’s distros is great enough to be worth the effort of backing things up and re-installing everything. If you feel better using something that isn’t made by Red Hat after what’s been happening, then switch. If you feel like the effort to switch from something you are already deep into using isn’t quite worth it, then there’s no issue in sticking with it.
OnlyOffice. FOSS, great MS compatibility, more modern than LibreOffice, local apps and runs in web with Nextcloud with great document collaboration options.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.