Gregory's Server@forestjohnson I'm mostly wondering how to preserve the "useful errors that will tell you what went wrong."
I've never seen that done in anything GUI-like, other than just stuffing a log-file into a textbox. And at that point it'd be better to be able to run grep on it, or find all logs around the same time on the system...
How do you give a novice user information like "This violated an SELinux policy" and let them fix it, without making it easy to accidentally allow an exploit to run.
@hp
> How do you give a novice user information like "This violated an SELinux policy"
1. disable SELinux
2. If you want to enable SELinux, you have to make a GUI for it -- you have to actually go into the SELinux source code and add the parts that will enable actual usability. Not to create a shitty error message like "This violated an SELinux policy", but to create an error message that contains the word "because".
------------------------
.. nobody has ever even TRIED to fix it.
Nobody ever tried to fix climate change either... But if we don't fix it, it's all over real quick.
I believe in an interpretation of what we observe about the universe that says that "what we observe is generally what was most likely to happen". aka "many worlds"
In a thousand years, the only likely outcome that anyone will be around to observe, is the outcome where we got thru it...
I took a heroic dose of psychedelics and saw the Golden Path, so I'm trying to walk it. Succeed or fail, don't care, at least I tried and did my best. Sue me.
@hp
> How do you give a novice user information like "This violated an SELinux policy"
1. disable SELinux
2. If you want to enable SELinux, you have to make a GUI for it -- you have to actually go into the SELinux source code and add the parts that will enable actual usability. Not to create a shitty error message like "This violated an SELinux policy", but to create an error message that contains the word "because".