public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jon Nall <nall@gentoo.org>
To: MAL <mal@komcept.com>
Cc: gentoo-user@gentoo.org, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] distcc
Date: 09 Feb 2003 14:38:20 -0600	[thread overview]
Message-ID: <1044823096.31643.1.camel@reykjavik> (raw)
In-Reply-To: <3E46A7C6.4020002@komcept.com>

[-- Attachment #1: Type: text/plain, Size: 685 bytes --]

why not just alias su="su -"? i did this (because i had the same
headaches you describe) and it hasn't bothered me since.

nall.

On Sun, 2003-02-09 at 13:11, MAL wrote:
> Nick Jones wrote:
> >>login).  On a side note, suing to root, didn't give me gcc either... I 
> >>had to add '. /etc/profile' to my root's .bashrc.
> >>
> >>Anyway, to fix this I simply added '. /etc/profile' to 
> >>/etc/init.d/distccd, just before it starts distccd.
> > 
> > su -
> 
> Yes, I know why.. thus my adding to .bashrc. Remembering to type su - 
> every time to login, is not a solution, it's an additional problem.
> 
> MAL
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-02-09 20:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 11:46 [gentoo-dev] distcc MAL
2003-02-08 15:59 ` Eric Andresen
2003-02-09 11:21 ` Nick Jones
2003-02-09 19:11   ` MAL
2003-02-09 20:38     ` Jon Nall [this message]
2003-02-09 21:01     ` [gentoo-dev] Re: [gentoo-user] " Martin Schlemmer
2003-02-10 20:04       ` nealbirch
  -- strict thread matches above, loose matches on Subject: below --
2004-02-23  5:26 [gentoo-dev] Distcc Lisa Seelye
2002-10-12 22:58 [gentoo-dev] distcc Wout Mertens
2002-10-13  3:28 ` Evan Read

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=1044823096.31643.1.camel@reykjavik \
    --to=nall@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-user@gentoo.org \
    --cc=mal@komcept.com \
    /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