Brian Cameron wrote: > Thomas: > >> Am I right with this view: >> The purpose of the gnome-cleanup script is, to wipe things >> from the config which changed in incompatible way with >> the upgrade of GNOME. > > No. This script is mainly provided for support services. > > There are certain things that can cause a user's GNOME > configuration to become corrupt, and this can often lead > GNOME failing to start, or work properly. > > Support services often tells users to run the gnome-cleanup > script to return their configuration to the default values. > While not elegant, this often fixes common problems that > are reported. > > In other words, you typically want to clean up a specific > user's configuration without rebooting the machine. > > Brian > >> Other Questions: >> >> o Centralized HOMEs may share GNOME settings between mutiple >> GNOME-Versions? > > This is possible, though typically when users want to run > gnome-cleanup, they understand that this will restore their > GNOME defaults for all machines that share the same $HOME > directory. > >> o Would an instand "upgrade" or even "downgrade" cleanup be >> better done instantly at Login-time. >> Machine-centric general cleanup could be still be necessary >> and be done by an SMF-script > > I don't think this relates. > >> o what if a GNOME-version is downgraded by simply rebooting >> an old Boot-Environment. Then possible new configs in >> user HOMEs hit old GNOME bits. Would then be a downgrade >> of the config needed? > > GNOME tries to be compatible between versions in terms of its > configuration, so downgrading should not be needed. However, > some people run into problems when they use unsupported versions > of GNOME (such as when they use the latest & greatest development > builds). These aren't supported, and are not guaranteed to be > compatible, and may corrupt your configuration. > > Brian > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org
So why not setup a mechanism so that the user's login removes the files next time he logs in if a config file in his own directory doesn't exist or is older than the timestamp of some system config file? This would work automatically for all users on next login.... Note that this behavior might well be intensely irritating for many users, however; I can imagine ITops deleting my gnome config everytime I log into a SunRay like they do on my ~/Desktop directory. -= Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird."
