[5520] in Release_7.7_team
Re: The 9.9 default xsession
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Jul 7 02:01:04 2006
Date: Fri, 7 Jul 2006 01:59:47 -0400
Message-Id: <200607070559.k675xlFR018887@cage-2.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
CC: release-team@mit.edu
In-reply-to: <200607051941.k65JfcFl004703@egyptian-gods.mit.edu>
X-Spam-Score: 3.548
X-Spam-Level: *** (3.548)
X-Spam-Flag: NO
> 1. Hardcoded things (gconfd-2 for its own use; gnome-settings-daemon)
> 2. Stuff listed in the user's session file or the default session
> 3. Stuff in desktop entries in the auto-start directories
A little more research revealed a fourth category:
4. Startup programs listed in ~/.gconf2/session-manual
These are intended to be programs which are not X session clients.
However, there is no site configuration (no analog of the default
session), so I don't think we can reasonably put
zwgc/get_message/etc. in there.
On a separate note, I've been thinking that we should move away from
the console concept. Right now the console is used chiefly to display
the results of mailquota and from, although it of course also displays
any error output from the standard login commands (at least, the ones
we don't redirect the output of to /dev/null) and from the user's
dotfiles. That output can be retrieved from /tmp/xsession-*, so I'm
not too worried about it.
So I'm thinking we can replace mailquota with a warning dialog when
the user is over mail quota (once again, zenity is kind of useless
here, but we can figure something out), and maybe just punt the from
dialog. In the age of poor-quality spam filters, you always have new
mail at login time.
For now, I'm going to punt both, and we can add back the quota
warnings later.
