Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #172300 > unrolled thread

permanently add dir to $PATH

Back to article view | Back to linux.debian.user

Contents

  permanently add dir to $PATH Tony Baldwin <tonybaldwin@gmx.com> - 2016-09-16 16:10 +0200
    Re: permanently add dir to $PATH Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-16 16:10 +0200
      Re: permanently add dir to $PATH Liam O'Toole <liam.p.otoole@gmail.com> - 2016-09-16 19:50 +0200
    Re: permanently add dir to $PATH "der.hans" <deb-user@LuftHans.com> - 2016-09-16 16:30 +0200

#172300 — permanently add dir to $PATH

as mentioned, I'm working with a new Jessie installation and having a 
coupl headaches, the first had to do with getting a kernel module to 
load on boot (already wrote to the list about it.)

The other problem is trying to permanently add $HOME/bin to the $PATH.

I have in .bash_profile
PATH=$PATH:$HOME/bin
export PATH

But every time I boot I have to manually add it again.

Any and all assistance appreciated in advance.

Thanks.
LLAP
Tony


-- 
http://tonybaldwin.me
all tony, all the time

[toc] | [next] | [standalone]

#172301

On Fri, Sep 16, 2016 at 10:01:39AM -0400, Tony Baldwin wrote:
> The other problem is trying to permanently add $HOME/bin to the $PATH.
> 
> I have in .bash_profile
> PATH=$PATH:$HOME/bin
> export PATH
> 
> But every time I boot I have to manually add it again.

This is probably because you are logging in with a display manager
instead of ssh or a Linux console.  The display managers do not launch
a login shell, so your login shell configuration files are never read.

(This is why I never use a display manager.  Well, one of the reasons.)

You need to identify which display manager you're using, and then try
to figure out how to configure it as a user.  Good luck.  I've found
that most of them have absolutely ZERO documentation about this.

[toc] | [prev] | [next] | [standalone]

#172314

On 2016-09-16, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> On Fri, Sep 16, 2016 at 10:01:39AM -0400, Tony Baldwin wrote:
>> The other problem is trying to permanently add $HOME/bin to the $PATH.
>> 
>> I have in .bash_profile
>> PATH=$PATH:$HOME/bin
>> export PATH
>> 
>> But every time I boot I have to manually add it again.
>
> This is probably because you are logging in with a display manager
> instead of ssh or a Linux console.  The display managers do not launch
> a login shell, so your login shell configuration files are never read.
>
> (This is why I never use a display manager.  Well, one of the reasons.)
>
> You need to identify which display manager you're using, and then try
> to figure out how to configure it as a user.  Good luck.  I've found
> that most of them have absolutely ZERO documentation about this.
>
>

gdm sources the login scripts, whereas lightdm does not. In the latter
case, do the necessary PATH munging in ~/.xsessionrc.

-- 

Liam

[toc] | [prev] | [next] | [standalone]

#172305

[Multipart message — attachments visible in raw view] — view raw

Am 16. Sep, 2016 schwätzte Tony Baldwin so:

moin moin Tony,

> as mentioned, I'm working with a new Jessie installation and having a coupl 
> headaches, the first had to do with getting a kernel module to load on boot 
> (already wrote to the list about it.)
>
> The other problem is trying to permanently add $HOME/bin to the $PATH.
>
> I have in .bash_profile
> PATH=$PATH:$HOME/bin
> export PATH
>
> But every time I boot I have to manually add it again.

You have to add it to the file again?

/etc/skel/.profile includes $HOME/bin

$ tail -4 /etc/skel/.profile 
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
     PATH="$HOME/bin:$PATH"
fi
$

But, the top of the file lets us know it's not used if ~/.bash_profile
exists.

The bash manpage lists the purpose of ~/.bash_profile and ~/.bashrc.

        ~/.bash_profile
               The personal initialization file, executed for login shells
        ~/.bashrc
               The individual per-interactive-shell startup file

~/.bashrc gets read for all shells, including screen and tmux instances
and GUI logins that don't invoke login shells, so I put my changes
in ~/.bashrc rather than ~/.bash_profile. If I had interactive
configurations, then I would put those in ~/.bash_profile, everything else
goes in ~/.bashrc.

Actually, I put them in ~/.bashrc_local and include that from ~/.bashrc
so it's easier to keep my localizations synced across systems.

if [ -f ~/.bashrc_local ]; then
         . ~/.bashrc_local
fi

ciao,

der.hans
-- 
#  http://www.LuftHans.com/        http://www.PhxLinux.org/
#  "The world is a dangerous place to live, not because of the people who
#  are evil, but because of the people who don't do anything about it."
#    --Albert Einstein

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web