Difference between revisions of "Sistema Operacional Linux"

From VeRLab Wiki
Jump to: navigation, search
(Restaurar o .bashrc default no Ubuntu)
(Restaurar o .bashrc default no Ubuntu)
Line 31: Line 31:
 
<br>
 
<br>
 
referencias: [https://unix.stackexchange.com/questions/740146/how-can-i-restore-my-default-bashrc-file-again link1] [https://askubuntu.com/questions/404424/how-do-i-restore-bashrc-to-its-default link2]
 
referencias: [https://unix.stackexchange.com/questions/740146/how-can-i-restore-my-default-bashrc-file-again link1] [https://askubuntu.com/questions/404424/how-do-i-restore-bashrc-to-its-default link2]
 +
 +
 +
 +
{| class="wikitable"
 +
|-
 +
! Para comparar o conteúdo de /etc/skel.bashrc do ubuntu 22.04 foi colado abaixo:
 +
|-
 +
 +
<pre>
 +
# ~/.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|*-256color) 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 -alFh'
 +
alias la='ls -A'
 +
alias l='ls -CF'
 +
 +
# Add an "alert" alias for long running commands.  Use like so:
 +
#  sleep 10; alert
 +
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
 +
 +
# 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
 +
</pre>
 +
|}
 +
 +
 
<br><br>
 
<br><br>

Revision as of 08:49, 10 April 2025

As máquinas do Verlab/J utilizam em sua maioria o sistema operacional Ubuntu LTS que sempre são lançadas em anos pares: 2016, 2018, 2020, 2022...

Emm geral, usamos a mais madura e não a recém lançada do ano, por motivos de já terem corrigidos os bug de lançamento. Por exemplo, em 2022 usávamos o ubuntu 20.04 e não o ubuntu 22.04. Porém em 2023 começamos a migrar as máquinas para ubuntu 22..04.



Introdução ao Uso do Linux





Dicas sobre uso de TMux, Byobu, screen e etc



Restaurar o .bashrc default no Ubuntu

Talvez o usuário editou incorretamente o .bashrc ou corrompeu o mesmo, e precisa restaurar para a versão default que o ubuntu cria ao criar a home do usuário. O arquivo default fica armazenado em /etc/skel/.bashrc e pode ser usado para sobreescrever o arquivo corrompido na home:

cat /etc/skel/.bashrc > ~/.bashrc
ou
cp /etc/skel/.bashrc ~/
referencias: link1 link2


Para comparar o conteúdo de /etc/skel.bashrc do ubuntu 22.04 foi colado abaixo:
# ~/.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|*-256color) 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 -alFh'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# 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