Bash doesn't read the config files right under Gentoo

dizzyp

Hi,

I store all my dotfiles using CVS, and have a couple of
shell script to retrieve/update them on different (new) hosts...

I been using RH, Deb, etc + Solaris, and it works allright...

But Gentoo+Bash won't read my ~/.bash_profile & ~/.bashrc

(I suspect it doesn't read /etc/profile either)

(Alas, I have to type "source ~/.bash_profile" on each log on)

Another problem is that the normal bash(emacs) keymapping isn't
working properly; ctrl-a gives me just a control character.

Anyone who know how I can fix this?

Regards,

--dpr

Larde · Posted: Wed Nov 13, 2002 5:24 pm Post subject:

Are you sure that you shell actually is set to /bin/bash? useradd doesn't set a shell by default in gentoo. So check you /etc/passwd with vipw or just try chsh -s /bin/bash and relogin.

Hth,
Larde.
_________________
Someday this will be my home... http://moonage.net/
I'll make you a deal
I'll say I came from Earth and my tongue is taped

arkane · l33t Joined: 30 Apr 2002 Posts: 918 Location: Phoenix, AZ

I have the same problem, though I've only ran into needing to add things to my own personal preferences as of the last few weeks.
I've resorted to just sourcing the ~/.bash_profile.
Though, thats not a remedy.

cat /etc/passwd | grep -i arkane
gives this:
arkane:x:1000:100::/home/arkane:/bin/bash

I use bash for everything.

rac · Posted: Wed Nov 13, 2002 9:51 pm Post subject:

Can people with problems like this post their version of baselayout?
_________________
For every higher wall, there is a taller ladder

arkane · l33t Joined: 30 Apr 2002 Posts: 918 Location: Phoenix, AZ

I just updated to 1.8.4.2 and it went away.

dizzyp · Posted: Thu Nov 14, 2002 11:27 am Post subject: Hi, me again...

Of course the shell is set to /bin/bash :-)

Got an answer on #gentoo: rename it to ~/.profile,
something that works, but .bash_profile is more standard
name on other distributions/OSes.

Can I use emerge to upgrade the whole lot to the latest version
in an easy way?

--dpr

hook · Posted: Thu Nov 14, 2002 2:08 pm Post subject:

that's a bit of a turn-off

...this should really be repaired. i mean ~/.profile isn't a standard file for it ... have you reported it to gentoo's bugzilla? (p.s. is there a more direct way of reporting errors?)
_________________
tea+free software+law=hook

(deep inside i'm still a tux's little helper)

Larde · Posted: Thu Nov 14, 2002 2:33 pm Post subject:

hook · Posted: Fri Nov 15, 2002 9:48 am Post subject:

larde, you're right ...i forgot about that --silly me

but it's still a bit odd isn't it?
i really think this should be repaired
_________________
tea+free software+law=hook

(deep inside i'm still a tux's little helper)

Larde · Posted: Fri Nov 15, 2002 12:19 pm Post subject:

Hey, no need to feel silly. :-)

I got that .profile thing wrong before myself - I thought it was used only by sh or ksh.

AJM

puddpunk · l33t Joined: 20 Jul 2002 Posts: 681 Location: New Zealand

Type this:

dizzyp · Posted: Mon Nov 18, 2002 10:01 am Post subject: Hi again...

DamageCo · n00b Joined: 19 Nov 2002 Posts: 5

Are you login with a standard console or with gnome-terminal ?

Is the problem occur in both env ?

I had the same prb with gnome-teminal which was fixed by editing the current profile with the menu. Just set check "Run command as login check" .

Anyway, I have the same prb with the su command. su - user -c "env" never read the dotfiles, but su - user does ! Any explanation for me ?

Hope this help a little bit...

Bye

DamageCo

gnewbie · n00b Joined: 29 Nov 2002 Posts: 3

For all of you who gnome-terminal do not read /etc/profile file at startup, the solution is

1) open gnome-terminal
2) Click Edit>Current Profile>Title & Command
at the sectionWindow title, check box for 'run command as login'

I found the solution at the following post:
http://forums.gentoo.org/viewtopic.php?t=20517

Carles.

jukka · Posted: Fri Nov 29, 2002 6:42 pm Post subject:

a trick for bash users (using gnome or not) to avoid headaches from problems like those described above:

~/.bash_profile contains only one line:
Code:

[ -f ~/.bashrc ] && source ~/.bashrc
the first line of ~/.bashrc is:
Code:

[ -f /etc/profile ] && source /etc/profile
followed by your personal variables, aliases, functions, etc.
/etc/profile contains global settings (variables, aliases...)

when using a setup like this, you don't have to care whether you are starting a login shell or not:

if its a login shell, /etc/profiles is read first, ~/.bash_profile is read afterwards, ~/.bashrc is sourced from there, which sources /etc/profiles in turn (a little redundancy...).
if its not a login shell, ~/.bashrc is read, and /etc/profiles is sourced from there. because ~/.bash_profile is (almos) empty, you will end up with (almost) the same environment variables as after starting a login shell.

if you worry about files being sourced twice (e.g. if you declare readonly variables), add something like the following to the file you want to be sourced only once (like a #ifndef ... #define ... #endif for the cpp):