To view parent comment, click here.
To read all comments associated with this story, please click here.
[i]fortunately most configuration tools in Linux are meerely front-ends to the configuration files</>
This is the proper way to do gui configuration tools. I frequently use these tools. However, I can't stand tools like YAST that fire up a big configuration "Wizard" that goes through and undoes all you hand-made changes.
The command-line and the GUI must remain friends! I remember when configuring DOS/WIndows was done via editing text files - autoexec.bat, config.sys, win.ini, sys.ini. Myab the horror of the Windows registry never come to the Free world!
I've never experienced problems with YaST's wizards (probably because I rarely hand-edit config files), but if they have a tendency to undo hand-made changes, this is a bug to be fixed, not necessarily a problem with the wizard approach.
That being said, I do find the wizards in YaST to be too unintuitive at times. Wizards are by definition supposed to be linear, and yet in YaST one is still faced with heierarchies of settings, just all displayed in one window instead of separate ones as in Windows.
For instance, setting up package selection during installation requires the user to leave the overall summary screen, make the changes, and then return to the summary screen before continuing. Why can't there just be an "advanced setup" option that incorporates these advanced settings in a linear manner?
Similar YaST issues can be found in other areas, too: the network devices and printer configurations especially come to mind as confusing tools to work with since they don't stick to a purely linear approach. While the interface is mostly a linear wizard, it also incoporates the equivalent of a heierarchy of dialog boxes, but all dislayed in the same window, which results in the end-user being confused about where he is in the process and why he's revisiting previous steps.
All this being said, YaST is a big step in the right direction in terms of giving hardware configuration a GUI. But it needs work to make all of its settings visible, either through a better, linear wizard approach, or by abandoning the wizard approach for a windowed heierarchy approach. I'm in favor of the latter: the web-like "one-page-fits-all" solution is notoriously poor for managing complex tasks with branchy natures, like system configuration.
...Perhaps if other distros took more of an interest in YaST, we could get it fixed faster!
(...then again, maybe there would just be infighting and stagnation; you never know.)





Member since:
2005-06-29
You're right, fortunately most configuration tools in Linux are meerely front-ends to the configuration files, because of that you can choose which approach you want to take. The best part about this is that graphical configuration tools in Linux, no matter how popular they get, should never mean the exclusion of configuration files.