rbenv [RESOLVIDO]

1. rbenv [RESOLVIDO]

Hugo
hugooliveira

(usa Debian)

Enviado em 06/03/2016 - 11:58h

estou com um problema no terminal toda vez que logo como root aparece o seguinte aviso:

bash: rbenv: command not found


  


2. Re: rbenv [RESOLVIDO]

Alexandre (azk4n)
azk

(usa Arch Linux)

Enviado em 06/03/2016 - 14:55h

vc usa .bashrc personalizado?
se sim, algum comando o rbenv deve estar incluído nele e vc não possui tal pacote;

| » https://github.com/azk4n
| » https://twitter.com/azk4n
Playing with computers.



3. resposta

Hugo
hugooliveira

(usa Debian)

Enviado em 06/03/2016 - 15:22h

Não uso como ele veio no Debian Jessie

# ~/.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 not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
#[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'

#alias grep='grep --color=auto'
#alias fgrep='fgrep --color=auto'
#alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
#alias ll='ls -l'
#alias la='ls -A'
#alias l='ls -CF'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

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

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi



o que eu posso fazer nesse caso?


4. Re: rbenv [RESOLVIDO]

Alexandre (azk4n)
azk

(usa Arch Linux)

Enviado em 06/03/2016 - 18:50h

tente rodar isso:
$ echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
e teste!

| » https://github.com/azk4n
| » https://twitter.com/azk4n
Playing with computers.



5. rt

Hugo
hugooliveira

(usa Debian)

Enviado em 06/03/2016 - 23:03h

mesma coisa cara o comando rodou sem erro mais continua o problema


6. Re: rbenv [RESOLVIDO]

Alexandre (azk4n)
azk

(usa Arch Linux)

Enviado em 07/03/2016 - 02:57h

vc disse que isso acontece quando vc abre o terminal como root, certo?
então o certo é inserir o comando setando o diretório do root, não o seu, logo:
como root:
# echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> /root/.bashrc

| » https://github.com/azk4n
| » https://twitter.com/azk4n
Playing with computers.



7. Re: rbenv [RESOLVIDO]

Perfil removido
removido

(usa Nenhuma)

Enviado em 07/03/2016 - 03:46h

Eu andei olhando umas páginas: https://github.com/rbenv/rbenv/issues/670

----------------------------------------------------------------------------------------------------------------
http://24.media.tumblr.com/tumblr_m62bwpSi291qdlh1io1_250.gif

# apt-get purge systemd (não é prá digitar isso!)

Encryption works. Properly implemented strong crypto systems are one of the few things that you can rely on. Unfortunately, endpoint security is so terrifically weak that NSA can frequently find ways around it. — Edward Snowden







Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts