SISTEMA COLORIDO

cadu405
(usa Outra)

Enviado em 07/12/2020 - 15:22h

Boa tarde estou fazendo alguns exercícios no Linux e reparei que as vídeo aulas que estou assistindo o sistema nos vídeos é colorido porém o meu é tudo de uma única cor, gostaria de saber como deixo colorido , pois facilita na compreensão das informações.
segue as imagens

albfneto
(usa openSUSE)

Enviado em 07/12/2020 - 16:38h

O meu é colorido, porque eu uso Sabayon Linux, baseada no Gentoo e o Gentoo tem o terminal colorido.

Eu tive uma idéia.... teste isto:

1) primeiro COPIA seu arquivo de bash, para não estragar ele:

$ cd /

$ cd ~/

$ sudo cp .bashrc    .bashrc.copia    (Isso protege seu arquivo de bash)

 

2) agora procura se no seu Linux tem este arquivo:

$ sudo ls /etc/bash/bashrc   (é assim, bashrc sem ponto)

 

3) SE TIVER, posta as linhas dele aqui....

$ sudo cat /etc/bash/bashrc

 

4. SE NÃO TIVER, crie um e o edite:

# seu editor favorito, aberto como root... aqui chamo EDITOR:

# EDITOR /etc/bash/bashrc

 

E coloque dentro do arquivo estas linhas:

# /etc/bash/bashrc

#

# This file is sourced by all *interactive* bash shells on startup,

# including some apparently interactive shells such as scp and rcp

# that can't tolerate any output.  So make sure this doesn't display

# anything or bad things will happen !





# Test for an interactive shell.  There is no need to set anything

# past this point for scp and rcp, and it's important to refrain from

# outputting anything in those cases.

if [[ $- != *i* ]] ; then

	# Shell is non-interactive.  Be done now!

	return

fi



# Bash won't get SIGWINCH if another process is in the foreground.

# Enable checkwinsize so that bash will check the terminal size when

# it regains control.  #65623

# http://cnswww.cns.cwru.edu/~chet/bash/FAQ (E11)

shopt -s checkwinsize



# Disable completion when the input buffer is empty.  i.e. Hitting tab

# and waiting a long time for bash to expand all of $PATH.

shopt -s no_empty_cmd_completion



# Enable history appending instead of overwriting when exiting.  #139609

shopt -s histappend



# Save each command to the history file as it's executed.  #517342

# This does mean sessions get interleaved when reading later on, but this

# way the history is always up to date.  History is not synced across live

# sessions though; that is what `history -n` does.

# Disabled by default due to concerns related to system recovery when $HOME

# is under duress, or lives somewhere flaky (like NFS).  Constantly syncing

# the history will halt the shell prompt until it's finished.

#PROMPT_COMMAND='history -a'



# Change the window title of X terminals 

case ${TERM} in

	[aEkx]term*|rxvt*|gnome*|konsole*|interix)

		PS1='\[\033]0;\u@\h:\w\007\]'

		;;

	screen*)

		PS1='\[\033k\u@\h:\w\033\\\]'

		;;

	*)

		unset PS1

		;;

esac



# Set colorful PS1 only on colorful terminals.

# dircolors --print-database uses its own built-in database

# instead of using /etc/DIR_COLORS.  Try to use the external file

# first to take advantage of user additions.

# We run dircolors directly due to its changes in file syntax and

# terminal name patching.

use_color=false

if type -P dircolors >/dev/null ; then

	# Enable colors for ls, etc.  Prefer ~/.dir_colors #64489

	LS_COLORS=

	if [[ -f ~/.dir_colors ]] ; then

		eval "$(dircolors -b ~/.dir_colors)"

	elif [[ -f /etc/DIR_COLORS ]] ; then

		eval "$(dircolors -b /etc/DIR_COLORS)"

	else

		eval "$(dircolors -b)"

	fi

	# Note: We always evaluate the LS_COLORS setting even when it's the

	# default.  If it isn't set, then `ls` will only colorize by default

	# based on file attributes and ignore extensions (even the compiled

	# in defaults of dircolors). #583814

	if [[ -n ${LS_COLORS:+set} ]] ; then

		use_color=true

	else

		# Delete it if it's empty as it's useless in that case.

		unset LS_COLORS

	fi

else

	# Some systems (e.g. BSD & embedded) don't typically come with

	# dircolors so we need to hardcode some terminals in here.

	case ${TERM} in

	[aEkx]term*|rxvt*|gnome*|konsole*|screen|cons25|*color) use_color=true;;

	esac

fi



if ${use_color} ; then

	if [[ ${EUID} == 0 ]] ; then

		PS1+='\[\033[01;31m\]\h\[\033[01;34m\] \w \$\[\033[00m\] '

	else

		PS1+='\[\033[01;32m\]\u@\h\[\033[01;34m\] \w \$\[\033[00m\] '

	fi



	alias ls='ls --color=auto'

	alias grep='grep --colour=auto'

	alias egrep='egrep --colour=auto'

	alias fgrep='fgrep --colour=auto'

else

	# show root@ when we don't have colors

	PS1+='\u@\h \w \$ '

fi



for sh in /etc/bash/bashrc.d/* ; do

	[[ -r ${sh} ]] && source "${sh}"

done



# Try to keep environment pollution down, EPA loves us.

unset use_color sh

 

Salve e reinicie o seu micro e o linux e teste executar no terminal algo.... Se não funcionar me avise.

Resumo esse é o arquivo que deixa colorido o terminal das distros baseadas no Gentoo. talvez funcione em outros lInux:

https://gist.github.com/theironsamurai/a7c0e5a8e662bbca02cd
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Albfneto,
Ribeirão Preto, S.P., Brasil.
Usuário Linux, Linux Counter: #479903.
Distros Favoritas: Sabayon, Gentoo, openSUSE, Mageia e OpenMandriva.

albfneto
(usa openSUSE)

Enviado em 07/12/2020 - 16:42h

Veja este é um terminal em Sabayon, depois que ele executa um comando:



¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Albfneto,
Ribeirão Preto, S.P., Brasil.
Usuário Linux, Linux Counter: #479903.
Distros Favoritas: Sabayon, Gentoo, openSUSE, Mageia e OpenMandriva.

albfneto
(usa openSUSE)

Enviado em 07/12/2020 - 16:45h

agora, se quiser definir cores, mudar o prompt, etc.... Isso, tem muita coisa na net para postar links, faça uma busca sobre:

"Editar .bashrc"
"Editar variável PS1"
"Personalizar o terminal Linux"
"mudar as cores do terminal LInux e do Bash" etc...

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Albfneto,
Ribeirão Preto, S.P., Brasil.
Usuário Linux, Linux Counter: #479903.
Distros Favoritas: Sabayon, Gentoo, openSUSE, Mageia e OpenMandriva.

pam30
(usa Outra)

Enviado em 07/12/2020 - 18:19h

Esse editor de texto parece ser o VIM
e o arquivo /etc/fstab

Dentro do vim:

:syntax on 

albfneto
(usa openSUSE)

Enviado em 07/12/2020 - 18:30h

Não tem problema, qualquer editor de texto que ele tiver, vai funcionar como root.

o que ele precisa é editar o arquivo /etc/bash/bashrc

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Albfneto,
Ribeirão Preto, S.P., Brasil.
Usuário Linux, Linux Counter: #479903.
Distros Favoritas: Sabayon, Gentoo, openSUSE, Mageia e OpenMandriva.