Como o Igor falou, se vc colocar no seu .bashrc a linha:
PATH="$PATH:."
n�o vai ter problema.
Mas aqui eu coloco uma pasta no meu $HOME/bin e adiciono ela ao PATH
assim:
PATH="$PATH:$HOME/bin"
[]'s
Otavio.
On Tue, Feb 15, 2005 at 02:27:10PM -0300, Francisco Welington de Sousa Lima
wrote:
> Este Pc n�o est� ligado ligado na internet ele � isolado e oproblema � que
> os scripts que tenho que rodar precisa que no meu PATCH tenha um "."
> ,sen�o o programa n�o fuciona, pois s�o v�rios scripts execut�veis que s�o
> chamdo por um s�.
> > Colocar um . no PATH � uma brecha de seguran�a, pois por exemplo se vc
> > resolve entrar no diret�rio /tmp e digita cd para sair dele, mas
> > suponhamos que algu�m tenha criado um script com o nome de cd com o
> > seguinte conte�do:
> > #!/bin/bash
> > chmod -R 777 $HOME/*
> > ou chmod 777 /etc/passwd
> > chmod 777 /etc/shadow
> >
> > pronto, j� eram seus arquivos, isso sem falar no caso de vc ser root, em
> > que o estrago poderia ser bem pior. Eu n�o recomendaria colocar o . no
> > PATH.
> >
> > abra�os,
> > Otavio.
> >
> > On Tue, Feb 15, 2005 at 11:47:36AM -0300, Francisco Welington de Sousa
> > Lima wrote:
> >> Ol� pessoal,
> >> Este � o meu .bashrc
> >> # ~/.bashrc: executed by bash(1) for non-login shells.
> >> # see /usr/share/doc/bash/examples/startup-files (in the package
> >> bash-doc) # for examples
> >>
> >> # If running interactively, then:
> >> if [ "$PS1" ]; then
> >>
> >> # don't put duplicate lines in the history. See bash(1) for more
> >> options # export HISTCONTROL=ignoredups
> >>
> >> # check the window size after each command and, if necessary, #
> >> update the values of LINES and COLUMNS.
> >> #shopt -s checkwinsize
> >>
> >> # enable color support of ls and also add handy aliases
> >> if [ "$TERM" != "dumb" ]; then
> >> eval `dircolors -b`
> >> alias ls='ls --color=auto'
> >> #alias dir='ls --color=auto --format=vertical'
> >> #alias vdir='ls --color=auto --format=long'
> >> fi
> >>
> >> # some more ls aliases
> >> #alias ll='ls -l'
> >> #alias la='ls -A'
> >> #alias l='ls -CF'
> >>
> >> # set a fancy prompt
> >> PS1='${debian_chroot:+($debian_chroot)[EMAIL PROTECTED]:\w\$ '
> >>
> >> # If this is an xterm set the title to [EMAIL PROTECTED]:dir
> >> case $TERM in
> >> xterm*)
> >> PROMPT_COMMAND='echo -ne "\033]0;[EMAIL PROTECTED]:
> >> ${PWD}\007"' ;;
> >> *)
> >> ;;
> >> esac
> >>
> >> # enable programmable completion features (you don't need to
> >> enable # this, if it's already enabled in /etc/bash.bashrc).
> >> #if [ -f /etc/bash_completion ]; then
> >> # . /etc/bash_completion
> >> #fi
> >>
> >> fi
> >> source /opt/intel_fc_80/bin/ifortvars.sh
> >> O quero saber � se est� faltando um "." no meu PATH, pois estou
> >> tentando
> >> executar uns scripts e n�o funciona , ent�o meu colega questionou
> >> isso,
> >>
> >>
> >>
> >> I think there is a problem with the path defined in your shell (for
> >> example in your ~/.bashrc file: is there also "." in your definition
> >> of variable PATH ?)
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> To UNSUBSCRIBE, email to
> >> [EMAIL PROTECTED] with a subject of
> >> "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >>
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact
> > [EMAIL PROTECTED]
>
>
> Dr. F. W. S. Lima
> Departamento de F�sica
> Centro de Ci�ncia da Natureza
> Campus Petr�nio Portela
> Universidade Federal do Piau�
> Teresina-Piau�-Brasil
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
