[gentoo-dev] /etc/profile

[gentoo-dev] /etc/profile

[messdev]

Why exporting global variables' mechanism is so complicated? It is not very 
,,user friendly'' to edit /etc/env.d/00basic to change some global variables, 
whitch then go to /etc/profile.env and then to /etc/profile... It's not 
intuitively. Or maybe there is some simpler way to edit it?


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] /etc/profile

[Alexander Gretencord]

On Thursday 28 November 2002 01:50, messdev wrote:
> Why exporting global variables' mechanism is so complicated?

Is it?

> It is not very ,,user friendly'' to edit /etc/env.d/00basic to change some
> global variables

Well, where's the problem? Instead of editing one file called /etc/profile you 
edit another file called /etc/env.d/something. How the mechanism of getting 
it into your shells environment works doesn't have to bother you.

> It's not intuitively. Or maybe there is some simpler way to edit it?

Well as said, what's not simple in editing _one_ file? You've always edited 
_one_ file.

Just think about what is achieved by this mechanism. It's a simple and good 
solution to a problem. And normal users usually don't change global settings 
anyway, but use their own .profile which is not affected by portage's 
handling of global profile entries. As a sysadmin you will appreciate 
gentoo's handling as packages can add to the global settings without messing 
around with the actual file.


Alex

-- 
"They that can give up essential liberty to obtain a little temporary safety 
deserve neither liberty nor safety."
Benjamin Franklin


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] /etc/profile

[messdev]

Ok. But when you try to learn how to define global variables it is difficult 
to make an idea, that u should do it in /etc/env.d/*

When you look into /etc/profile you can see `source /etc/profile.env` - then, 
when you look into /etc/profile.env, everything points, that u should change 
definitions exacly in this file - i wanna say, that it is a good idea to put 
the comment into /etc/profile.env, that this file is genereting by using 
/etc/env.d/* files, and the definitions of variables there.

Or maybe i'm wrong... :)

Messer.

--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Re: /etc/profile

[Paul]

messdev <messdev@messer.homelinux.org>, on Fri Nov 29, 2002 [12:07:56 AM] said:
> Ok. But when you try to learn how to define global variables it is difficult 
> to make an idea, that u should do it in /etc/env.d/*
> 
> When you look into /etc/profile you can see `source /etc/profile.env` - then, 
> when you look into /etc/profile.env, everything points, that u should change 
> definitions exacly in this file - i wanna say, that it is a good idea to put 
> the comment into /etc/profile.env, that this file is genereting by using 
> /etc/env.d/* files, and the definitions of variables there.
> 
> Or maybe i'm wrong... :)
> 
> Messer.
> 
> --

	Hi;

	I agree, /etc/profile.env should have the same message at
the top as /etc/ld.so.conf, as they are both autogenerated by
env-update. Go ahead and make a bug report on bugs.gentoo.org.
It should be a trivial adjustment.

Paul
set@pobox.com

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] /etc/profile

[Martin Schlemmer]

On Fri, 2002-11-29 at 01:07, messdev wrote:
> Ok. But when you try to learn how to define global variables it is difficult 
> to make an idea, that u should do it in /etc/env.d/*
> 
> When you look into /etc/profile you can see `source /etc/profile.env` - then, 
> when you look into /etc/profile.env, everything points, that u should change 
> definitions exacly in this file - i wanna say, that it is a good idea to put 
> the comment into /etc/profile.env, that this file is genereting by using 
> /etc/env.d/* files, and the definitions of variables there.
> 

Nobody are stopping you from just adding what you need to the
bottom of /etc/profile ...


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] /etc/profile

[Zach Forrest]

I noticed some discussion in November about /etc/profile, but it seems
to have trailed off. Are there any objections to adding the following?

if [ -e "${HOME}/.bash_profile" ]; then
      . ${HOME}/.bash_profile
fi


- Zach

Re: [gentoo-dev] /etc/profile

[jano]

I thought ~/.bash_profile was read without needing to source it directly in
the /etc/profile; at least, that's the way it works for me.  I also make the
symbolic link, ~/.bashrc to the ~/.bash_profile, for su's and non
shell-login xterms *shrug*

jano


> I noticed some discussion in November about /etc/profile, but it seems
> to have trailed off. Are there any objections to adding the following?
>
> if [ -e "${HOME}/.bash_profile" ]; then
>      . ${HOME}/.bash_profile
> fi
>
>
> - Zach
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] /etc/profile

[Zach Forrest]

That was my understanding as well, but for some reason it doesn't do 
that for me so I've had to add it to /etc/profile. (Maybe I installed 
bash on the Wednesday before the last full moon between 5 and 6?)


Zach

jano wrote:

> I thought ~/.bash_profile was read without needing to source it directly in
> the /etc/profile; at least, that's the way it works for me.  I also make the
> symbolic link, ~/.bashrc to the ~/.bash_profile, for su's and non
> shell-login xterms *shrug*
> 
> jano
> 
> 
> 
>>I noticed some discussion in November about /etc/profile, but it seems
>>to have trailed off. Are there any objections to adding the following?
>>
>>if [ -e "${HOME}/.bash_profile" ]; then
>>     . ${HOME}/.bash_profile
>>fi
>>
>>
>>- Zach
>>
>>
>>_______________________________________________
>>gentoo-dev mailing list
>>gentoo-dev@gentoo.org
>>http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>>
> 
> 
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> 
> 

Re: [gentoo-dev] /etc/profile

[Juergen Ilse]

Hello,

On Sun, Dec 02, 2001 at 05:52:12PM -0800, Zach Forrest wrote:
> I noticed some discussion in November about /etc/profile, but it seems
> to have trailed off. Are there any objections to adding the following?
> 
> if [ -e "${HOME}/.bash_profile" ]; then
>       . ${HOME}/.bash_profile
> fi

I think, it is not a good idea ...
If you start bash as login-shell, it should parse ${[HOME}/.bash_profile
if that file exists, so there should be no need for such a hack. If you
insert "bash-specific" commands to this file, you may get error-messages,
if you use some other shell that reads /etc/profile (for example ash, sash
or ksh). Please don't do such things like inserting something like source
~/.bash_profile in /etc/profile. /etc/profile should not be bash-specific
in any way.

ciao,
	Juergen Ilse					(ilse@asys-h.de)
-- 
Wenn ich auch nur aus jedem 1000. Bug in einem M$ Produkt|Juergen Ilse
einen Tag trauern wollte, also da muesste ich 300 Jahre  |Internet POP Hannover
alt werden und wuerde mehrere Dutzend schwarze Anzuege   |Vahrenwalder Str. 205
aufbrauchen. (Detlef Bosau in dcoulm)                    |30165 Hannover

[gentoo-dev] /etc/profile

[Morgan Christiansson]

$PS1 var:

I think this should be the opposite, if the user isn't root let the user
know who they are.

And if they are root, give them the "supershell" without the user-name.


if [ `/usr/bin/whoami` == 'root' ] ; then
         export PS1='\[\033[01;32;40m\]\u@\h \[\033[01;34;40m\]\W 
 >\[\033[00m\]'
         export PATH=/sbin:/usr/sbin:$PATH
else
         export PS1='\[\033[01;34;40m\]\W > \[\033[00m\]'
         export PATH=$PATH
fi

----------------------------------------------------------------------

ls alias:

I think "alias ls='ls --color=auto'" should be in /etc/profile.

Most other distros have it and besides, it's a lot more readable.

I saw there were other aliases such as "alias d='ls --color'" but i've
never used them.

-- 
Morgan Christiansson