3 ms·
Can you elaborate on the reasons for using Fedora server instead? I use Fedora Workstation on several laptops and desktops (without issue). I'm curious if I'm
by rkangel 6y ago
Can you elaborate on the reasons for using Fedora server instead?
I use Fedora Workstation on several laptops and desktops (without issue). I'm curious if I'm missing some problem/opportunity.
- rwmj 6y agoDefaults to GNOME, firewall disabled, ext4 (and now btrfs) instead of XFS. (These spins are all about defaults - so installing Server doesn't make it any less useful for desktops, but you may have to dnf install a few things the first time you use it.)
- rkangel 6y agoWhat do you mean "defaults to GNOME"? Server defaults to no DE at all I thought (been a year or two since I've used it) and Fedora defaults to GNOME anyway. If it by default doesn't install email client and music players I don't use that might be nice though.
- boredishBoi 6y agoI think the defaults they’re referring to are for fedora desktop, not server
- rkangel 6y agoYes you're right - thank you. On a re-read I see that I had the assertions the wrong way round.
- diffeomorphism 6y agoThese points seem to be about why fedora workstation is not a great fit for him/her. Workstation defaults to gnome, other spins or server don't.
- yjftsjthsd-h 6y ago> What do you mean "defaults to GNOME"? Server defaults to no DE at all I thought (been a year or two since I've used it) and Fedora defaults to GNOME anyway. The "workstation" version uses GNOME.
- vetinari 6y agoI'm pretty sure Fedora Workstation comes with firewalld enabled: $ systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
- rwmj 6y agoBut with all the high ports open by default: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GUAWCR2C7OSVKVXUYHOHWNIBGFVSYK65/ https://lists.fedoraproject.org/archives/list/devel@lists.fe... The justification was that blocking firewall ports breaks user applications.
- vetinari 6y agoI have mixed feelings on this: - on one hand, nothing listens on these ports by default; and they have a point that it does break user applications; - on the other hand, they should be closed, and users should open them explicitly once they install an app that needs it. However, I'm afraid we would see exactly the same thing we see with SELinux: many tutorials about installing apps or services start with "Disable SELinux" instead of how to enable exactly what is needed. We would see the same thing with firewall and "Disable firewall" as step 1. - as a sidenote to the second point: many apps do not ship with firewalld profile, so it is not a matter of `firewall-cmd -add-service $appname` either.