@RojoLoco said in CentOS 7 File Server (samba). Do you know easy GUI to manage ?:
@scottalanmiller said in CentOS 7 File Server (samba). Do you know easy GUI to manage ?:
@RojoLoco said in CentOS 7 File Server (samba). Do you know easy GUI to manage ?:
@Dashrender said in CentOS 7 File Server (samba). Do you know easy GUI to manage ?:
@scottalanmiller said in CentOS 7 File Server (samba). Do you know easy GUI to manage ?:
Why do you want a GUI? What's the end goal?
I'm guessing his goal is to not have to learn CLI commands.
I'm the captain of that vessel... it's the 21st century, why in the hell would I restrict myself to needing to type letters at a computing system to make it go? Are we cavemen, dragging our knuckles toward the black screen with archaic green letters to type cryptic text commands when GUIs have existed for a couple of decades now? I thought we lived in the future.
GUI is the past, CMD is the future. GUI was an experiment in the 1990s and it went poorly. Microsoft has made it clear that even in the Windows world, GUI is legacy. And with DevOps, the drop off of GUI is rapid.
And yet in an SMB windows environment, I can accomplish literally everything I need to do and then some via GUI. Funny how that works, eh? Because the bottom line is not how you think I should do it, but how I actually accomplish daily, weekly, monthly tasks without CLI. GUIs work 110% for the stuff I've ever had to administer (insert SAM bashing everything I've ever done here to prove that all the world needs to use CLI all the time always), and the lack of possibility that a simple typo can ruin a day's work, I'll keep my GUI and continue having an easy, well paid job, thanks. Different strokes for different mafackas. In the immortal words of Peter Lorre, "you do it your way, and I'll do it mine".
I disagree. GUI is not "scriptable" in any way, so the only thing you can do is learning procedures and apply that point-and-click algorithm like a robot. I won't call it "do a sysadmin task", sorry.
In addition, there is a hard limit in what you can do in a defined amount of time because of the intrinsic click/wait ratio of your procedures (and of your brain, of course). Of course, there is also a limit in your minimum error ratio following the procedures, because even if you do only one error every 10k clicks, you will have 100 errors every million of clicks… I think that doing gui-based sysadministration require ~2k clicks per full working days.
You can throw all those limits if you simply script a procedure. The error ratio of a correct script is ZERO, and you can run it as fast as your machine (and not your brain-hand system) can. Machines today are VERY fast.
Scripted procedures are the building blocks used to build great services, and it's not an opinion or something that some of us say because we are all biased in certain way.
It's automation, baby!