Re: [sabayon] Sabayon for RHEL 4



On Tue, 2006-28-02 at 14:52 +0100, Alexander Larsson wrote:
> > I should have mentioned that: those files exist.  I made sure of that
> > before the test profile was applied to the test user.
> > The contents of the directories match the ones on FC4.
> > 
> > Any ideas?
> 
> Not really. That sounds strange though.

I got it working.  Here's what I did (on CentOS 4):

1. yum install gamin-python gnome-python2-gconf
2. rpm -ivh --nodeps sabayon-2.12.1-1.i386.rpm (from FC4 extras repo)
3. cd /usr/lib/python-2.3/site-packages
4. ln -s /usr/lib/python-2.4/site-pakagaes/sabayon .
5. cd /etc/gconf/2
6. Edited local-mandatory.path to read:

#include "$(HOME)/.gconf.path.mandatory"
xml:readonly:/home/$(USER)/.gconf.xml.mandatory

7. Edited local-defaults.path to read:

#include "$(HOME)/.gconf.path.defaults"
xml:readonly:/home/$(USER)/.gconf.xml.defaults

8. useradd test
9. created profile, Test, on a FC4 box
10. cd /etc/desktop-profiles
11. scp * root x x x x:/etc/desktop-profiles
12. Logged into Gnome with user, test.  The profile was applied.  Here's
the relevant log from /var/log/messages:

Mar  6 13:11:31 vmcentos gdm(pam_unix)[2194]: session opened for user
test by (uid=0)
Mar  6 13:11:39 vmcentos gconfd (test-12183): starting (version 2.8.1),
pid 12183 user 'test'
Mar  6 13:11:40 vmcentos gconfd (test-12183): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
configuration source at position 0
Mar  6 13:11:40 vmcentos gconfd (test-12183): Resolved address
"xml:readonly:/home/test/.gconf.xml.mandatory" to a read-only
configuration source at position 1
Mar  6 13:11:40 vmcentos gconfd (test-12183): Resolved address
"xml:readwrite:/home/test/.gconf" to a writable configuration source at
position 2
Mar  6 13:11:40 vmcentos gconfd (test-12183): Resolved address
"xml:readonly:/home/test/.gconf.xml.defaults" to a read-only
configuration source at position 3
Mar  6 13:11:40 vmcentos gconfd (test-12183): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 4


The key was editing the local-* files in /etc/gconf/2.  For some reason,
gconf would not read $(HOME)/.gconf.path.defaults or
$(HOME)/.gconf.path.mandatory: a bug, perhaps?.  So, I just commented
that line in each local-* and replaced it with the actual path.

I've done some testing, and so far everything seems to be working.  Of
course, the versions of Gnome in FC4 and CentOS are different, so not
all gconf settings will be applicable.  But, as I understand it, gconf
is supposed to be backwards compatible; that is, new gconf keys are
simply ignored in older versions of Gnome.  That being said, I made sure
to only apply those settings I knew were common to each version of
Gnome.

This looks very promising.  I am concerned that I have to force install
sabayon.  But, if I don't come across any bugs, I'm going to deploy this
for my customer.  It will make managing profiles much easier.

Regards,

Ranbir

-- 
Kanwar Ranbir Sandhu
Linux 2.6.15-1.1831_FC4 i686 GNU/Linux 
12:46:02 up 5:45, 3 users, load average: 1.36, 1.49, 1.24 





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]