Roger Oberholtzer wrote:
On Sat, 2007-11-24 at 13:10 +0100, Philippe Landau wrote:
Aaron Kulkis wrote:
Roger Oberholtzer wrote:
It would be nice if there was a mechanism for other configuration systems to at least be started from YaST. Like gnome / kde / compiz configurations. Not to duplicate them. But at least to find them. I am sure there are many more config programs that can be located. Perhaps this should be a YaST module more than any change to YaST itself. But I think it is a missing feature. Something simple. Just a description of what the config program configs, and a button to start it. Those are user-level configurations. YaST is a SYSTEM level tool.
If those configuration programs were invoked from YaST, they would only change root's configuration -- they wouldn't change diddly squat for the normal user.
And frankly, giving newbies the idea that a SYSTEM set-up tool should be where to go to change a USER'S customizations is just plain backwards. For most users there is no difference except root requiring entering a password.
Exactly. It is a fictional division. For example, you go into YaST to share a personal folder via NFS, not just system-wide folders. Quite often, and especially in a desktop system, the difference is blurred.
Perhaps to you, personally, but not to the kernal. The kernal makes a VERY big distinction between every user ID, and an even bigger distinction between root (UID 0) and every other user.
KDE's config ccenter, which is of course not under the control of YaST developers, has system settings. Of course YaST cannot keep other systems from allowing system setting changes. But the developers can recognize this fact that the distinction is not clear.
KDE's config center modifies the settings of the user whose current UID it is running under. IF started under UID 0 (root) then it's going to change the configuration of the the root user.... KDE's config tool doesn't know what user is at the keyboard and mouse...the only thing it knows is the UID is running under.
Perhaps what is needed is a YaDT (D for desktop) or YaUT (U for user) where all these other configs come together. But then I would suggest that some more things in YaST be moved there as they are not really system-level tools. Like bluetooth device pairings. Those must surely be per-user. But they are in YaST. Why have things like KIWI in YaST? You are not configuring the existing system. As a user you are perhaps making some other new system. IMO, a very 'user' activity. Unless we are making self-replicating/duplicating systems:)
This is just plain silly. IF I want to reconfig the KDE desktop, all I need to do is right-click on the desktop, and holy-smokes there's the option to configure the desktop. Using a system configuration tool to configure user's settings is just digging a rat's nest which will never end. How many applications are out there which have configuration files? How many thousand of those is SuSE supposed to write YaST modules for, and who chooses which apps have a module, and which don't. And when a system has other software loaded on it which is downloaded from some other site... then there will be complaints that the software is "broken" because there's not a dedicated YaST module to configure it. No developer has time to return mail to hundreds of newbies explaining why their "it's broken" complaints are problems of ignorance on their part, and nothing more -- precisely because of a precedence set by a system configuration tool team embarking on a journey into the never-ending rat-hole of trying to support configuration of user-level software.
So for most users a unified control panel would be helpful. There the difference between system and user level tasks can be educationally highlighted for example with different tabs, background colour etc. Of course the password prompt would only come up when required.
Kind regards Philippe
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org