Le dimanche 27 juin 2010 à 01:40 +0100, Roger Leigh a écrit :
> On Fri, Jun 25, 2010 at 01:46:41PM +0200, Josselin Mouette wrote:
> > You may also need (but I haven’t checked):
> > * /var/run/cups for printing
> > * /var/run/avahi-daemon
> > and some others that I’m forgetting.
>
> Thanks! I think we now have most of these. We don't preserve the
> environment by default (you have to use the -p option), but we
> could make that automatic in a future release by adding a new
> configuration option.
You should definitely pass the following environment variables without
asking, since GNOME applications won’t work without them:
DISPLAY
XAUTHORITY
ORBIT_SOCKETDIR
DBUS_SESSION_BUS_ADDRESS
The following shouldn’t hurt as well.
Terminal:
TERM
COLORTERM
XSMP support (probably doesn’t work in a chroot):
SESSION_MANAGER
gnome-keyring (only the SSH stuff works across the lenny→squeeze
upgrade):
SSH_AGENT_PID
SSH_AUTH_SOCK
GNOME_KEYRING_CONTROL
GNOME_KEYRING_PID
seahorse:
GPG_AGENT_INFO
Used by xdg-utils and debianutils scripts:
XDG_SESSION_COOKIE
DESKTOP_SESSION
GNOME_DESKTOP_SESSION_ID
GTK+ modules to load:
GTK_MODULES
GTK_IM_MODULE
Language:
LANG
LC_*
> We definitely have /tmp and all of /var/run
> so most of the above should be catered for.
Passing all of /var/run looks a bit dangerous to me since it could lead
some scripts in the chroot believe that a daemon is started in the
chroot. I’m not sure if that’s a real problem, but you should probably
at least print a warning somewhere.
> If anyone on the lists is using schroot for desktop applications,
> I'm currently uploaded schroot version 1.4.5-1 which adds a
> "desktop" configuration profile. Just set
> script-config=desktop/config
> in your chroot definition.
Great!
--
.''`. Josselin Mouette
: :' :
`. `' “If you behave this way because you are blackmailed by someone,
`- […] I will see what I can do for you.” -- Jörg Schilling
Attachment:
signature.asc
Description: This is a digitally signed message part