hm yes, had a look at wows sfs, these groups seem to miss, too.
Gnome can be a real mess, but at least some applications should start.
You might type in JWM in a console things like:
gnome-panel
epiphany
gnome[tab to see more]
That gives clues about what misses.
Anyway, here are my files:
/etc/group
Code: Select all
root:x:0:
daemon:x:1:
tty:x:2:
ppp:x:200:
users:x:500:
nobody:x:65534:
guest:x:501:
spot:x:502:spot
bin::2:root,bin,daemon
audio::17:
503:x:503:messagebus
haldaemon:x:3:
video:x:504:
cdrom:x:505:
disk:x:506:
plugdev:x:507:hal,root
uucp:x:508:
kmem:x:509:
lp:x:510:
floppy:x:511:
power:x:512:avahi::86:avahi
netdev::85:avahi
gdm::95:gdm
netdev::87:avahi
sabayon::63:sabayon
stb-admin::87:
storage:x:95:hal,root
vboxusers:x:513:root
gshadow
Code: Select all
root:::root
bin:::root,bin,daemon
daemon:::root,bin,daemon
sys:::root,bin,adm
adm:::root,adm,daemon
tty:::
disk:::root
lp:::daemon,lp
mem:::
kmem:::
nobody:::
users:::
utmp:x::
floppy:x::
pppusers:x::
nogroup:!::
spot:!::
503:!::
haldaemon:!::
video:!::
power:!::
postgres:!::
pulse:!::
pulse-rt:!::
pulse-access:!::
vboxusers:!::
shadow (contains the encrypted passwords)
Code: Select all
root:$1$FD.MrIhr$BsfBOUpaBH4TPKcq0VcSk0:11329:0:99999:7:::
daemon:!:11141:0:99999:7:::
nobody:!:11141:0:99999:7:::
spot:!:12822:0:99999:7:::
bin:*:9797:0:::::
messagebus:!:0:99999:7:::
haldaemon:!:13993:0:99999:7:::
avahi:*:86:0:::::
gdm:*:95:0:::::
sabayon:*:9797:0:::::
passwd
Code: Select all
root:x:0:0:root:/root:/bin/sh
daemon:x:1:1::/:
nobody:x:65534:65534::/tmp:
spot:x:502:502:Linux User,,,:/root/spot:/bin/sh
bin:x:2:2:bin:/bin:
messagebus:x:503:503:Linux User,,,:/tmp:/bin/sh
haldaemon:x:504:3:Linux User,,,:/home/haldaemon:/bin/sh
avahi:x:86:86:avahi:/etc/avahi:
gdm:x:95:95:gdm:/etc/X11/gdm:
sabayon:x:63:63:Sabayon user:/var/sabayon:/bin/false
gnome relies on other settings, too.
Critical seems to be
/etc/gconf/gconf.xml.defaults/
Make sure, it has the same values as in WOWs sfs.
But these might be altered by Gnome itself afterwards.
Gnome uses config and registry files spread all over the filesystem.
The programs it depends on, have them elsewhere.
This is a mess to find out, what interacts with what.
Once you start the panel with wrong/missing settings, it is broken.
It then might be best, to replace completely with the original the
/etc/gconf/gconf.xml.defaults/
One thing that
might work for full installations:
download Muppy0084beta1 LIVE and Gnome.
Merge with SFS-Combiner msy_084.sfs and Gnome.sfs, so that you have a very large msy_084.sfs.
Then boot this frugal or burn a CD, and with this, create a full installation.
But I did NOT test this myself.
Sorry that I can't be more precise, but it took me 3 weeks fulltime to get Gnome to work (almost) as expected.
At least the issues mentioned above, might help you to find out, where the problem is.
One thing concerning HAL:
to fix automount problems, edit:
/etc/dbus-1/system.d/hal.conf
from:
Code: Select all
<deny send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
<deny send_interface="org.freedesktop.Hal.Device.VideoAdapterPM"/>
<deny send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
<deny send_interface="org.freedesktop.Hal.Device.Volume"/>
<deny send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
to:
Code: Select all
<!-- deny send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/ -->
<!-- deny send_interface="org.freedesktop.Hal.Device.VideoAdapterPM"/ -->
<!-- deny send_interface="org.freedesktop.Hal.Device.LaptopPanel"/ -->
<!-- deny send_interface="org.freedesktop.Hal.Device.Volume"/ -->
<!-- deny send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/ -->
Without this, it conflicts with other settings in this file.
Mark