On Fri, Jul 05, Steven T. Hatton wrote:
Another thing I find a bit disorienting is the way the contents of the /etc/rc.config have been moved into /etc/sysconfig. This certainly has its good points. It is easier to find a particular configuration item this way. I suspect it also lays the groundwork for bigger and better things to come. One of these is, I hope, a return to providing a mask over these configuration items.
What are you missing? You can edit this variables in three ways: 1. vi/emacs/your favorite editor 2. with the YaST2 config module for the service to which the sysconfig file belongs. 3. YaST2 sysconfig editor (like YaST2 rc.config editor before). You have the same three choices as before.
Now it seems necessary to start processes such as Apache by explicitly modifying the runlevels. That's fine, if that's what SuSE intend for us to do. The interface we have for that is likewise very nice. The difficult part seems to be figuring out what SuSE expect us to do. That is, *should* I be using the runlevel editor for starting services automatically?
You can do what you wish. If you like to do it with the mouse, use the YaST2 runlevel editor. If you don't like this, use insserv or chkconfig on the console. Or use ln and rm, ...
Is there a paradigm shift in YaST? Am I just having trouble adjusting to a new and better way of doing things, or are there really shortcomings in the current (SuSE 8).
We only make some things easier: why creating/deleting links and edit START_* variables, if creating/deleting links is enough and more flexible? Now you can start services only for one runlevel and not, as before, for all or none.
I very much like the new look and feel of the GUI based YaST2. The terminal based version, well....(how 'bout using tab to move the focus?) What do others think of YaST verses YaST2?
I always use tab to move to the next focus. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B