• 1 Post
  • 52 Comments
Joined 5 months ago
cake
Cake day: December 13th, 2024

help-circle










  • So yeah, even though I specifically said you’d probably accuse me of saying something and specifically told you I wasn’t saying that, you still accused me of it. You should work on your reading comprehension.

    Now, you said that a desktop edition is virtually the same as a server edition + a prepackaged GUI. I gave you plenty of reasons they’re not.

    As an IT professional, you absolutely should know this. So far, the only skill you’ve shown any true mastery of is misguided condescension. So instead of arguing against a point I didn’t make, if you’d like to argue against my actual point, feel free. Otherwise, maybe realize you’re not as educated as you thought, and learn.


  • I mean if that’s what you think, I can tell you don’t work in the industry. Desktop editions generally have more than just a “prepackaged GUI” on top of a server edition.

    • Server editions generally have text based installers. This might not seem like a big deal, until you’re installing on a system that doesn’t have any graphics, just a serial console.
    • They almost always have an easy way to do headless and network installations.
    • They sometimes have additional security modules, like SELinux, different kernel boot parameters, or even different kernel versions. (Although this is less common nowadays.)
    • They’re also missing an audio server (different than a GUI), and usually a print server.
    • They can often be GBs lighter, which makes a difference when you’re installing on virtual machines with limited disk space.
    • They sometimes use different file systems by default (like Fedora used to).
    • They might create different swap setups.
    • They usually have very different network defaults. Like, desktop editions usually have a firewall, whereas server editions usually don’t (or it’s not enabled by default).
    • Server editions often include terminal tools that desktop editions don’t.
    • They’ll sometimes have a different network manager (Ubuntu Server uses systemd-networkd while Ubuntu Desktop uses Network-Manager).
    • Server editions almost never come with userland file mounting tools like gvfs.
    • Sometimes (like in Fedora) a server edition will come with remote management solutions like Cockpit.
    • The home directory skeletons will be vastly different on a server vs a desktop.

    That’s just off the top of my head. I’m sure there are plenty more I could find.

    Now, since you seem like you might accuse me of it, note that I did not say that a server edition and a desktop edition can’t be swapped back and forth by installing and removing packages and changing a bunch of config. They can. But, it’s not “just” some GUI stuff that makes a desktop edition, and it’s not “just” the lack of a GUI that makes a server edition. They are usually quite different.

    Source: I’ve been a professional Linux server administrator for 16 years. But don’t take my word for it. Try it yourself. Install Ubuntu server, then run sudo apt install ubuntu-desktop and see if it’s exactly the same as installing Ubuntu Desktop.




  • If you want to ride a bike, you need to learn to balance on a bike. That will never change. You don’t need to be a professional cyclist.

    If you want to self host, you need to learn some basic administration, and that includes the terminal. That will never change. You don’t need to be a professional server administrator.

    You might be able to get by with some hand holdy solution that offers a few things you can do, but just like riding a scooter is much more limited than riding a bike, using a turnkey solution is much more limited than setting up your own server.

    Imagine wanting to self host but refusing to learn how to forward a port. There are just some things you need to learn. Like I said in my original comment, the terminal is not as scary as people make it sound. Right now, you are the person making it sound scary.