From: Forrest Voight <voights@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: /etc/rc.conf
Date: Mon, 13 Feb 2006 17:24:11 -0500 [thread overview]
Message-ID: <b572c9e10602131424t1887d4fbwd869b21fbee1ed79@mail.gmail.com> (raw)
In-Reply-To: <1139868629.24829.0.camel@cocagne.max-t.internal>
What happens if two env.d files set the same variable?
On 2/13/06, Olivier Crete <tester@gentoo.org> wrote:
> On Mon, 2006-13-02 at 16:51 -0500, Forrest Voight wrote:
> > What about env.d? Gnome could install and env file that by default
> > sets XSESSION to gnome.
>
> Can't do... you can have gnome, kde, xfce, etc all installed at the same
> time.
>
> > On 2/13/06, Paul de Vrieze <pauldv@gentoo.org> wrote:
> > > On Monday 13 February 2006 13:19, Forrest Voight wrote:
> > > > Why doesn't it make sense to split DISPLAYMANAGER and XSESSION up?
> > > > They are related, but in different contexts. XSESSION is for the user
> > > > and DISPLAYMANAGER is used at boot time.
> > > >
> > > > On 2/13/06, Paul de Vrieze <pauldv@gentoo.org> wrote:
> > > > > On Monday 13 February 2006 03:33, Donnie Berkholz wrote:
> > > > > > And even then, it's only copied over when you specify the -m
> option
> > > > > > to useradd. It isn't done by default.
> > > > >
> > > > > Users might further decide they use a .bashrc from a different
> > > > > system, or to clean all percieved cruft from the
> > > > > .bashrc/.bash_profile. Having a sane default is probably better.
> > >
> > > I was just arguing why one should not keep XSESSION in .bashrc only, and
> > > rely on skel. It's too easy to break.
> > >
> > > Paul
> > >
> > > --
> > > Paul de Vrieze
> > > Gentoo Developer
> > > Mail: pauldv@gentoo.org
> > > Homepage: http://www.devrieze.net
> > >
> > >
>
> --
> Olivier Crête
> tester@gentoo.org
> Gentoo Developer
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-13 22:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 19:16 [gentoo-dev] /etc/rc.conf Forrest Voight
2006-02-12 19:38 ` Donnie Berkholz
2006-02-12 23:33 ` Chris Gianelloni
2006-02-12 23:49 ` Donnie Berkholz
2006-02-13 0:03 ` [gentoo-dev] /etc/rc.conf Forrest Voight
2006-02-13 0:37 ` Donnie Berkholz
2006-02-13 0:56 ` Forrest Voight
2006-02-13 1:27 ` Edward Catmur
2006-02-13 2:33 ` Donnie Berkholz
2006-02-13 9:43 ` Paul de Vrieze
2006-02-13 12:19 ` Forrest Voight
2006-02-13 12:26 ` Paul de Vrieze
2006-02-13 21:51 ` Forrest Voight
2006-02-13 22:10 ` Olivier Crete
2006-02-13 22:24 ` Forrest Voight [this message]
2006-02-13 23:42 ` John Myers
2006-02-14 0:01 ` Alec Warner
2006-02-14 0:26 ` Mike Frysinger
2006-02-14 1:07 ` Forrest Voight
2006-02-14 1:15 ` Mike Frysinger
2006-02-14 10:28 ` John Mylchreest
2006-02-14 11:16 ` Forrest Voight
2006-02-12 23:52 ` [gentoo-dev] /etc/rc.conf Daniel Drake
2006-02-12 21:49 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b572c9e10602131424t1887d4fbwd869b21fbee1ed79@mail.gmail.com \
--to=voights@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox