>>>Out of curiosity, why would it allow me to configure anything from the >>>shell, and the gui tools won't save properly? If I were doing a bad thing, >>>I'd be doing it either way. >>> >>> > Not necessarily. From the command line, you're talking directly to the > files in question. From the GUI, you're only talking to the GUI and > depending on the GUI to pass along your inputs to _all_ of the relevant > files and then depending on the SAVE button on the GUI to save all of > those files' changes. GUIs can be simple or complex to write because of > the need for all those callbacks to work correctly. Almost always, the > GUIs do a fine job, because the GUI writers work very hard to get the > GUIs right. However, s*t happens, and sometimes (rarely) a GUI will > miss something. For a minute I believed you (actually, of course, you're right), but the thing is, now after I've disabled selinux, the guis DO seem to work right. I'm 90% sure (but not 100%) that the gui wasn't trying to do something funny behind the scenes.
