3 ms·
So, this raises the question of why you're running a desktop-oriented OS on a server. As a staging area. The main reason for not using Fedora as a production
by dhimes 17y ago
So, this raises the question of why you're running a desktop-oriented OS on a server.
As a staging area. The main reason for not using Fedora as a production server is not that it is desktop oriented but that it updates too frequently. Some of us (well, at least one of us) run(s) servers on our desktops as well.
- ubernostrum 17y agoAnd it certainly seems to be easy to change the policy settings to disallow people installing packages :) I guess I'm just looking at this from the POV of Fedora really trying to be an everyday desktop OS, where minimal pain in installing new software is a good thing and Fedora's policies for trusted repositories and signed packages help keep the risk minimal (yeah, somebody could sneak a backdoor into something in a Fedora repo, but if they can do that they're interested in more than owning your desktop machine).
- dhimes 17y agoThe way to success as an everyday OS isn't through bad policy, it's through education and clarity. Put in the right policies but make them easy for the end user to understand and change. Commands like "restorecon" suck (as an everyday OS). But if, attached to a mv (or its gui equivalent) was a message: "the default permissions for this directory are to make the file available to X, Y, and Z. Would you like to make these files available, too?", it would work. Even better is a mv -yes (& gui equivalent) which does it automatically.