Re: GDM in sid does not read /etc/environment anymore
- To: Petter Reinholdtsen <firstname.lastname@example.org>
- Cc: email@example.com
- Subject: Re: GDM in sid does not read /etc/environment anymore
- From: Daniel Ruoso <firstname.lastname@example.org>
- Date: Mon, 01 Sep 2003 15:34:04 -0300
- Message-id: <[🔎] 1062441244.955.6.camel@guarani>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <20030829170154.B6834@saruman.uio.no> <20030829173316.GA1347@dat.etsit.upm.es> <1062185895.2542.4.camel@guarani> <email@example.com>
There is a patch posted to this bug that grep /etc/environment looking
for LANG=*, and then export just the LANG...
Em Dom, 2003-08-31 às 10:47, Petter Reinholdtsen escreveu:
> [Daniel Ruoso]
> > I've actually sent him an email but got no answer. I've posted in
> > debian-devel few days ago and nobody complained that GDM could source
> > /etc/environment in the init script. That's an one-line patch (already
> > tagged as patch in bts for more than a year)...
> Remember that the file /etc/environment is not a shell script, it is a
> data file for the pam_env module. The format happen to look like a
> shell script, but it is not.
> See for example <URL:http://linux.oreillynet.com/lpt/a/1263> for a
> description of the format.
> If you want to pass the values on to forked program, this might be
> for i in `cat /etc/environment`; do export $i; done
> It will probably not handle space in the content.