Not picking one method or the other, but just wanted to add that Webmin strips out any comments that are located within a config file. This may or may not be important to people, but if you wish to have the comments in the config files available at a later date, then make a back-up of these files before firing up Webmin.
Cheers! Neil On Wednesday 03 January 2007 15:24, Gustin Johnson wrote: > TAB auto complete, screen, vim, tail -f /var/log/somelogfile > > Webmin cannot compete with this. It is an order of magnitude slower, > especially for troubleshooting. > > Having said that, webmin certainly has its place, but most of the time > it gets in the way. > > Jon wrote: > > Great minds... :) > > > > I disagree that CLI is faster in all cases. I have so many servers now > > that it's quite frequently easier to click, click, than it is to ssh, > > type, type, type, type, type, type, type. > > > > However, it took me about a month to even start looking at the GUI > > because I was so used to CLI. > > > > J > > > > Shawn wrote: > > The problem with webmin though is that while the graphical interface is > > convenient, you STILL need to know what you are doing with the > > underlying server. With samba, if you enter something for the directory > > mask and get this wrong, you'll either not be able to access your > > shares, or the security will be too open. But this is a Samba problem, > > not a webmin problem. > > > > So, after you go through the trouble of learning how to deal with your > > service, you quickly find webmin more gets in your way than helps you. > > THe time it takes to open a browser, navigate to webmin, login, make the > > changes, save the changes - this adds a delay. If you understand your > > service that well, it's so much faster to just edit the text file in > > question, without the network lag of a web browser. > > > > And if you end up editing the config files directly because you now know > > enough to do so, then why do you need webmin?? :) > > > > I'm not saying "don't use webmin", but showing that webmin is but a > > stepping stone in the path of server knowledge. > > > > On the other hand, seeing as webmin allows direct configuration of your > > servers, you need to take precautions to ensure it is not accessible to > > unauthorized folks. It should never be made accessible outside the > > local network - unless you know what your doing with the security side > > of it. Just a thought. > > > > Shawn > > > > > > Jon wrote: > >>>> That's the rub, yes. Webmin modules simply put a nice HTML GUI into the > >>>> various servers installed on a system. While it can apt-get (or yum) for > >>>> you, in general it's not going to configure a server for you. The > >>>> knowledge about how various apps should be configured still lies with > >>>> the user. > >>>> > >>>> One thing that I do like GUIs for is that they frequently expose options > >>>> that are otherwise unapparent. The Samba webmin module is a good example > >>>> of a nice module that presents all of the 'obvious' Samba functionality > >>>> (like Unix/Samba user sync, for example) right in your face. It's good > >>>> for quick start stuff. > >>>> > >>>> J -- Neil Bower CLUG - http://clug.ca Registered Linux User # 323470 ( http://counter.li.org ) _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
