Re: .bashrc und .bash_profile werden unter Debian unstable nicht gelesen!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mittwoch, 28. April 2004 12:14, Andreas Schmidt wrote:
> On 2004.04.28 11:26, Wolfgang Balster wrote:
> > Hallo Liste,
> >
> > Ich will ~/bin in meinen Pfad bekommen und es geht ums Verrecken
> > nicht
> > ...
> > Weiß jemand Bescheid?
>
> Vielleicht hat es ja was hiermit zu tun?
Hat es! wenn ich innerhalb der bash-Shell erneut bash aufrufe, wird .bashrc
eingelesen und der Pfad sowie umask so geändert, wie ich das in der .bashrc
eingegeben hatte.
>
> "If bash is invoked with the name sh, it tries to mimic the startup
> behavior of historical versions of sh as closely as possible, while
> conforming to the POSIX standard as well. When invoked as an
> interactive login shell, or a non-interactive shell with the --login
> option,
wo findet das statt? Damit ich sh durch bash ersetzen kann... Newbie, kenne
mich da nicht gut aus.
> it first attempts to read and execute commands from /etc/
> profile and ~/.profile, in that order. The --noprofile option may be
> used to inhibit this behavior. When invoked as an interactive shell
> with the name sh, bash looks for the variable ENV, expands its value if
> it is defined, and uses the expanded value as the name of a file to
> read and execute. Since a shell invoked as sh does not attempt to read
> and execute commands from any other startup files, the --rcfile option
> has no effect. A non-interactive shell invoked with the name sh does
> not attempt to read any other startup files. When invoked as sh, bash
> enters posix mode after the startup files are read."
> (man bash)
>
> Schoenen Gruss,
>
> Andreas
- --
Mit freundlichem Gruss
Wolfgang
GPG 7FF6F4D4 | FAFD 8741 E703 31AC 5B1F AA45 B894 E07E 7FF6 F4D4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAj5pZuJTgfn/29NQRApiMAJ9lLX/yWU/J5/SvVT11weGQQfR38wCePl0h
cvSSxMwDX4H/VvSAVMaJJ00=
=nTcd
-----END PGP SIGNATURE-----
Reply to: