Gregory's ServerI did linux servers for 8 years before i knew that the different numbers on the man pages were a secret code that had a concrete meaning for what kind of man page it is. Give me fucking break.
|
5 comments
@forestjohnson That's not to say that things are great now. Not at all. I'm just trying to say that the problem is large to the point where it seems that nobody has ever even TRIED to fix it. @hp Yeah, that's what I'm saying, nobody has done it yet. But that doesn't mean its impossible. Windows is absolutely not the way, but I do believe that a well-documented HTTP-based UI for linux, systemd, and docker, could potentially be a home run. It would have to include the linux installer too, including managing the installation from a phone, so you don't have to plug a kbd and mouse into the 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. |
@forestjohnson I think that's fair to a point. But nobody has come close to doing anything like that.
Netware was kinda easy, in that respect, but it also couldn't do a great deal.
Windows is fine until something goes wrong. Then the difficulty curve becomes a cliff because it won't ever tell you anything useful. If you encounter a problem for the first time on Windows you have to go ask someone.
On Linux, at least, once you have a base set of knowledge you can mostly figure things out.