Re: Locking down the gnome desktop


On Sat, 2003-12-06 at 23:09, Havoc Pennington wrote:

> However, the panel is extra special. It has several ways to confuse you,

	That's one way of putting it :-)

> which I hope I'll get right:
> 1. There was an original plan to allow "panel profiles," though this was
>    never exposed in the UI. So keys are stored in 
>    /apps/panel/profiles/<something>/foo where the <something> is 
>    variable - it should usually be "default"
> 2. In older versions, it would name the subdir for a given panel 
>    instance (such as top or bottom panel) with some random number
>    like 000001, rather than something like bottom_panel
> 3. The real fun one - /apps/panel/default_setup. When you log in the
>    first time and there are no profiles, the panel _copies manually_ the
>    contents of /apps/panel/default_setup to a new profile. So the panel 
>    has its sort of own layer of weird on top of gconf.

	It also needs the default setup so that when you log into a multihead
machine for the first time, it can setup the panels on those newly
available screens to the default setup.

> So, I _believe_ you should be able to create a profile in
> /etc/gconf/gconf.xml.defaults, under /apps/panel/profiles/, and the
> panel would then simply ignore /apps/panel/default_setup.

	Yes, that should work ... but it won't pick up the defaults for

	(I accept that there is an argument that the panel should just copy the
user's panel configuration to the new screens ...)

> The admin guide says there's a toplevel_id_list, but I don't see this in
> my current setup; if there's no list like this, I'm assuming panels
> found in gconf.xml.defaults can't be deleted by the user since they will
> always appear in gconf directory listings, I could be wrong.

	No, there is a toplevel_id_list in general/toplevel_id_list in the
profile directory.

	So, if I was looking to set this up I'd do something along the lines

	1) Create a /etc/gconf/gconf.xml.mandatory.local
	2) Add that to /etc/gconf/2/path
	3) Copy /etc/gconf/schemas/panel-default-setup.entries and
	   modify it to taste.
	4) Install it into the mandatory database using a command
	   along the lines of:

gconftool-2 --direct
	    --load my-default-panel-setup.entries

	That should work fine, but I haven't actually tested it ..


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