Re: password et bashrc
Bernard Schoenacker a écrit : > Je recherche un moyen de pouvoir afficher un caractère par lettre ou > signe lorsque l'opérateur inscrit son mot de passe, cette solution est > employée sur Debian facile comme distro... Cf. script ci-dessous : https://stackoverflow.com/questions/1923435/how-do-i-echo-stars-when-reading-password-with-read Sébastien -- Sébastien Dinot, sebastien.di...@free.fr http://www.palabritudes.net/ Ne goutez pas au logiciel libre, vous ne pourriez plus vous en passer !
password et bashrc
Bonjour, Je recherche un moyen de pouvoir afficher un caractère par lettre ou signe lorsque l'opérateur inscrit son mot de passe, cette solution est employée sur Debian facile comme distro... Merci pour votre aimable attention Bien à vous Bernard
Re: bashrc problem
Thanks a lot @Will Mengarini On Wed, Jan 12, 2022 at 8:21 PM Will Mengarini wrote: > * Yamada??? [22-01/12=We 20:10 +0800]: > > Do you mean if .bash_profile exists, .bashrc will be ignored? > > Sometimes. From `man bash`: > When bash is invoked as an interactive login shell, or as a > non-interactive shell with the --login option, it first reads > and executes commands from the file /etc/profile, if that file > exists. After reading that file, it looks for ~/.bash_profile, > ~/.bash_login, and ~/.profile, in that order, and reads and > executes commands from the first one that exists and is readable. > [...] > When an interactive shell that is not a login shell > is started, bash reads and executes commands from > /etc/bash.bashrc and ~/.bashrc, if these files exist. > > * Yamada??? [22-01/12=We 19:49 +0800]: > >>> I have a .bashrc file in my home dir, whose content is shown as > follows. > >>> But every time I log into the system, I have to source this file by > hand. > >>> > >>> $ which scala > >>> /usr/bin/scala > >>> > >>> $ cat .bashrc > >>> #THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!! > >>> export SDKMAN_DIR="$HOME/.sdkman" > >>> [[ -s "$HOME/.sdkman/bin/sdkman-init.sh" ]] && source \ > >>> "$HOME/.sdkman/bin/sdkman-init.sh" > >>> > >>> $ . .bashrc > >>> $ which scala > >>> /home/xxx/.sdkman/candidates/scala/current/bin/scala > >>> > >>> How can I make it take effect automatically after I login the system? > > On Wed, Jan 12, 2022 at 8:07 PM Will Mengarini wrote: > >> > >> Check whether you have either ~/.bash_profile or ~/.profile. > >> > >> If ~/.bash_profile, the line > >> . ~/.bashrc > >> will suffice. > >> > >> If ~/.profile, use > >> # if running bash > >> if [ -n "$BASH_VERSION" ]; then > >> # include .bashrc if it exists > >> if [ -f ~/.bashrc ]; then > >> . ~/.bashrc > >> fi > >> fi > >> in case you someday want to try other shells. >
Re: bashrc problem
* Yamada??? [22-01/12=We 20:10 +0800]: > Do you mean if .bash_profile exists, .bashrc will be ignored? Sometimes. From `man bash`: When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. [...] When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. * Yamada??? [22-01/12=We 19:49 +0800]: >>> I have a .bashrc file in my home dir, whose content is shown as follows. >>> But every time I log into the system, I have to source this file by hand. >>> >>> $ which scala >>> /usr/bin/scala >>> >>> $ cat .bashrc >>> #THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!! >>> export SDKMAN_DIR="$HOME/.sdkman" >>> [[ -s "$HOME/.sdkman/bin/sdkman-init.sh" ]] && source \ >>> "$HOME/.sdkman/bin/sdkman-init.sh" >>> >>> $ . .bashrc >>> $ which scala >>> /home/xxx/.sdkman/candidates/scala/current/bin/scala >>> >>> How can I make it take effect automatically after I login the system? On Wed, Jan 12, 2022 at 8:07 PM Will Mengarini wrote: >> >> Check whether you have either ~/.bash_profile or ~/.profile. >> >> If ~/.bash_profile, the line >> . ~/.bashrc >> will suffice. >> >> If ~/.profile, use >> # if running bash >> if [ -n "$BASH_VERSION" ]; then >> # include .bashrc if it exists >> if [ -f ~/.bashrc ]; then >> . ~/.bashrc >> fi >> fi >> in case you someday want to try other shells.
Re: bashrc problem
* Yamada??? [22-01/12=We 19:49 +0800]: > I have a .bashrc file in my home dir, whose content is shown as follows. > But every time I log into the system, I have to source this file by hand. > > $ which scala > /usr/bin/scala > > $ cat .bashrc > #THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!! > export SDKMAN_DIR="$HOME/.sdkman" > [[ -s "$HOME/.sdkman/bin/sdkman-init.sh" ]] && source \ > "$HOME/.sdkman/bin/sdkman-init.sh" > > $ . .bashrc > $ which scala > /home/xxx/.sdkman/candidates/scala/current/bin/scala > > How can I make it take effect automatically after I login the system? Check whether you have either ~/.bash_profile or ~/.profile. If ~/.bash_profile, the line . ~/.bashrc will suffice. If ~/.profile, use # if running bash if [ -n "$BASH_VERSION" ]; then # include .bashrc if it exists if [ -f ~/.bashrc ]; then . ~/.bashrc fi fi in case you someday want to try other shells.
Re: bashrc problem
Do you mean if .bash_profile exists, .bashrc will be ignored? Thanks. On Wed, Jan 12, 2022 at 8:07 PM Will Mengarini wrote: > * Yamada??? [22-01/12=We 19:49 +0800]: > > I have a .bashrc file in my home dir, whose content is shown as follows. > > But every time I log into the system, I have to source this file by hand. > > > > $ which scala > > /usr/bin/scala > > > > $ cat .bashrc > > #THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!! > > export SDKMAN_DIR="$HOME/.sdkman" > > [[ -s "$HOME/.sdkman/bin/sdkman-init.sh" ]] && source \ > > "$HOME/.sdkman/bin/sdkman-init.sh" > > > > $ . .bashrc > > $ which scala > > /home/xxx/.sdkman/candidates/scala/current/bin/scala > > > > How can I make it take effect automatically after I login the system? > > Check whether you have either ~/.bash_profile or ~/.profile. > > If ~/.bash_profile, the line > . ~/.bashrc > will suffice. > > If ~/.profile, use > # if running bash > if [ -n "$BASH_VERSION" ]; then > # include .bashrc if it exists > if [ -f ~/.bashrc ]; then > . ~/.bashrc > fi > fi > in case you someday want to try other shells. >
bashrc problem
Hello list I have a .bashrc file in my home dir, whose content is shown as follows. But every time I log into the system, I have to source this file by hand. $ which scala /usr/bin/scala $ cat .bashrc #THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!! export SDKMAN_DIR="$HOME/.sdkman" [[ -s "$HOME/.sdkman/bin/sdkman-init.sh" ]] && source "$HOME/.sdkman/bin/sdkman-init.sh" $ . .bashrc $ which scala /home/xxx/.sdkman/candidates/scala/current/bin/scala How can I make it take effect automatically after I login the system? ありがとう Yamada
Re: Some Bash Alias Statements Work, Others Don't.The subject line tells it all!? Debian Stretch (64bit).,,Without warning, or any other indications, some of the alias statements in my user .bashrc ar
Thanks for the reply. There doesn't seem to be any such demarcation. On 10/29/2019 07:24 AM, Dan Purgert wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Stephen P. Molnar wrote: The subject line tells it all!? Debian Stretch (64bit). Without warning, or any other indications, some of the alias statements in my user .bashrc are no longer working!. The strange thing is that some still are working. Also, if I enter the complete path to an executable whose alias is NOT working, the executable works Reentering the alias statement in .bashrc does not restore the function. Going out on a limb here -- is there specific point in your alias list where things stop working (e.g. the 5th alias is OK, everything after stops), or is it that aliases 1,3,7,and 9 all work, but 2,4,5,6,8 are non-working? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAl24IXAACgkQjhHd8xJ5 ooEe4Qf+IrPAmTwjIm3Vd5kFJvLg1W2YR5spP3SJfaYqNip42MiYK+uHCDjWJhhb uV9giwL2mjAkdLHCjm49crTEO1UBJuoRyj+hfZ1+ZS2jDZtsz3pLocTNHRTko4/z 8mb1sW8ddI5xt9VdRow+5/FlPOkqd39HnicKXLCGQ7hO+/px9LQ7dGyyFhdcmd/h mAnCFfZKkOAOI2l3SCPE3bAnrJSgEg/+VLk1ZzOTvQ3Xu2bxdOO2qKT+gdJP7nr3 RW/PCS188GB9rV+mllKkEmzEymtvs3MjgLF0x+CTZY8zIpQZ8K9y6vxOsmH/czGe tMy2VsTDXN4LScu5x2/ahpqqqaQRvQ== =crfS -END PGP SIGNATURE- -- Stephen P. Molnar, Ph.D. www.molecular-modeling.net 614.312.7528 (c) Skype: smolnar1
Re: Some Bash Alias Statements Work, Others Don't.The subject line tells it all!? Debian Stretch (64bit).,,Without warning, or any other indications, some of the alias statements in my user .bashrc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Stephen P. Molnar wrote: > The subject line tells it all!? Debian Stretch (64bit). > > Without warning, or any other indications, some of the alias statements > in my user .bashrc are no longer working!. > > The strange thing is that some still are working. Also, if I enter the > complete path to an executable whose alias is NOT working, the > executable works Reentering the alias statement in .bashrc does not > restore the function. Going out on a limb here -- is there specific point in your alias list where things stop working (e.g. the 5th alias is OK, everything after stops), or is it that aliases 1,3,7,and 9 all work, but 2,4,5,6,8 are non-working? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAl24IXAACgkQjhHd8xJ5 ooEe4Qf+IrPAmTwjIm3Vd5kFJvLg1W2YR5spP3SJfaYqNip42MiYK+uHCDjWJhhb uV9giwL2mjAkdLHCjm49crTEO1UBJuoRyj+hfZ1+ZS2jDZtsz3pLocTNHRTko4/z 8mb1sW8ddI5xt9VdRow+5/FlPOkqd39HnicKXLCGQ7hO+/px9LQ7dGyyFhdcmd/h mAnCFfZKkOAOI2l3SCPE3bAnrJSgEg/+VLk1ZzOTvQ3Xu2bxdOO2qKT+gdJP7nr3 RW/PCS188GB9rV+mllKkEmzEymtvs3MjgLF0x+CTZY8zIpQZ8K9y6vxOsmH/czGe tMy2VsTDXN4LScu5x2/ahpqqqaQRvQ== =crfS -END PGP SIGNATURE- -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
Some Bash Alias Statements Work, Others Don't.The subject line tells it all!? Debian Stretch (64bit).,,Without warning, or any other indications, some of the alias statements in my user .bashrc are no
The subject line tells it all!? Debian Stretch (64bit). Without warning, or any other indications, some of the alias statements in my user .bashrc are no longer working!. The strange thing is that some still are working. Also, if I enter the complete path to an executable whose alias is NOT working, the executable works Reentering the alias statement in .bashrc does not restore the function. If I enter the alias statement in a terminal the alias works for that session of the terminal. The only thing that Google has yielded is when all of the alias statements stop working. This is inconvenient and very annoying. AS solution to the problem will be much appreciated. Thanks in advance. -- Stephen P. Molnar, Ph.D. www.molecular-modeling.net 614.312.7528 (c) Skype: smolnar1
Re: Strange .bashrc Problem
Thanks for the reply. Adding the lines from your .bash_profile to mine restored the functionality of .bashrc. I don't have any backups of .bash_profile, but I would guess the the HEX installation script woped out the origional .bash_profile. ( I try to never assume anything as we all know how that work can be parsed). An any rate, my thanks for the answers. The assistance that is so forthcoming is one of the things that makes Linux the OS of choice! On 04/25/2018 03:40 PM, Andy Smith wrote: Hello, On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote: Whie the additional lines are necessary for the execution of HEX they seem to have wiped oour all of the alias entries I have in .bashrc. Rebooting the system does not eliminate the problem! Bu bumbling about I discovered the it is necessary to source .bashrc inorder to recticate the alias lines in .bashrc (note: commenting out the added lines in .bash_profile did not solve the problem). My .bash_profile contains: # include .bashrc if it exists if [ -f ~/.bashrc ]; then . ~/.bashrc fi Does yours (still)? Maybe you could compare your ,bash_profile now to one from your recent backups. Cheers, Andy -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
Re: Strange .bashrc Problem
On Wed, Apr 25, 2018 at 10:49:52PM +0300, Abdullah Ramazanoglu wrote: > It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called > directly. That's not correct. As a LOGIN shell, bash reads ONE file, searching among the following items in sequence: a) ~/.bash_profile b) ~/.bash_login c) ~/.profile Whichever one it finds first, that's what it reads. If you also want it to read ~/.bashrc (you DO want this), then you must ensure that ~/.bashrc gets sourced/dotted from whatever file bash DOES read. > I gather that you had no ~/.bash_profile prior to installing HEX. That's my guess as well. > So I would suggest simply sourcing ~/.bashrc at the last line of > ~/.bash_profile If he has other stuff in ~/.profile then he may want to source ~/.profile instead. Then ~/.profile can source ~/.bashrc and everything should be back to normal.
Re: Strange .bashrc Problem
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote: > Bu bumbling about I discovered > the it is necessary to source .bashrc inorder to recticate the alias lines > in .bashrc (note: commenting out the added lines in .bash_profile did not > solve the problem). > > What's going on what is the fix? It is normal and expected that you must source (or dot in) ~/.bashrc from your ~/.bash_profile or ~/.profile. If this previously worked for you and then STOPPED working when you installed HEX, then two possible things come to mind: 1) Installing HEX somehow removed the ". ~/.bashrc" code from your profile. 2) Installing HEX created a ~/.bash_profile that previously did not exist. Before this, you were using ~/.profile which is what Debian creates in a default stretch install. #2 seems more likely to me. If that's the case, then perhaps what you want to do is source ~/.profile from your ~/.bash_profile. Or perhaps you would prefer to merge the two into a single file. A lot will depend on how you believe HEX will handle future upgrades. Will it search for its installed content in your ~/.bash_profile and blindly append its content to ~/.bash_profile if it doesn't see it? Even if the content is actually in ~/.profile instead?
Re: Strange .bashrc Problem
On Wed, 25 Apr 2018 15:34:02 -0400 Stephen P. Molnar said: > What's going on what is the fix? It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called directly. However, when ~/.bash_profile did exist, then it is called *instead of* ~/.bashrc and it is up to ~/.bash_profile to source ~/.bashrc or not. I gather that you had no ~/.bash_profile prior to installing HEX. So I would suggest simply sourcing ~/.bashrc at the last line of ~/.bash_profile Regards -- Abdullah Ramazanoglu
Re: Strange .bashrc Problem
Hello, On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote: > Whie the additional lines are necessary for the execution of HEX they seem > to have wiped oour all of the alias entries I have in .bashrc. Rebooting > the system does not eliminate the problem! Bu bumbling about I discovered > the it is necessary to source .bashrc inorder to recticate the alias lines > in .bashrc (note: commenting out the added lines in .bash_profile did not > solve the problem). My .bash_profile contains: # include .bashrc if it exists if [ -f ~/.bashrc ]; then . ~/.bashrc fi Does yours (still)? Maybe you could compare your ,bash_profile now to one from your recent backups. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Strange .bashrc Problem
I am running Debian Stretch on my 64-bit Linux platform. I have just
installed the molecular docking program HEX. The installation program
added the line shown below to .bash_profile:
#
# Lines added by 'hex_setup.bin' for Hex 8.0.0
#
export HEX_ROOT=/home/comp/Apps/Hex
export HEX_VERSION=8.0.0
export PATH=${PATH}:${HEX_ROOT}/bin
export HEX_CACHE=/home/comp/Apps/Hex/hex_cache
Whie the additional lines are necessary for the execution of HEX they
seem to have wiped oour all of the alias entries I have in .bashrc.
Rebooting the system does not eliminate the problem! Bu bumbling about
I discovered the it is necessary to source .bashrc inorder to recticate
the alias lines in .bashrc (note: commenting out the added lines in
.bash_profile did not solve the problem).
What's going on what is the fix?
Thanks in advance.
--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1
Re: Alias - Erreur pour recharger .bashrc
Le 28/08/2017 à 19:42, Étienne Mollier a écrit :
> G2PC, le 2017-08-28 :
>> Mon shell est zsh.
>>
>> [...]
>>
>> Recharger .bashrc avec la commande source ~/.bashrc
>>
>> J'ai une erreur avec mon .bashrc
>> source ~/.bashrc
>> /home/root/.bashrc:16: command not found: shopt
>> /home/root/.bashrc:24: command not found: shopt
>> /home/root/.bashrc:122: command not found: shopt
>> /usr/share/bash-completion/bash_completion:51: command not found: shopt
>> /usr/share/bash-completion/bash_completion:57: command not found: complete
>> /usr/share/bash-completion/bash_completion:62: command not found: complete
>> /usr/share/bash-completion/bash_completion:65: command not found: complete
>> /usr/share/bash-completion/bash_completion:68: command not found: complete
>> /usr/share/bash-completion/bash_completion:71: command not found: complete
>> /usr/share/bash-completion/bash_completion:74: command not found: complete
>> /usr/share/bash-completion/bash_completion:77: command not found: complete
>> /usr/share/bash-completion/bash_completion:80: command not found: complete
>> /usr/share/bash-completion/bash_completion:83: command not found: complete
>> /usr/share/bash-completion/bash_completion:86: command not found: complete
>> /usr/share/bash-completion/bash_completion:89: command not found: complete
>> /usr/share/bash-completion/bash_completion:92: command not found: complete
>> /usr/share/bash-completion/bash_completion:314: parse error near `\n'
>> \[\e]0;\u@\h
>> \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;31m\]\h\[\033[01;34m\] \W
>> \$\[\033[00m\]
> G2PC, le 2017-08-28, un peu plus tard :
>> Par contre, je ne sais pas si cette erreur de .bashrc est
>> normale et si je dois quand même la corrigée. Je part du
>> principe que, je n'ai pas à m'en occuper, puisque j'utilise
>> zsh.
> Bonsoir,
>
> Si ça peut vous rassurer, l'erreur est tout à fait normale en
> sourçant ce fichier ~/.bashrc avec le shell Zsh à la place de
> Bash. Vous n'avez à priori rien à corriger, à moins bien sûr que
> des bugs ne se soient cachés ailleurs dans le script. ;-)
Merci pour ta précision car c'était une question que je me suis posé. Je
m'étais dit aussi, que, c'est zsh qui interrogeait le bashrc et que cela
devait créer les erreurs.
J'ai peut être tout de même une erreur de syntaxe dans le bashrc, mais,
comme j'utilise zsh, je ne me pose pas plus de question, pour le moment,
concernant le fichier bashrc, qui doit déjà bien être documenté.
>
> La commande `shopt`, de l'erreur « command not found: shopt »,
> est une "builtin" : une commande intégrée et propre à Bash. Vous
> pouvez trouver sa description dans le manuel de `bash`, section
> "builtins", dont voici un extrait :
>
>> shopt: shopt [-pqsu] [-o] [optname ...]
>> Set and unset shell options.
> Cette commande n'existe pas en Zsh, d'où l'erreur.
>
>
> Si j'en crois la page de manuel de `zshbuiltins`, la commande à
> peu près équivalente serait `setopt` :
>
>> setopt [ {+|-}options | {+|-}o option_name ] [ -m ] [
>> name ... ]
>> Set the options for the shell. All options spec‐
>> ified either with flags or by name are set.
> La syntaxe diffère pas mal, ainsi que les options supportées,
> mais c'est l'intérêt de pouvoir choisir des shells différents.
>
> Même remarque pour la "builtin" `complete`, de l'erreur « command
> not found: complete », servant à définir les autocompletions via
> la touche Tab, elle est propre à Bash. Toujours dans la section
> "builtins" du manuel, vous trouverez plus de détails à son sujet.
>
> L'équivalent en Zsh est... décrit dans trois pages de manuel :
> - zshcompwid
> - zshcompsys
> - zshcompctl
>
> Ça donne une assez bonne idée de la granularité avec laquelle on
> peut configurer son shell en Zsh. :-)
>
> À plus,
Encore merci pour le complément d'information et les mots clé pour
accéder au manuel.
a + Bonne soirée.
Re: Alias - Erreur pour recharger .bashrc
G2PC, le 2017-08-28 :
> Mon shell est zsh.
>
> [...]
>
> Recharger .bashrc avec la commande source ~/.bashrc
>
> J'ai une erreur avec mon .bashrc
> source ~/.bashrc
> /home/root/.bashrc:16: command not found: shopt
> /home/root/.bashrc:24: command not found: shopt
> /home/root/.bashrc:122: command not found: shopt
> /usr/share/bash-completion/bash_completion:51: command not found: shopt
> /usr/share/bash-completion/bash_completion:57: command not found: complete
> /usr/share/bash-completion/bash_completion:62: command not found: complete
> /usr/share/bash-completion/bash_completion:65: command not found: complete
> /usr/share/bash-completion/bash_completion:68: command not found: complete
> /usr/share/bash-completion/bash_completion:71: command not found: complete
> /usr/share/bash-completion/bash_completion:74: command not found: complete
> /usr/share/bash-completion/bash_completion:77: command not found: complete
> /usr/share/bash-completion/bash_completion:80: command not found: complete
> /usr/share/bash-completion/bash_completion:83: command not found: complete
> /usr/share/bash-completion/bash_completion:86: command not found: complete
> /usr/share/bash-completion/bash_completion:89: command not found: complete
> /usr/share/bash-completion/bash_completion:92: command not found: complete
> /usr/share/bash-completion/bash_completion:314: parse error near `\n'
> \[\e]0;\u@\h
> \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;31m\]\h\[\033[01;34m\] \W
> \$\[\033[00m\]
G2PC, le 2017-08-28, un peu plus tard :
> Par contre, je ne sais pas si cette erreur de .bashrc est
> normale et si je dois quand même la corrigée. Je part du
> principe que, je n'ai pas à m'en occuper, puisque j'utilise
> zsh.
Bonsoir,
Si ça peut vous rassurer, l'erreur est tout à fait normale en
sourçant ce fichier ~/.bashrc avec le shell Zsh à la place de
Bash. Vous n'avez à priori rien à corriger, à moins bien sûr que
des bugs ne se soient cachés ailleurs dans le script. ;-)
La commande `shopt`, de l'erreur « command not found: shopt »,
est une "builtin" : une commande intégrée et propre à Bash. Vous
pouvez trouver sa description dans le manuel de `bash`, section
"builtins", dont voici un extrait :
> shopt: shopt [-pqsu] [-o] [optname ...]
> Set and unset shell options.
Cette commande n'existe pas en Zsh, d'où l'erreur.
Si j'en crois la page de manuel de `zshbuiltins`, la commande à
peu près équivalente serait `setopt` :
> setopt [ {+|-}options | {+|-}o option_name ] [ -m ] [
> name ... ]
> Set the options for the shell. All options spec‐
> ified either with flags or by name are set.
La syntaxe diffère pas mal, ainsi que les options supportées,
mais c'est l'intérêt de pouvoir choisir des shells différents.
Même remarque pour la "builtin" `complete`, de l'erreur « command
not found: complete », servant à définir les autocompletions via
la touche Tab, elle est propre à Bash. Toujours dans la section
"builtins" du manuel, vous trouverez plus de détails à son sujet.
L'équivalent en Zsh est... décrit dans trois pages de manuel :
- zshcompwid
- zshcompsys
- zshcompctl
Ça donne une assez bonne idée de la granularité avec laquelle on
peut configurer son shell en Zsh. :-)
À plus,
--
Étienne Mollier <etienne.moll...@mailoo.org>
Re: Alias - Erreur pour recharger .bashrc
Le 28/08/2017 à 15:14, Francois Lafont a écrit : > Bonjour, > > On 08/28/2017 03:02 PM, G2PC wrote: > >> Pouvez vous m'aider pour .bashrc ? J'ai ajouté des alias, mais, >> je n'arrive pas à recharger le .bashrc Mon shell est zsh. > Sauf erreur, le .bashrc, comme son nom l'indique, c'est pour > shell bash. Si tu utilises zsh, alors il doit y avoir sans > doute un autre fichier de conf, j'imagine que ça doit se > trouver dans le man (ne connaissant pas vraiment zsh, je ne > me risque pas à t'en dire plus). > > À+ Merci de ta réponse rapide. Effectivement, j'ai posté un peu vite, car, je ne me sentais pas forcément à l'aise, avec le bashrc et le zsh mais, j'ai trouvé la réponse plus rapidement que prévu : Noter que le shell par défaut de Debian s'appelle bash, mais qu'il en existe d'autres, selon les usages (zsh, csh, ...), pour lesquels le fonctionnement est légèrement différent. Attention ! J'utilise zsh, et, zsh utilise ~/.zshrc et non pas ~/.bashrc. Enlever les alias ajoutés dans .bashrc puisqu'il ne recharge pas, et, ajouter les alias dans .zshrc Recharger .zshrc avec la commande |source ~/.zshrc| Les alias sont maintenant fonctionnels. Par contre, je ne sais pas si cette erreur de .bashrc est normale et si je dois quand même la corrigée. Je part du principe que, je n'ai pas à m'en occuper, puisque j'utilise zsh. Source : https://www.visionduweb.eu/wiki/index.php?title=Utiliser_des_commandes_shell_avec_le_terminal#Exemples_pour_des_alias_avec_apt-get [Résolu]
Re: Alias - Erreur pour recharger .bashrc
Bonjour, On 08/28/2017 03:02 PM, G2PC wrote: > Pouvez vous m'aider pour .bashrc ? J'ai ajouté des alias, mais, > je n'arrive pas à recharger le .bashrc Mon shell est zsh. Sauf erreur, le .bashrc, comme son nom l'indique, c'est pour shell bash. Si tu utilises zsh, alors il doit y avoir sans doute un autre fichier de conf, j'imagine que ça doit se trouver dans le man (ne connaissant pas vraiment zsh, je ne me risque pas à t'en dire plus). À+ -- François Lafont
Alias - Erreur pour recharger .bashrc
Bonjour, Pouvez vous m'aider pour .bashrc ? J'ai ajouté des alias, mais,
je n'arrive pas à recharger le .bashrc Mon shell est zsh. Exemples pour
des alias avec apt-get
alias search='apt-cache search'
alias show='apt-cache show'
alias install='sudo apt-get install'
alias remove='sudo apt-get remove'
alias update='sudo apt-get update'
alias upgrade='sudo apt-get upgrade'
Utiliser ensuite la commande update && upgrade pour lancer une mise à jour.
Recharger .bashrc avec la commande |source ~/.bashrc|
J'ai une erreur avec mon .bashrc
source ~/.bashrc
/home/root/.bashrc:16: command not found: shopt
/home/root/.bashrc:24: command not found: shopt
/home/root/.bashrc:122: command not found: shopt
/usr/share/bash-completion/bash_completion:51: command not found: shopt
/usr/share/bash-completion/bash_completion:57: command not found: complete
/usr/share/bash-completion/bash_completion:62: command not found: complete
/usr/share/bash-completion/bash_completion:65: command not found: complete
/usr/share/bash-completion/bash_completion:68: command not found: complete
/usr/share/bash-completion/bash_completion:71: command not found: complete
/usr/share/bash-completion/bash_completion:74: command not found: complete
/usr/share/bash-completion/bash_completion:77: command not found: complete
/usr/share/bash-completion/bash_completion:80: command not found: complete
/usr/share/bash-completion/bash_completion:83: command not found: complete
/usr/share/bash-completion/bash_completion:86: command not found: complete
/usr/share/bash-completion/bash_completion:89: command not found: complete
/usr/share/bash-completion/bash_completion:92: command not found: complete
/usr/share/bash-completion/bash_completion:314: parse error near `\n'
\[\e]0;\u@\h
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;31m\]\h\[\033[01;34m\] \W
\$\[\033[00m\]
Source :
https://www.visionduweb.eu/wiki/index.php?title=Utiliser_des_commandes_shell_avec_le_terminal#Exemples_pour_des_alias_avec_apt-get
Re: /etc/bash.bashrc instead ~/.bashrc
Hello José, José Luis Segura Lucas josel.seg...@gmx.es wrote: In one (and only one) of then, when I open a terminal or connect by SSH, my bash load the default system configuration from /etc/bash.bashrc, instead of reading, as usual, ~/.bashrc. I can think that I don't really have a ~/.bashrc (or have a mispelling on the file name), but if I run bash from the terminal, my configuration file in ~/.bashrc is loaded. From man bash: When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior. When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. I guess that the SSH connect is a login shell, while the terminal is not a login shell (especially if you run it manually). Hence, if you connect with SSH, Bash will run /etc/profile and ~/.profile. My ~/.profile has a section like the following: # if running bash if [ -n $BASH_VERSION ]; then # include .bashrc if it exists if [ -f $HOME/.bashrc ]; then . $HOME/.bashrc fi fi which is also in the .profile in /etc/skel/, I therefore assume that this is currently shipped with Debian. I suggest you check whether these files (/etc/profile, ~/.profile, ~/.bash_profile) exist and whether they load ~/.bashrc. Best regards, Claudius -- Cat, n.: Lapwarmer with built-in buzzer. http://chubig.net telnet nightfall.org 4242 signature.asc Description: PGP signature
Re: /etc/bash.bashrc instead ~/.bashrc
Hello Claudius El 23/06/12 11:42, Claudius Hubig escribió: I guess that the SSH connect is a login shell, while the terminal is not a login shell (especially if you run it manually). Hence, if you connect with SSH, Bash will run /etc/profile and ~/.profile. My ~/.profile has a section like the following: # if running bash if [ -n $BASH_VERSION ]; then # include .bashrc if it exists if [ -f $HOME/.bashrc ]; then . $HOME/.bashrc fi fi which is also in the .profile in /etc/skel/, I therefore assume that this is currently shipped with Debian. I suggest you check whether these files (/etc/profile, ~/.profile, ~/.bash_profile) exist and whether they load ~/.bashrc. Best regards, Claudius You are right: I have the ~/.profile file missing. I don't know how can I miss this file, but it didn't exist at all. I copied this from another computer and it works. I don't remember to write or generate by hand this ~/.profile. Is it created automatically? Thanks for your answer, it was driving me crazy :D Best regards signature.asc Description: OpenPGP digital signature
Re: /etc/bash.bashrc instead ~/.bashrc
On Sat, Jun 23, 2012 at 05:24:59PM +0200, José Luis Segura Lucas wrote: You are right: I have the ~/.profile file missing. I don't know how can I miss this file, but it didn't exist at all. I copied this from another computer and it works. tal% less .profile # ~/.profile: executed by the command interpreter for login shells. # This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login # exists. # see /usr/share/doc/bash/examples/startup-files for examples. # the files are located in the bash-doc package. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120623164932.GB14371@tal
Re: /etc/bash.bashrc instead ~/.bashrc
Hello José, José Luis Segura Lucas josel.seg...@gmx.es wrote: I don't remember to write or generate by hand this ~/.profile. Is it created automatically? It should be created automatically from the files in /etc/skel/ if you are using useradd or adduser (the former with the --create-home option). Best regards, Claudius -- Monday is an awful way to spend one seventh of your life. http://chubig.net telnet nightfall.org 4242 signature.asc Description: PGP signature
/etc/bash.bashrc instead ~/.bashrc
Hi all! I have several computers with Debian installed. In all of them I have unstable with, in some cases, some experimental packages. In one (and only one) of then, when I open a terminal or connect by SSH, my bash load the default system configuration from /etc/bash.bashrc, instead of reading, as usual, ~/.bashrc. I can think that I don't really have a ~/.bashrc (or have a mispelling on the file name), but if I run bash from the terminal, my configuration file in ~/.bashrc is loaded. I add an echo on each files before sending you my problem to check that the problem is the configuration file and not only a possible misconfiguration on my ~/.bashrc file. I tried with different users and all of them loads the same configuration file (/etc/bash.bashrc). I didn't found any difference between this /etc/bash.bashrc and my other /etc/bash.bashrc in my other Debian installations... Is there any other place where bash is configured and tell it to load one config file or another? I don't know what to do to fix this problem... any help will be very appreciated. Thanks in advance signature.asc Description: OpenPGP digital signature
bashrc, bash_profile, /etc/skel/ - Debian Squeeze
Hi, I was tried Gentoo Linux system but after a while I come back to Debian GNU/Linux system again on my PC Box. So, in my /home/csanyipal/ directory there remain some dot files from Gentoo system, eg.: .bashrc, .bash_profile. When I installed 64bit Debian GNU/Linux Squeeze, I used my $HOME directory with it's dot files too. So, I think the .bashrc and .bash_profile remain in the state in which was on Gentoo. Now I have the empty /etc/skel/ directory! I try to reinstall bash, but still get not in my $HOME directory the debianized .bashrc and .bash_profile, and still the /etc/skel/ directory is empty. What should I reinstall to get the default /etc/skel/ directory? When 'ls' on my bash prompt, I get not colorized output too. How can I get the default BASH shell, with default .bashrc and .bash_profile again, and why is the /etc/skel/ directory empty? Any advices will be appreciated! -- Regards, Paul Chany You can freely correct me in my English. http://csanyi-pal.info -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877hizuvej@debian-asztal.excito
Re: bashrc, bash_profile, /etc/skel/ - Debian Squeeze
¡Warning: bad english here! I guess the /etc/skel debian directory isn't actually empty: try ls --all /etc/skel You've to restore your fancy-console-files from a previous backup or browsing in gentoo svn to find the files (maybe some base-files or something) On Mon, Sep 6, 2010 at 10:29, Csanyi Pal csanyi...@gmail.com wrote: Hi, I was tried Gentoo Linux system but after a while I come back to Debian GNU/Linux system again on my PC Box. So, in my /home/csanyipal/ directory there remain some dot files from Gentoo system, eg.: .bashrc, .bash_profile. When I installed 64bit Debian GNU/Linux Squeeze, I used my $HOME directory with it's dot files too. So, I think the .bashrc and .bash_profile remain in the state in which was on Gentoo. Now I have the empty /etc/skel/ directory! I try to reinstall bash, but still get not in my $HOME directory the debianized .bashrc and .bash_profile, and still the /etc/skel/ directory is empty. What should I reinstall to get the default /etc/skel/ directory? When 'ls' on my bash prompt, I get not colorized output too. How can I get the default BASH shell, with default .bashrc and .bash_profile again, and why is the /etc/skel/ directory empty? Any advices will be appreciated! -- Regards, Paul Chany You can freely correct me in my English. http://csanyi-pal.info -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877hizuvej@debian-asztal.excito
Re: bashrc, bash_profile, /etc/skel/ - Debian Squeeze
Csanyi Pal: When I installed 64bit Debian GNU/Linux Squeeze, I used my $HOME directory with it's dot files too. So, I think the .bashrc and .bash_profile remain in the state in which was on Gentoo. Yes, that's how it should be. Debian package managers must never touch anything under /home. Now I have the empty /etc/skel/ directory! Check with ls -la. I try to reinstall bash, but still get not in my $HOME directory the debianized .bashrc and .bash_profile, This is by design. Debian never overwrites user files. and still the /etc/skel/ directory is empty. What should I reinstall to get the default /etc/skel/ directory? What do you need that for? It is only used when you create new users. J. -- Driving behind lorries carrying hazardous chemicals makes me wish for a simpler life. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: bashrc, bash_profile, /etc/skel/ - Debian Squeeze
Pier Paolo pierpaolo.fra...@gmail.com writes: I guess the /etc/skel debian directory isn't actually empty: try ls --all /etc/skel Uh, yes, of course!! You've to restore your fancy-console-files from a previous backup or browsing in gentoo svn to find the files (maybe some base-files or something) After I copy .bashrc and .profile to my $HOME directory, and setup owner for these files to be owned by user: by me, everything back to the normal. Thanks! OK, I edited these files and add some lines there, like: EDITOR=emacsclient; export EDITOR -- Regards, Paul Chany http://www.debian.org http://wiki.debian.org/DebianEdu http://csanyi-pal.info -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87eid7dvhc@debian-asztal.excito
Re: GDM não carrega meu .bashrc
2010/8/16 Ronaldo Reis Junior chrys...@gmail.com Pessoal, estou usando o debian testing/unstable. Tem alguns comandos que preciso que rode assim que faço o login em meu ambiente (icewm ou kde) mas o GDM não está rodando o meu .bashrc. Assim sempre que logo tenho que abrir o xterm para que ele rode o .bashrc e com isto defina algumas variáveis. Como faço para corrigir isto? Eu já ouvi alguém falar num tal de '.gnomerc'. Já testou isso ? [ ]s Valeu Inte Ronaldo -- 5ª lei - Se você acha que está certo e é capaz de convencer o seu orientador, ele será muito feliz. --Herman, I. P. 2007. Following the law. NATURE, Vol 445, p. 228. Prof. Ronaldo Reis Júnior | .''`. UNIMONTES/DBG/Lab. Ecologia Comportamental e Computacional | : :' : Campus Universitário Prof. Darcy Ribeiro, Vila Mauricéia | `. `'` CP: 126, CEP: 39401-089, Montes Claros - MG - Brasil | `- Fone: (38) 3229-8192 | ronaldo.r...@unimontes.br | http://www.ppgcb.unimontes.br/lecc | LinuxUser#: 205366 -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c695bd0.30...@gmail.com -- Robson Roberto Souza Peixoto Robinho robsonpeix...@gmail.com Telefones: (19) 8821-0396 (oi) (19) 9799-0135 (vivo) Computer Science Master's degree student, University of Campinas Linux Counter #395633 IRC: robsonpeixoto Twitter: http://twitter.com/rrspba
Re: GDM não carrega meu .bashrc
On Wed, 18 Aug 2010 06:53:32 -0300 Robson Peixoto robsonpeix...@gmail.com wrote: 2010/8/16 Ronaldo Reis Junior chrys...@gmail.com Pessoal, estou usando o debian testing/unstable. Tem alguns comandos que preciso que rode assim que faço o login em meu ambiente (icewm ou kde) mas o GDM não está rodando o meu .bashrc. Assim sempre que logo tenho que abrir o xterm para que ele rode o .bashrc e com isto defina algumas variáveis. Como faço para corrigir isto? Eu já ouvi alguém falar num tal de '.gnomerc'. Já testou isso ? Uso o '.xsessionrc'. Não sei se é o recomendado, mas funciona... []'s -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100818144707.1c081...@yeh1.parsec
Re: GDM não carrega meu .bashrc
Quando vc loga no KDE, eh executado um shell de login, ou não-interativo. Nesse momento, o GDM (ou KDE?) procura por um arquivo de perfil para ler (.profile ou .bash_profile -- este último tem precedência sobre o .profile). Ou seja, provavelmente vc quer utilizar o arquivo .bash_profile, se o shell padrão é o bash. Acho que dá pra fazer alguma coisa ou no .xinitrc ou no .xsession. []´s Helio Loureiro http://helio.loureiro.eng.br http://hloureiro.multiply.com http://twitter.com/helioloureiro
Re: GDM não carrega meu .bashrc
Use este arquivo aqui: /etc/gdm/PostLogin/Default como já foi falado vc só usa o .bashrc quando executa um console/terminal. Em 16 de agosto de 2010 12:40, Ronaldo Reis Junior chrys...@gmail.comescreveu: Pessoal, estou usando o debian testing/unstable. Tem alguns comandos que preciso que rode assim que faço o login em meu ambiente (icewm ou kde) mas o GDM não está rodando o meu .bashrc. Assim sempre que logo tenho que abrir o xterm para que ele rode o .bashrc e com isto defina algumas variáveis. Como faço para corrigir isto? Valeu Inte Ronaldo -- 5ª lei - Se você acha que está certo e é capaz de convencer o seu orientador, ele será muito feliz. --Herman, I. P. 2007. Following the law. NATURE, Vol 445, p. 228. Prof. Ronaldo Reis Júnior | .''`. UNIMONTES/DBG/Lab. Ecologia Comportamental e Computacional | : :' : Campus Universitário Prof. Darcy Ribeiro, Vila Mauricéia | `. `'` CP: 126, CEP: 39401-089, Montes Claros - MG - Brasil | `- Fone: (38) 3229-8192 | ronaldo.r...@unimontes.br | http://www.ppgcb.unimontes.br/lecc | LinuxUser#: 205366 -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c695bd0.30...@gmail.com
GDM não carrega meu .bashrc
Pessoal, estou usando o debian testing/unstable. Tem alguns comandos que preciso que rode assim que faço o login em meu ambiente (icewm ou kde) mas o GDM não está rodando o meu .bashrc. Assim sempre que logo tenho que abrir o xterm para que ele rode o .bashrc e com isto defina algumas variáveis. Como faço para corrigir isto? Valeu Inte Ronaldo -- 5ª lei - Se você acha que está certo e é capaz de convencer o seu orientador, ele será muito feliz. --Herman, I. P. 2007. Following the law. NATURE, Vol 445, p. 228. Prof. Ronaldo Reis Júnior | .''`. UNIMONTES/DBG/Lab. Ecologia Comportamental e Computacional | : :' : Campus Universitário Prof. Darcy Ribeiro, Vila Mauricéia | `. `'` CP: 126, CEP: 39401-089, Montes Claros - MG - Brasil | `- Fone: (38) 3229-8192 | ronaldo.r...@unimontes.br | http://www.ppgcb.unimontes.br/lecc | LinuxUser#: 205366 -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c695bd0.30...@gmail.com
Re: GDM não carrega meu .bashrc
2010/8/16 Ronaldo Reis Junior chrys...@gmail.com estou usando o debian testing/unstable. Tem alguns comandos que preciso que rode assim que faço o login em meu ambiente (icewm ou kde) mas o GDM não está rodando o meu .bashrc. Assim sempre que logo tenho que abrir o xterm para que ele rode o .bashrc e com isto defina algumas variáveis. Esse eh o comportamento esperado. O .bashrc é lido toda vez que se abre um shell interativo. Por exemplo, quando vc abre o xterm. Quando vc loga no KDE, eh executado um shell de login, ou não-interativo. Nesse momento, o GDM (ou KDE?) procura por um arquivo de perfil para ler (.profile ou .bash_profile -- este último tem precedência sobre o .profile). Ou seja, provavelmente vc quer utilizar o arquivo .bash_profile, se o shell padrão é o bash. Atenciosamente, -- João Olavo Baião de Vasconcelos Analista de Sistemas - Infraestrutura joaoolavo.wordpress.com
résultat bizarre de 'find ... -path ... -prune ...' dans une fonction dans .bashrc
Bonsoir,
Je poste dans cette liste parce que j'utilisais cette fonction sous
FreeBSD+tcsh et qu'après recherches, je ne comprends pas ce qui se passe
sous debian+bash
J'utilise une fonction dans '.bashrc' basée sur 'find' et utilisant le
paramètre '-prune' pour simplifier des recherches en excluant un
répertoire (/mnt ou /media en tête).
Or l'exclusion du répertoire ne fonctionne pas lorsqu'on utilise la
fonction alors que cela fonctionne en lançant directement 'find' en
reprenant strictement la syntaxe utilisée dans la fonction (grâce à la
sortie de 'echo $EXEC'
function fprune {
INFO=recherche [ $3 ] dans le repertoire [ $1 ] en excluant le
repertoire [ $2 ]
EXEC=find $1 -path '$2' -type d -prune -o -name $3 -type f -print
echo $INFO
echo $EXEC
$EXEC
}
Par exemple : pour rechercher les fichiers nommés 'smart' dans le
répertoire '/etc' en excluant le répertoire '/etc/default'
(après un 'su' pour être sûr que ce n'est pas un problème de droits)
* en utilisant la fonction, le répertoire '/etc/default' est parcouru:
# fprune /etc /etc/default smart*
recherche [ smart* ] dans le repertoire [ /etc/ ] en excluant le
repertoire [ /etc/default ]
find /etc -path '/etc/default' -type d -prune -o -name smart* -type f
-print
/etc/init.d/smartmontools
/etc/smartd.conf
/etc/default/smartmontools
* en utilisant find directement, le répertoire '/etc/default' est bien
exclu :
# find /etc -path '/etc/default' -type d -prune -o -name smart* -type f
-print
/etc/init.d/smartmontools
/etc/smartd.conf
quelq'un aurait-il une piste ou faut-il que je poste dans une liste
orientée 'scripts' ?
merci d'avance
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/DebFrFrenchLists
Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et
Reply-To:
To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Which files do what: .bashrc and friends
Boyd Stephen Smith Jr. wrote: On Wednesday 19 November 2008, tyler [EMAIL PROTECTED] wrote about 'Re: Which files do what: .bashrc and friends': I believe .profile and .bash_profile are synonyms, so you'd only use one or the other. .profile is only used by bash when it cannot find .bash_profile. .profile is also used by the traditional Bourne shell and Korn shell and is the standard location of such commands. Yes, this is what I also prefer. If using .bash_profile i.e. when specific things related to bash only are setup, I take care to check if .profile is sourced and if not source it out. For konsole I setup alias with konsole -ls regards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Which files do what: .bashrc and friends
On a Debian-based system running KDE 3.5.10 I see several files that are used when logging in / starting a Konsole: .profile .bash_history .bash_logout .bash_profile .bashrc I imagine three times these files might be used: 1) When logging in 2) When starting Konsole 3) When running a shell script via Konqeror In which of the files should I put commands that I want to run at each of these events? For instance, if I want a certain command to be run when I log in, should that be in .bashrc, .profile, .bash_profile, or elsewhere? If I want a command to be run when I open Konsole, where would that go? How about a command that I want run before every script that I run from my file manager (an example of such a use would be a local export)? Thanks in advance. If there are any good docs that explain this, I'd love to see them. I have not been able to google anything recent that is relevant to Debian. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я ä-ö-ü-ß-Ä-Ö-Ü
Re: Which files do what: .bashrc and friends
Dotan Cohen [EMAIL PROTECTED] writes: On a Debian-based system running KDE 3.5.10 I see several files that are used when logging in / starting a Konsole: .profile .bash_history .bash_logout .bash_profile .bashrc Thanks in advance. If there are any good docs that explain this, I'd love to see them. I have not been able to google anything recent that is relevant to Debian. man bash answers most of your questions: FILES /bin/bash The bash executable /etc/profile The systemwide initialization file, executed for login shells /etc/bash.bashrc The systemwide per-interactive-shell startup file /etc/bash.logout The systemwide login shell cleanup file, executed when a login shell exits ~/.bash_profile The personal initialization file, executed for login shells ~/.bashrc The individual per-interactive-shell startup file ~/.bash_logout The individual login shell cleanup file, executed when a login shell exits ~/.inputrc Individual readline initialization file I believe .profile and .bash_profile are synonyms, so you'd only use one or the other. .bash_history holds your command line history, and is not used for runtime configuration. I'm not sure what shell scripts run from another application do. I would guess they stuff done in .bashrc would affect them, but not stuff in *profile. Cheers, Tyler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which files do what: .bashrc and friends
2008/11/19 tyler [EMAIL PROTECTED]: Dotan Cohen [EMAIL PROTECTED] writes: On a Debian-based system running KDE 3.5.10 I see several files that are used when logging in / starting a Konsole: .profile .bash_history .bash_logout .bash_profile .bashrc Thanks in advance. If there are any good docs that explain this, I'd love to see them. I have not been able to google anything recent that is relevant to Debian. man bash answers most of your questions: FILES /bin/bash The bash executable /etc/profile The systemwide initialization file, executed for login shells /etc/bash.bashrc The systemwide per-interactive-shell startup file /etc/bash.logout The systemwide login shell cleanup file, executed when a login shell exits ~/.bash_profile The personal initialization file, executed for login shells ~/.bashrc The individual per-interactive-shell startup file ~/.bash_logout The individual login shell cleanup file, executed when a login shell exits ~/.inputrc Individual readline initialization file I believe .profile and .bash_profile are synonyms, so you'd only use one or the other. .bash_history holds your command line history, and is not used for runtime configuration. I'm not sure what shell scripts run from another application do. I would guess they stuff done in .bashrc would affect them, but not stuff in *profile. Cheers, Tyler Thanks, Tyler. I had read man bash so long ago that I forgot what was there, and didn't think to review it. Just to confirm (as in CS so many things are counter intuitive): 1) Is a login shell run when the user logs onto KDE (even though he does not see a konsole window)? 2) Is an interactive shell the term used for opening a konsole window? Thanks! -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я ä-ö-ü-ß-Ä-Ö-Ü
Re: Which files do what: .bashrc and friends
Dotan Cohen [EMAIL PROTECTED] writes: 2008/11/19 tyler [EMAIL PROTECTED]: Dotan Cohen [EMAIL PROTECTED] writes: On a Debian-based system running KDE 3.5.10 I see several files that are used when logging in / starting a Konsole: .profile .bash_history .bash_logout .bash_profile .bashrc Thanks in advance. If there are any good docs that explain this, I'd love to see them. I have not been able to google anything recent that is relevant to Debian. man bash answers most of your questions: Thanks, Tyler. I had read man bash so long ago that I forgot what was there, and didn't think to review it. Just to confirm (as in CS so many things are counter intuitive): 1) Is a login shell run when the user logs onto KDE (even though he does not see a konsole window)? Yes. 2) Is an interactive shell the term used for opening a konsole window? Yes. Cheers, Tyler -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which files do what: .bashrc and friends
Dotan Cohen wrote:
On a Debian-based system running KDE 3.5.10 I see several files that
are used when logging in / starting a Konsole:
.profile
Run once upon login.
.bash_history
List of previous commands for recall/edit/re execution
.bash_logout
Run once upon logout
.bash_profile
I believe equivalent to .profile
.bashrc
Run once for each interactive shell, after .profile
The main difference between .profile and .bashrc is that
.profile only gets run when you start a login shell,
but .bashrc gets run for all shells.
So, for example, if you use
$ su -
you'll run root's .profile and .bashrc, but
$ su
only runs root's .bashrc
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which files do what: .bashrc and friends
On Wednesday 19 November 2008, tyler [EMAIL PROTECTED] wrote about 'Re: Which files do what: .bashrc and friends': I believe .profile and .bash_profile are synonyms, so you'd only use one or the other. .profile is only used by bash when it cannot find .bash_profile. .profile is also used by the traditional Bourne shell and Korn shell and is the standard location of such commands. -- Boyd Stephen Smith Jr. ,= ,-_-. =. [EMAIL PROTECTED] ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/ signature.asc Description: This is a digitally signed message part.
Re: Which files do what: .bashrc and friends
On Wednesday 19 November 2008, Dotan Cohen [EMAIL PROTECTED] wrote about
'Re: Which files do
what: .bashrc and friends':
1) Is a login shell run when the user logs onto KDE (even though he
does not see a konsole window)?
Nope a login shell is when bash is executed with the -l option, or having
an argv[0] starting with '-'.
If you want things to run when KDE starts up, you can use .kde/env
and .kde/Autostart. All readable files in .kde/env are sourced by
the /usr/bin/startkde script, which is run by /bin/sh. All .desktop files
in .kde/Autostart are activated (by kdeinit or somesuch, around the same
time your session is restored; .desktop file are like things in KMenu, they
might open a file, start a program, whatever).
2) Is an interactive shell the term used for opening a konsole window?
Yes. An interactive shell is any shell where stdin AND stderr are
terminals (tty or pty). When konsole (and other X11 terminal applications)
use a shell, they attach stdin, stdout, and stderr to a pseudo-terminal
(pty; slave side) created by them.
(This leaves non-interactive shells; those when stdin or stderr are not
attached to a terminal.)
An example:
[EMAIL PROTECTED]:~$ grep keychain .bash_profile
[[ -t 0 ]] [[ -x ~/bin/keychain-load.bash ]] eval
$(~/bin/keychain-load.bash)
[EMAIL PROTECTED]:~$ cat bin/keychain-load.bash
#! /bin/bash
# Starts and loads the keychain, interacting with the user as needed.
# May start gnupg-agent, but doesn't prompt for keys because gnupg-agent
# regularly times out keys.
# Since interaction is clearly available, we clear the keychain before adding
# keys (assume user is an attacker).
if [ -x /usr/bin/keychain ]; then
SSH_KEYS=('id_dsa')
eval $(/usr/bin/keychain --eval --inherit any-once --stop others \
--clear [EMAIL PROTECTED])
fi
[EMAIL PROTECTED]:~$ grep -A 1 keychain .bashrc
if [ -x ~/bin/keychain-start.sh ]; then
. ~/bin/keychain-start.sh
fi
[EMAIL PROTECTED]:~$ cat bin/keychain-start.sh
#! /bin/sh
# Starts keychain or initializes the environment, but requires no interactivity.
if [ -x /usr/bin/keychain ]; then
{ eval $(/usr/bin/keychain --eval --quiet --inherit any-once --stop
others --noask --lockwait
0); } /dev/null 21
fi
[EMAIL PROTECTED]:~$ cd .kde
/home/bss/.kde
[EMAIL PROTECTED]:~/.kde$ ls env Autostart
Autostart:
keychain-load.desktop
env:
gtk-qt-engine.rc.sh keychain-start.sh ssh-askpass.sh
[EMAIL PROTECTED]:~/.kde$ # env/keychain-start.sh is a hard link to
~/bin/keychain-start.sh
[EMAIL PROTECTED]:~/.kde$ cat Autostart/keychain-load.desktop
[Desktop Entry]
Name=Load Keychain
Comment=Start agents and add keys to them.
Exec=/home/bss/bin/keychain-load.bash
Terminal=true
StartupNotify=false
Type=Application
Encoding=UTF-8
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
[EMAIL PROTECTED] ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
signature.asc
Description: This is a digitally signed message part.
Re: Which files do what: .bashrc and friends
Boyd Stephen Smith Jr. [EMAIL PROTECTED] writes: On Wednesday 19 November 2008, Dotan Cohen [EMAIL PROTECTED] wrote about 'Re: Which files do what: .bashrc and friends': 1) Is a login shell run when the user logs onto KDE (even though he does not see a konsole window)? Nope a login shell is when bash is executed with the -l option, or having an argv[0] starting with '-'. If you want things to run when KDE starts up, you can use .kde/env and .kde/Autostart. All readable files in .kde/env are sourced by the /usr/bin/startkde script, which is run by /bin/sh. All .desktop files in .kde/Autostart are activated (by kdeinit or somesuch, around the same time your session is restored; .desktop file are like things in KMenu, they might open a file, start a program, whatever). Aha! I assumed since kdm was where KDE users login from, then it must call .*profile in the process. Seems strange that you could be logged in without having actually encountered a login shell. Google gave me this, which helped to explain it: http://ubuntuforums.org/archive/index.php/t-350855.html Cheers, Tyler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which files do what: .bashrc and friends
Boyd Stephen Smith Jr. (2008-11-19 14:37 -0600) wrote: 1) Is a login shell run when the user logs onto KDE (even though he does not see a konsole window)? Nope a login shell is when bash is executed with the -l option, or having an argv[0] starting with '-'. If K Display Manager (kdm) is installed file /etc/kde3/kdm/Xsession executes user's login shell, for example $HOME/.bash_profile which in turn might source .bashrc too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which files do what: .bashrc and friends
Dotan Cohen a écrit : Thanks in advance. If there are any good docs that explain this, I'd love to see them. I have not been able to google anything recent that is relevant to Debian. Quick'n dirty solution : Another way to know, even if it does not cover all cases, is to put the following line at the beginning of each : echo `basename $0` is running Fanfan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which files do what: .bashrc and friends
Mike McCarty [EMAIL PROTECTED]: Dotan Cohen wrote: .bashrc Run once for each interactive shell, after .profile ... if called by .profile or .bash_profile. A long time ago, this was automatic (a la ksh and ENV; if ENV = ~/.kshrc, then ~/.kshrc was run on login shell invocation). Every bash install I've seen in years has . .bashrc in the stock install .bash_profile, meaning it's no longer automatic. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which files do what: .bashrc and friends
From the INVOCATION section of the Bash man page: When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior. When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: .bash_profile and .bashrc not executing
John Salmon wrote: Martin Marcher [EMAIL PROTECTED] wrote in news:[EMAIL PROTECTED]: On Saturday 12 January 2008 20:50 John Salmon wrote: I'm a new user to Debian Linux. I have the latest version loaded on a dedicated PC with all the default settings. I have added a ~/bin directory to my system. My .bash_profile and .bashrc files were the default files loaded during the install. However, my PATH remains unchanged when I log on even though the .bash_profile file has the lines to add my ~/bin directory. I can make the change manually after I've logged on and can execute files that are in that directory. Also, the aliases set in my .bashrc file don't work. As a check, I've set environment variables in both files and they return null with echo after logging on. I haven't tried re-installing the system from scratch. Any suggestions? you did re-login after the changes did you? (i think bash -l also behaves like a full re-llogin) hth martin Yes, I did. In fact, I also tried re-booting the system. Another thing, I tried to run ~/.bash_profile and got \bash: /home/johns/.bash_profile: Permission denied (johns is me). ls -al shows .bash_prfile access has no execute permission set. John, I recently posted a rather long description of how the shell deals with files, whether executable (binary or scripts) or sourced. Bottom line, if the shell knows the name of the file and that the file is a script, it needs then to be able to read it. You did not post the ls -l output, so I can't say if permissions might be the issue or not. The first field of ls -l should be at least a dash followed by the letter 'r', followed by either a dash or 'w', etc. You also didn't say whether you're login is from the GUI (xdm, kdm, gdm) or from a console in text mode. If you logged in using the GUI, you should switch to a console and do a text mode login to see if you get any error messages from the shell. Or, from a shell window after the GUI login, you can use 'bash -l' at the command prompt, as suggested above, to start a new shell that acts like a login shell. If any errors are reported, that is the likely cause of your problem, since the shell will abort processing the startup files when an error is found. -- Bob McGowan smime.p7s Description: S/MIME Cryptographic Signature
Re: .bash_profile and .bashrc not executing
Martin Marcher [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
On Saturday 12 January 2008 20:50 John Salmon wrote:
I'm a new user to Debian Linux. I have the latest version loaded on a
dedicated PC with all the default settings. I have added a ~/bin
directory to my system. My .bash_profile and .bashrc files were the
default files loaded during the install. However, my PATH remains
unchanged when I log on even though the .bash_profile file has the
lines to add my ~/bin directory. I can make the change manually after
I've logged on and can execute files that are in that directory.
Also, the aliases set in my .bashrc file don't work. As a check, I've
set environment variables in both files and they return null with
echo after logging on. I haven't tried re-installing the system from
scratch.
Any suggestions?
you did re-login after the changes did you? (i think bash -l also
behaves like a full re-llogin)
hth
martin
Yes, I did. In fact, I also tried re-booting the system.
Another thing, I tried to run ~/.bash_profile and got \bash:
/home/johns/.bash_profile: Permission denied (johns is me). ls -al shows
.bash_prfile access has no execute permission set.
--
John Salmon
[EMAIL PROTECTED]
Posted via Pronews.com - Premium Corporate Usenet News Provider
http://www.pronews.com offers corporate packages that have access to 100,000+
newsgroups
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: .bash_profile and .bashrc not executing
John Salmon [EMAIL PROTECTED]: Martin Marcher [EMAIL PROTECTED] wrote in news:[EMAIL PROTECTED]: On Saturday 12 January 2008 20:50 John Salmon wrote: I'm a new user to Debian Linux. I have the latest version loaded on a dedicated PC with all the default settings. I have added a ~/bin directory to my system. My .bash_profile and .bashrc files were the default files loaded during the install. However, my PATH remains unchanged when I log on even though the .bash_profile file has the lines to add my ~/bin directory. I can make the change manually after I've logged on and can execute files that are in that directory. Also, the aliases set in my .bashrc file don't work. As a check, I've set environment variables in both files and they return null with echo after logging on. I haven't tried re-installing the system from scratch. you did re-login after the changes did you? (i think bash -l also behaves like a full re-llogin) Yes, I did. In fact, I also tried re-booting the system. That's excessive. Reboots are only necessary when you update the kernel and modules, or change hardware. Another thing, I tried to run ~/.bash_profile and got \bash: /home/johns/.bash_profile: Permission denied (johns is me). ls -al shows .bash_prfile access has no execute permission set. (0) heretic /home/keeling_ ls -lF .profile .bash_profile .bashrc /bin/ls: .bash_profile: No such file or directory -rw-r--r-- 1 keeling keeling 1158 2007-06-14 12:44 .bashrc -rw-r--r-- 1 keeling keeling 1203 2008-01-05 10:03 .profile Notice I have no .bash_profile, but I do have .profile, and neither of those are executable. On startup, bash looks for .profile or .bash_profile and runs it. Manually, try: source ~/.bash_profile or: . ~/.bash_profile # that's a period/dot -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.bash_profile and .bashrc not executing
I'm a new user to Debian Linux. I have the latest version loaded on a
dedicated PC with all the default settings. I have added a ~/bin directory
to my system. My .bash_profile and .bashrc files were the default files
loaded during the install. However, my PATH remains unchanged when I log on
even though the .bash_profile file has the lines to add my ~/bin directory.
I can make the change manually after I've logged on and can execute files
that are in that directory. Also, the aliases set in my .bashrc file don't
work. As a check, I've set environment variables in both files and they
return null with echo after logging on. I haven't tried re-installing the
system from scratch.
Any suggestions?
--
John Salmon
[EMAIL PROTECTED]
Posted via Pronews.com - Premium Corporate Usenet News Provider
http://www.pronews.com offers corporate packages that have access to 100,000+
newsgroups
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: .bash_profile and .bashrc not executing
On Saturday 12 January 2008 20:50 John Salmon wrote: I'm a new user to Debian Linux. I have the latest version loaded on a dedicated PC with all the default settings. I have added a ~/bin directory to my system. My .bash_profile and .bashrc files were the default files loaded during the install. However, my PATH remains unchanged when I log on even though the .bash_profile file has the lines to add my ~/bin directory. I can make the change manually after I've logged on and can execute files that are in that directory. Also, the aliases set in my .bashrc file don't work. As a check, I've set environment variables in both files and they return null with echo after logging on. I haven't tried re-installing the system from scratch. Any suggestions? you did re-login after the changes did you? (i think bash -l also behaves like a full re-llogin) hth martin -- http://noneisyours.marcher.name http://feeds.feedburner.com/NoneIsYours You are not free to read this message, by doing so, you have violated my licence and are required to urinate publicly. Thank you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.bashrc messes up 'set'
I've just discovered that a stable install (4.0, (with rdiff-backup
pulled from testing)) has a wonky (that's a technical term, you
understand ... ;-) ) /etc/skel/bashrc apparently.
If I ssh in as a freshly-created user and then run the set command, I
get pages and pages of script-looking text, seemingly related to
ImageMagick, as below (most of it snipped out as marked):
[EMAIL PROTECTED]:~$ set | more
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
snip normal stuff you'd expect to see
SSH_TTY=/dev/pts/1
TERM=xterm
UID=1024
USER=chyntt
_=set
bash205='3.1.17(1)-release'
bash205b='3.1.17(1)-release'
bash3='3.1.17(1)-release'
_ImageMagick ()
{
local prev;
prev=${COMP_WORDS[COMP_CWORD-1]};
case $prev in
-channel)
COMPREPLY=($( compgen -W 'Red Green Blue Opacity \
Matte Cyan Magenta Yellow Black' --
$cur ));
return 0
snip pages and pages of similar scripting stuff
COMPREPLY=($( command ls $admindir | grep ^$cur ))
}
set_prefix ()
{
[ -z ${prefix:-} ] || prefix=${cur%/*}/;
[ -r ${prefix:-}CVS/Entries ] || prefix=
}
If I rename/delete/move the user's .bashrc and then log out / back in,
the set command returns what would be expected.
I don't see anything particularly odd in /etc/skel/bashrc (but then, I'm
not a scripter). I wasn't able to find anything about this on the 'net.
I'm mostly just wondering if other folks have seen this.
Thanks!
--
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: .bashrc messes up 'set'
On Tue, Sep 18, 2007 at 10:08:35 -0500, Kent West wrote:
I've just discovered that a stable install (4.0, (with rdiff-backup pulled
from testing)) has a wonky (that's a technical term, you understand ... ;-)
) /etc/skel/bashrc apparently.
If I ssh in as a freshly-created user and then run the set command, I get
pages and pages of script-looking text, seemingly related to ImageMagick,
as below (most of it snipped out as marked):
[...]
_ImageMagick ()
{
local prev;
prev=${COMP_WORDS[COMP_CWORD-1]};
case $prev in
-channel)
COMPREPLY=($( compgen -W 'Red Green Blue Opacity \
Matte Cyan Magenta Yellow Black' -- $cur
));
return 0
snip pages and pages of similar scripting stuff
COMPREPLY=($( command ls $admindir | grep ^$cur ))
}
set_prefix ()
{
[ -z ${prefix:-} ] || prefix=${cur%/*}/;
[ -r ${prefix:-}CVS/Entries ] || prefix=
}
If I rename/delete/move the user's .bashrc and then log out / back in, the
set command returns what would be expected.
I don't see anything particularly odd in /etc/skel/bashrc (but then, I'm
not a scripter). I wasn't able to find anything about this on the 'net. I'm
mostly just wondering if other folks have seen this.
I think this is due to bash_completion now being enabled in the default
.bashrc from /etc/skel. These three lines are responsible:
if [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
You can comment them out if the bash_completion code bothers you.
--
Regards,| http://users.icfo.es/Florian.Kulzer
Florian |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: .bashrc messes up 'set'
On 09/18/2007 10:08 AM, Kent West wrote: I've just discovered that a stable install (4.0, (with rdiff-backup pulled from testing)) has a wonky (that's a technical term, you understand ... ;-) ) /etc/skel/bashrc apparently. [...] I don't see anything particularly odd in /etc/skel/bashrc (but then, I'm not a scripter). I wasn't able to find anything about this on the 'net. I'm mostly just wondering if other folks have seen this. Thanks! It's not really a problem. That code seems to relate to bash_completion. Look at /etc/bash_completion and /etc/bash_completion.d/ if you're interested. Or just ignore it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: .bashrc problem--ls output and root prompt
On Tue, Aug 21, 2007 at 04:14:04PM -0700, Dr. Jennifer Nussbaum wrote: PS1='\h\w $ '; export PS1 So, nothing fancy. How do i get my coloured ls back, and my # prompt as sudo'ed root? Use \$ rather than a plain $ to get # as root. A. -- Ansgar Esztermann Researcher Sysadmin http://www.mpibpc.mpg.de/groups/grubmueller/start/people/aeszter/index.shtml pgpOVGmgXgxwy.pgp Description: PGP signature
.bashrc problem--ls output and root prompt
Im a new Debian Etch user, coming from FreeBSD. When i
first installed my system, running the ls command
would
give me coloured output (executables one colour,
directories another). Also, when I sudo'ed to root, i
would get the usual # prompt as root.
I then copied over my (straightforward) .bashrc file,
and now i dont have the colored output and sudoing to
root
leaves me with a $ prompt. (I do reset my PS1 line,
but i dont know how to have a different one for root,
keeping
the #.) Can someone give me a suggestion? My
complete
.bashrc, less comments, and with my CVSROOT masked,
is:
---
PS1='\h\w $ '; export PS1
BLOCKSIZE=K;export BLOCKSIZE
EDITOR=emacs; export EDITOR
CVS_RSH=ssh; export CVS_RSH
CVSROOT= [HIDDEN]; export CVSROOT
PATH=${PATH}:/sbin:/usr/sbin
---
So, nothing fancy. How do i get my coloured ls back,
and my # prompt as sudo'ed root?
Thanks,
Jen
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: .bashrc problem--ls output and root prompt
2007/8/21, Dr. Jennifer Nussbaum [EMAIL PROTECTED]:
Im a new Debian Etch user, coming from FreeBSD. When i
first installed my system, running the ls command
would
give me coloured output (executables one colour,
directories another). Also, when I sudo'ed to root, i
would get the usual # prompt as root.
I then copied over my (straightforward) .bashrc file,
and now i dont have the colored output and sudoing to
root
leaves me with a $ prompt. (I do reset my PS1 line,
but i dont know how to have a different one for root,
keeping
the #.) Can someone give me a suggestion? My
complete
.bashrc, less comments, and with my CVSROOT masked,
is:
---
PS1='\h\w $ '; export PS1
BLOCKSIZE=K;export BLOCKSIZE
EDITOR=emacs; export EDITOR
CVS_RSH=ssh; export CVS_RSH
CVSROOT= [HIDDEN]; export CVSROOT
PATH=${PATH}:/sbin:/usr/sbin
---
So, nothing fancy. How do i get my coloured ls back,
and my # prompt as sudo'ed root?
Hi,
try to add:
alias ls='ls --color=auto'
Best regards,
Sergio Cuellar
--
Meine Hoffnung soll mich leiten
Durch die Tage ohne Dich
Und die Liebe soll mich tragen
Wenn der Schmerz die Hoffnung bricht
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gnome i .bashrc
El Friday 18/05/07, a les 07:26 (+0200), Orestes Mas va escriure: .Xsession? .xinitrc? Això ara mateix no m'ho sé de memòria i no tinc temps per buscar-ho (haig de preparar una classe), però segur que algú t'ho respon. Suposo que deu ser .Xsession, però vull dir amb això ho he de tenir tot duplicat a dos llocs. En fi, potser posant un source ~/.environment en el .Xsession i en el .bashrc i llavors definir totes les variables en aquest fitxer, però em pregunto si hi ha algun sistema estàndard de fer-ho. Ho dic perquè si vas xapusses d'aquestes al final et tornes boig per trobar les coses :) Ernest
Re: gnome i .bashrc
El Friday 18/05/07, a les 01:45 (+0200), Orestes Mas va escriure: A Divendres 18 Maig 2007 00:15, Ernest Adrogué va escriure: Hola nanos, A veure, el problema que tinc és que el Gnome/GDM no llegeix el fitxer .bashrc a l'arrencada, per tant si canvio el PATH, etc. o les variables d'entorn, no afecta als programes que s'arrenquen directament del menú... la qual cosa és un problema. Algú sap com fer-ho, perquè ho llegeixi? Jo diria que no l'ha de llegir. El .bashrc i el .bash_profile són, respectivament, per logins no interactius i interactius _a la consola_. Quan tu entres a les X no ho fas a través d'una consola sinó a través de GDM... D'acord, doncs reformulo la pregunta: Quina és la manera per definir variables d'entorn a nivell d'usuari? Perquè jo les variables les he posat sempre en el .bashrc, que em sembla que era la manera tradicional de fer-ho. Sembla que amb els nous sistemes aquests ha quedat obsolet aquest mètode. Ernest
Re: personal .bashrc
Marc Shapiro wrote: Lorenzo Bettini wrote: Hi on the standard user's home I use everyday I have the .bashrc file that is read upon login. Now I created a brand new user (with adduser), but the .bashrc file I inserted in his home is never read upon login... in /etc/profile and /etc/bash.profile the .bashrc is actually never read... so how does it work? Check .bash_profile for the original user. It is probably sourcing .bashrc with code similar to: # include .bashrc if it exists if [ -f ~/.bashrc ]; then . ~/.bashrc fi and your new user is probably not doing this. you're right! actually the new user did not have .bash_profile at all... I had to create it like that. thanks Lorenzo -- +-+ | Lorenzo Bettini ICQ# lbetto, 16080134 | | PhD in Computer Science, DSI, Univ. di Firenze | | Florence - Italy(GNU/Linux User # 158233) | | http://www.lorenzobettini.it| | http://tronprog.blogspot.com BLOG | | http://www.purplesucker.com Deep Purple Cover Band | | http://www.gnu.org/software/src-highlite| | http://www.gnu.org/software/gengetopt | | http://www.gnu.org/software/gengen | | http://doublecpp.sourceforge.net| +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: personal .bashrc
Ali Jawad wrote: I remember that the files are read like /etc/profile - ~/.bash_profile - ~/.bashrc - ~./profile but the bashrc file should be created by default without you having to insert it.. that's what I thought too, but neither .bashrc nor .bash_profile were created automatically... -- +-+ | Lorenzo Bettini ICQ# lbetto, 16080134 | | PhD in Computer Science, DSI, Univ. di Firenze | | Florence - Italy(GNU/Linux User # 158233) | | http://www.lorenzobettini.it| | http://tronprog.blogspot.com BLOG | | http://www.purplesucker.com Deep Purple Cover Band | | http://www.gnu.org/software/src-highlite| | http://www.gnu.org/software/gengetopt | | http://www.gnu.org/software/gengen | | http://doublecpp.sourceforge.net| +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: personal .bashrc
On Tue, Dec 26, 2006 at 10:53:27AM +0100, Lorenzo Bettini wrote.. I remember that the files are read like /etc/profile - ~/.bash_profile - ~/.bashrc - ~./profile but the bashrc file should be created by default without you having to insert it.. that's what I thought too, but neither .bashrc nor .bash_profile were created automatically... Check your /etc/skel/ directory, remembering that you won't be able to see what is listed there (in terms of dot files) unless you use a command like 'ls -la'. The files you have in this directory are the files that are automatically inserted into $HOME whenever you create a new user. Edit them, and all *new* users created will get these edited files upon user creation. -- Kevin Coyner GnuPG key: 1024D/8CE11941 signature.asc Description: Digital signature
personal .bashrc
Hi on the standard user's home I use everyday I have the .bashrc file that is read upon login. Now I created a brand new user (with adduser), but the .bashrc file I inserted in his home is never read upon login... in /etc/profile and /etc/bash.profile the .bashrc is actually never read... so how does it work? thanks in advance Lorenzo -- +-+ | Lorenzo Bettini ICQ# lbetto, 16080134 | | PhD in Computer Science, DSI, Univ. di Firenze | | Florence - Italy(GNU/Linux User # 158233) | | http://www.lorenzobettini.it| | http://tronprog.blogspot.com BLOG | | http://www.purplesucker.com Deep Purple Cover Band | | http://www.gnu.org/software/src-highlite| | http://www.gnu.org/software/gengetopt | | http://www.gnu.org/software/gengen | | http://doublecpp.sourceforge.net| +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: personal .bashrc
Lorenzo Bettini wrote: Hi on the standard user's home I use everyday I have the .bashrc file that is read upon login. Now I created a brand new user (with adduser), but the .bashrc file I inserted in his home is never read upon login... in /etc/profile and /etc/bash.profile the .bashrc is actually never read... so how does it work? Check .bash_profile for the original user. It is probably sourcing .bashrc with code similar to: # include .bashrc if it exists if [ -f ~/.bashrc ]; then . ~/.bashrc fi and your new user is probably not doing this. -- Marc Shapiro [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: personal .bashrc
I remember that the files are read like /etc/profile - ~/.bash_profile - ~/.bashrc - ~./profile but the bashrc file should be created by default without you having to insert it.. On 12/25/06, Lorenzo Bettini [EMAIL PROTECTED] wrote: Hi on the standard user's home I use everyday I have the .bashrc file that is read upon login. Now I created a brand new user (with adduser), but the .bashrc file I inserted in his home is never read upon login... in /etc/profile and /etc/bash.profile the .bashrc is actually never read... so how does it work? thanks in advance Lorenzo -- +-+ | Lorenzo Bettini ICQ# lbetto, 16080134 | | PhD in Computer Science, DSI, Univ. di Firenze | | Florence - Italy(GNU/Linux User # 158233) | | http://www.lorenzobettini.it| | http://tronprog.blogspot.com BLOG | | http://www.purplesucker.com Deep Purple Cover Band | | http://www.gnu.org/software/src-highlite| | http://www.gnu.org/software/gengetopt | | http://www.gnu.org/software/gengen | | http://doublecpp.sourceforge.net| +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- With Regards Ali Jawad -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Lokalen Editor ohne root-Rechte mit bashrc definieren
Ich habe einen Shellzugang und dort keine Rootrechte. In der lokalen .bashrc finde ich: # .bashrc # User specific aliases and functions # Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi /etc/bashrc kann ich nur lesen, auch klar und dort ist nano definiert, den ich nun nicht so mag. export EDITOR=pico export VISUAL=pico Wo trage ich nun zB folgendes ein: export EDITOR=/usr/bin/vim Es hilt auch nichts, wenn ich den export lokal nach if definiere. Was bedeutet VISUAL=pico in diesem Zusammenhang? Al -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Lokalen Editor ohne root-Rechte mit bashrc definieren
On Wed, 25 Oct 2006 16:24:22 +0200 Al Bogner wrote: Ich habe einen Shellzugang und dort keine Rootrechte. In der lokalen .bashrc finde ich: # .bashrc # User specific aliases and functions # Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi /etc/bashrc kann ich nur lesen, auch klar und dort ist nano definiert, den ich nun nicht so mag. export EDITOR=pico export VISUAL=pico nano? Ich seh da pico ;-) Wobei pico auf den meisten Debian-Systemen dann doch wohl n Symlink auf nano ist. Wo trage ich nun zB folgendes ein: export EDITOR=/usr/bin/vim Es hilt auch nichts, wenn ich den export lokal nach if definiere. Du willst dir ~/.bash_profile statt ~/.bashrc angucken. Was bedeutet VISUAL=pico in diesem Zusammenhang? Ich glaube $EDITOR ist was einfaches wie 'ed' und $VISUAL ist vim/nano/etc... Wenn VISUAL gesetzt ist wird EDITOR ignoriert afaik. Gruß Evgeni
Re: Lokalen Editor ohne root-Rechte mit bashrc definieren
Am Mittwoch, 25. Oktober 2006 16:38 schrieb Evgeni Golov: On Wed, 25 Oct 2006 16:24:22 +0200 Al Bogner wrote: Ich habe einen Shellzugang und dort keine Rootrechte. In der lokalen .bashrc finde ich: # .bashrc # User specific aliases and functions # Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi /etc/bashrc kann ich nur lesen, auch klar und dort ist nano definiert, den ich nun nicht so mag. export EDITOR=pico export VISUAL=pico nano? Ich seh da pico ;-) Wobei pico auf den meisten Debian-Systemen dann doch wohl n Symlink auf nano ist. Wird wohl so sein. Ich will dort nicht zu viel im System rumstochern, nicht, dass sie mich rauswerfen. Wo trage ich nun zB folgendes ein: export EDITOR=/usr/bin/vim Es hilt auch nichts, wenn ich den export lokal nach if definiere. Du willst dir ~/.bash_profile statt ~/.bashrc angucken. Was bedeutet VISUAL=pico in diesem Zusammenhang? Ich glaube $EDITOR ist was einfaches wie 'ed' und $VISUAL ist vim/nano/etc... Wenn VISUAL gesetzt ist wird EDITOR ignoriert afaik. So klappt es leider nicht. Wenn ich mutt aufrufe, dann startet noch immer nano als Editor. cat .bash_profile # .bash_profile # Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi # User specific environment and startup programs PATH=$PATH:$HOME/bin export PATH unset USERNAME export EDITOR=/usr/bin/vim export VISUAL==/usr/bin/vim Al -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Lokalen Editor ohne root-Rechte mit bashrc definieren
Am Mittwoch, 25. Oktober 2006 19:15 schrieb Al Bogner: So klappt es leider nicht. Wenn ich mutt aufrufe, dann startet noch immer nano als Editor. cat .bash_profile # .bash_profile # Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi # User specific environment and startup programs PATH=$PATH:$HOME/bin export PATH unset USERNAME export EDITOR=/usr/bin/vim export VISUAL==/usr/bin/vim Klappt doch, das 2. = war natürlich zu viel. Al
Re: Lokalen Editor ohne root-Rechte mit bashrc definieren
On Wed, Oct 25, 2006 at 07:21:04PM +0200, Al Bogner wrote: export VISUAL==/usr/bin/vim Klappt doch, das 2. = war natürlich zu viel. Grundsaetzlich immer funktionieren Konstrukte wie alias mutt='EDITOR=vim mutt' cu ulf -- Ulf Volmer [EMAIL PROTECTED] www.u-v.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Lokalen Editor ohne root-Rechte mit bashrc definieren
* Al Bogner [EMAIL PROTECTED] wrote: So klappt es leider nicht. Wenn ich mutt aufrufe, dann startet noch immer nano als Editor. Hast du die .bash_profile auch eingelesen? Den Editor für mutt kannst du ausserdem auch in der .muttrc angeben, vielleicht ist der ja auch in einer globalen /etc/Muttrc auf nano eingestellt. Gruß Jens
Re: Testing/Etch: .bash_profile/.bashrc n ach ssh login NICHT ausgeführt
man bash When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior. When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. [EMAIL PROTECTED]:~$ cat .profile # ~/.profile: executed by Bourne-compatible login shells. if [ -f ~/.bashrc ]; then . ~/.bashrc fi #PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11 #export PATH mesg n cu mb Holger Rauch wrote: Hallo, ich habe bei einem neu aufgesetzten Testing (Etch) System das Problem, daß nach einem ssh login die .bash_profile und die .bashrc im HOME-Verzeichnis eines Benutzers nicht mehr gesourced werden. Wenn ich auf diesem neu installierten System von einem user mittels su - user_name auf einen anderen user wechsle, werden .bash_profile und .bashrc wie erwartet gesourced. Bei einem System, das ich seit geraumer Zeit von Sarge auf Etch upgedated habe, gibt es dieses Problem interessanterweise NICHT (zumindest hab ich es bis jetzt noch nicht bemerkt). Meine ersten Verdächtigen waren die SSH-Konfiguration (server- und client-seitig) bzw. die PAM-Konfiguration. Allerdings konnte ich da erstmal nix feststellen. In den README.Debian files zu den PAM packages konnte ich ebenfalls nix finden. Offensichtliche Fragen: - Woran liegt es, daß nach ssh logins auf einem neu hochgezogenen Etch-/Testing-System die .bash_profile/.bashrc im HOME-Verzeichnis eines Benutzers nicht mehr gesourced werden? - Was muß man an welchen config files ändern, um das alte Verhalten (Berücksichtigung von benutzer-spezifischen .bash_profile/.bashrc files) wieder herzustellen? Vielen Dank im Voraus für die Info! Gruß, Holger -- GPG key: 0x965D2902 GPG key fingerprint: 3FE8 7472 2637 2993 6BD7 015E 6E25 6D5A 965D 2902 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Testing/Etch: .bash_ profile/.bashrc nach ssh login NICHT ausgeführt
Nein, ganz so einfach ist es nicht. Denn: a) die shell ist klar eine login shell b) ich habe die --noprofile option NICHT angegeben c) ~/.bash_profile ist definitiv da und wird aber trotzdem bei ssh logins NICHT gesourced (~/.bashrc ist auch da und wird explizit von der ~/.bash_profile aus gesourced) d) Wie gesagt, gibt es einen Unterschied zwischen d1) logins mittels su - user_name und d2) den ssh logins Bei d1) funktioniert's wie gehabt (und erwuenscht), bei d2) NICHT Was soll dieses Verhalten mit der bash man page (bzw. dem, was da drin steht) zu tun haben??? Ich vermute mal, GAR NIX! On Tue, 24 Oct 2006, Marc Schröder wrote: man bash When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior. When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. [EMAIL PROTECTED]:~$ cat .profile # ~/.profile: executed by Bourne-compatible login shells. if [ -f ~/.bashrc ]; then . ~/.bashrc fi #PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11 #export PATH mesg n cu mb Holger Rauch wrote: Hallo, ich habe bei einem neu aufgesetzten Testing (Etch) System das Problem, daß nach einem ssh login die .bash_profile und die .bashrc im HOME-Verzeichnis eines Benutzers nicht mehr gesourced werden. Wenn ich auf diesem neu installierten System von einem user mittels su - user_name auf einen anderen user wechsle, werden .bash_profile und .bashrc wie erwartet gesourced. Bei einem System, das ich seit geraumer Zeit von Sarge auf Etch upgedated habe, gibt es dieses Problem interessanterweise NICHT (zumindest hab ich es bis jetzt noch nicht bemerkt). Meine ersten Verdächtigen waren die SSH-Konfiguration (server- und client-seitig) bzw. die PAM-Konfiguration. Allerdings konnte ich da erstmal nix feststellen. In den README.Debian files zu den PAM packages konnte ich ebenfalls nix finden. Offensichtliche Fragen: - Woran liegt es, daß nach ssh logins auf einem neu hochgezogenen Etch-/Testing-System die .bash_profile/.bashrc im HOME-Verzeichnis eines Benutzers nicht mehr gesourced werden? - Was muß man an welchen config files ändern, um das alte Verhalten (Berücksichtigung von benutzer-spezifischen .bash_profile/.bashrc files) wieder herzustellen? Vielen Dank im Voraus für die Info! Gruß, Holger -- GPG key: 0x965D2902 GPG key fingerprint: 3FE8 7472 2637 2993 6BD7 015E 6E25 6D5A 965D 2902 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl) -- GPG key: 0x965D2902 GPG key fingerprint: 3FE8 7472 2637 2993 6BD7 015E 6E25 6D5A 965D 2902 signature.asc Description: Digital signature
Re: Testing/Etch: .bash_profile/.bashrc n ach ssh login NICHT ausgeführt
uups, ich hab mir jetzt die man page passage nochmal durchgelesen (und nicht nur cp). ich würde meinen, als ich das problem hatte, lautete diese noch anders. jedenfalls war mein fix der, dass ich in der .profile die .bashrc source. cu marc Holger Rauch wrote: Nein, ganz so einfach ist es nicht. Denn: a) die shell ist klar eine login shell b) ich habe die --noprofile option NICHT angegeben c) ~/.bash_profile ist definitiv da und wird aber trotzdem bei ssh logins NICHT gesourced (~/.bashrc ist auch da und wird explizit von der ~/.bash_profile aus gesourced) d) Wie gesagt, gibt es einen Unterschied zwischen d1) logins mittels su - user_name und d2) den ssh logins Bei d1) funktioniert's wie gehabt (und erwuenscht), bei d2) NICHT Was soll dieses Verhalten mit der bash man page (bzw. dem, was da drin steht) zu tun haben??? Ich vermute mal, GAR NIX! -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Testing/Etch: .bash_ profile/.bashrc nach ssh login NICHT ausgeführt
Hallo Marc (und auch an die anderen), mittlerweile hab ich das eigentliche Problem entdeckt: Ich vergaß beim Anlegen der accounts mit useradd, den switch -s für die login shell mitzugeben und nahm fälschlicherweise an, daß auch in diesem Fall /bin/bash als login shell in die /etc/passwd eingetragen wird (weil die bash ja unter Linux sowieso default ist; als Ausnahme fällt mir als Distro da spontan nur grml ein). Dem ist aber NICHT so (es stand /bin/sh drin). Wird die bash als /bin/sh aufgerufen, verhält sie sich meines Wissens auch so und will dann im HOME dir die ~/.profile (und NICHT ~/.bash_profile) sourcen. Die war aber NICHT da und deswegen wurde AUSSCHLIEßLICH /etc/profile gesourced. Fazit: Nach Abändern von /bin/sh in /bin/bash für die betroffenen accounts funktionierte alles wieder wie von vornherein gewünscht. Sorry für den unnötigen mailing list traffic (aber vielleicht helfen meine Ausführungen ja jmd., der ein ähnliches Problem hat). Gruß, Holger -- GPG key: 0x965D2902 GPG key fingerprint: 3FE8 7472 2637 2993 6BD7 015E 6E25 6D5A 965D 2902 signature.asc Description: Digital signature
Re: Testing/Etch: .bash_ profile/.bashrc nach ssh login NICHT ausgeführt
On Oct 24, Holger Rauch wrote: Ich vergaß beim Anlegen der accounts mit useradd, den switch -s für die login shell mitzugeben und nahm fälschlicherweise an, daß auch in diesem Fall /bin/bash als login shell in die /etc/passwd eingetragen wird (weil die bash ja unter Linux sowieso default ist; als Ausnahme fällt mir als Distro da spontan nur grml ein). Dem ist aber NICHT so (es stand /bin/sh drin). Wird die bash als /bin/sh aufgerufen, verhält sie sich meines Wissens auch so und will dann im HOME dir die ~/.profile (und NICHT ~/.bash_profile) sourcen. Die war aber NICHT da und deswegen wurde AUSSCHLIEßLICH /etc/profile gesourced. Den default kannst du in /etc/default/useradd festlegen. Dort ist auch dokumentiert, warum /bin/sh als Default gewählt wurde. Für adduser ist der Default in /etc/adduser.conf festgelegt, und da steht dann auch /bin/bash als Login Shell. Allerdings ist /bin/sh normalerweise ein Link auf /bin/bash. Verhält sich die bash anders, wenn sie als /bin/sh gestartet wird? Fazit: Nach Abändern von /bin/sh in /bin/bash für die betroffenen accounts funktionierte alles wieder wie von vornherein gewünscht. Oder ist bei dir /bin/sh kein symlink auf die bash? andreas -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Testing/Etch: .bash_profile/.bashrc nach ssh login NICHT ausgeführt
* Andreas Putzo: Allerdings ist /bin/sh normalerweise ein Link auf /bin/bash. Verhält sich die bash anders, wenn sie als /bin/sh gestartet wird? Ja: Schau mal in der manpage unter „--norc“. Andreas -- The whole world is a tuxedo and you are a pair of brown shoes. -- George Gobel -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Testing/Etch: .bash_ profile/.bashrc nach ssh login NICHT ausgeführt
Hallo, Andreas Putzo wrote: Allerdings ist /bin/sh normalerweise ein Link auf /bin/bash. Verhält sich die bash anders, wenn sie als /bin/sh gestartet wird? Ja: --norc Do not read and execute the system wide initialization file /etc/bash.bashrc and the personal initialization file ~/.bashrc if the shell is interactive. This option is on by default if the shell is invoked as sh. Schönen Gruß, Wolf -- Jetzt ist Frühlingszeit - Zeit für neue, jahreszeitbedingte Bauernregeln: Die Frühlingsluft riecht frisch und zärtlich, der Winter sagt: Ich habe fertig...! (Harald Schmidt) -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Testing/Etch: .bash_pro file/.bashrc nach ssh login NICHT ausgeführt
Hallo, ich habe bei einem neu aufgesetzten Testing (Etch) System das Problem, daß nach einem ssh login die .bash_profile und die .bashrc im HOME-Verzeichnis eines Benutzers nicht mehr gesourced werden. Wenn ich auf diesem neu installierten System von einem user mittels su - user_name auf einen anderen user wechsle, werden .bash_profile und .bashrc wie erwartet gesourced. Bei einem System, das ich seit geraumer Zeit von Sarge auf Etch upgedated habe, gibt es dieses Problem interessanterweise NICHT (zumindest hab ich es bis jetzt noch nicht bemerkt). Meine ersten Verdächtigen waren die SSH-Konfiguration (server- und client-seitig) bzw. die PAM-Konfiguration. Allerdings konnte ich da erstmal nix feststellen. In den README.Debian files zu den PAM packages konnte ich ebenfalls nix finden. Offensichtliche Fragen: - Woran liegt es, daß nach ssh logins auf einem neu hochgezogenen Etch-/Testing-System die .bash_profile/.bashrc im HOME-Verzeichnis eines Benutzers nicht mehr gesourced werden? - Was muß man an welchen config files ändern, um das alte Verhalten (Berücksichtigung von benutzer-spezifischen .bash_profile/.bashrc files) wieder herzustellen? Vielen Dank im Voraus für die Info! Gruß, Holger -- GPG key: 0x965D2902 GPG key fingerprint: 3FE8 7472 2637 2993 6BD7 015E 6E25 6D5A 965D 2902 signature.asc Description: Digital signature
Re: Globale bashrc
Gestern (05.10.2006/09:47 Uhr) schrieb Patrick Cornelißen, Jim Knuth schrieb: und das funktioniert eben bei mir NICHT :( Wie hast du das getestet? Loginshells werden nur beim logingelesen nicht wenn du ein neues Xterm oder so oeffnest. das heisst, dass wenn ich als root eingeloggt bin und su amavis mache, die Loginshell (.bashrc) nicht greift? Du kannst dich z.B. an einer der konsolen einloggen und es da testen. -- Viele Gruesse, Kind regards, Jim Knuth [EMAIL PROTECTED] ICQ #277289867 -- Zufalls-Zitat -- Eine Betriebsanalyse ist eine kostspielige Methode, durch betriebsfremde Fachleute das ermitteln zu lassen, was man im Betrieb seit 20 Jahren weiß. (Michael Schiff, dt. Schriftsteller, 1925-) -- Der Text hat nichts mit dem Empfaenger der Mail zu tun -- Virus free. Checked by NOD32 Version 1.1793 Build 8141 06.10.2006
Re: Globale bashrc
Jim Knuth schrieb: das heisst, dass wenn ich als root eingeloggt bin und su amavis mache, die Loginshell (.bashrc) nicht greift? su - amavis dann sollte auch das environment richtig eingelesen werden. -- Bye, Patrick Cornelissen http://www.p-c-software.de ICQ:15885533 signature.asc Description: OpenPGP digital signature
Re: Globale bashrc
On 06.10.06 15:06:23, Jim Knuth wrote: Gestern (05.10.2006/09:47 Uhr) schrieb Patrick Cornelißen, Jim Knuth schrieb: und das funktioniert eben bei mir NICHT :( Wie hast du das getestet? Loginshells werden nur beim logingelesen nicht wenn du ein neues Xterm oder so oeffnest. das heisst, dass wenn ich als root eingeloggt bin und su amavis mache, die Loginshell (.bashrc) nicht greift? .bashrc wird beim starten einer neuen shell eingelesen. .profile ist fuer Login-Shells zustaendig. su username startet aber nur ne neue Shell mit ner anderen uid, keine login-shell. Dafuer benutzt man su - username (oder su -l username). Siehe auch: man bash (Abschnitt INVOCATION) man su Andreas -- Afternoon very favorable for romance. Try a single person for a change. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Globale bashrc
Heute (06.10.2006/16:08 Uhr) schrieb Andreas Pakulat, On 06.10.06 15:06:23, Jim Knuth wrote: Gestern (05.10.2006/09:47 Uhr) schrieb Patrick Cornelißen, Jim Knuth schrieb: und das funktioniert eben bei mir NICHT :( Wie hast du das getestet? Loginshells werden nur beim logingelesen nicht wenn du ein neues Xterm oder so oeffnest. das heisst, dass wenn ich als root eingeloggt bin und su amavis mache, die Loginshell (.bashrc) nicht greift? .bashrc wird beim starten einer neuen shell eingelesen. .profile ist fuer Login-Shells zustaendig. su username startet aber nur ne neue Shell mit ner anderen uid, keine login-shell. Dafuer benutzt man su - username (oder su -l username). Siehe auch: man bash (Abschnitt INVOCATION) man su dank Euch allen. Genau so ... ;) Andreas -- Viele Gruesse, Kind regards, Jim Knuth [EMAIL PROTECTED] ICQ #277289867 -- Zufalls-Zitat -- Im Tierreich halten Schimpansen den Rekord für die schnellsten Quickies: drei Sekunden. -- Der Text hat nichts mit dem Empfaenger der Mail zu tun -- Virus free. Checked by NOD32 Version 1.1793 Build 8141 06.10.2006
Re: Globale bashrc
Am Donnerstag 05 Oktober 2006 02:53 schrieb Jim Knuth: nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen Inhalt, den root hat. Denn da funktionierts. Bei mir steht dafür: # 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 in der .bashrc Was hast Du denn da rein geschrieben? Gruß Chris -- A: because it distrupts the normal process of thought Q: why is top posting frowned upon
Re: Globale bashrc
Jim Knuth schrieb: und das funktioniert eben bei mir NICHT :( Wie hast du das getestet? Loginshells werden nur beim logingelesen nicht wenn du ein neues Xterm oder so öffnest. Du kannst dich z.B. an einer der konsolen einloggen und es da testen. -- Bye, Patrick Cornelissen http://www.p-c-software.de ICQ:15885533 signature.asc Description: OpenPGP digital signature
Re: Globale bashrc
at Donnerstag, 5. Oktober 2006 02:53 wrote Jim Knuth: nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen Inhalt, den root hat. Denn da funktionierts. in der /etc/bash.bashrc ist defaultmäßig schon etwas eingetragen, das du nur auskommentieren musst (gilt nur für user nicht für root). Zum testen komplett ab und wieder anmelden. -- Grüße, Simon P.S. entferne doch bitte dein Reply-To
Globale bashrc
Hallo, ich suche eine globale bashrc, die Ergänzungen zu den lokalen ~/.bashrc's macht. Im Wesentlichen sollen einige Umgebungsvariablen, aliase und kleine Programme ausgeführt werden. Da auf der Maschine bereits mehrere NFS-Homeverzeichnisse exisitieren, bringt eine Ergänzung in die /etc/skel/... nichts. Wo finde ich solch eine globale Konfigurationsdatei, die die o.b. Ergänzungen durchführt? Vielen Dank. Gruß, Christian -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Globale bashrc
Am Mittwoch 04 Oktober 2006 18:20 schrieb Christian Christmann: ich suche eine globale bashrc, die Ergänzungen zu den lokalen ~/.bashrc's macht. Wo finde ich solch eine globale Konfigurationsdatei, die die o.b. Ergänzungen durchführt? Am Ende von man bash Gruß Chris -- A: because it distrupts the normal process of thought Q: why is top posting frowned upon
Re: Globale bashrc
Heute (04.10.2006/20:03 Uhr) schrieb Christian Frommeyer, Am Mittwoch 04 Oktober 2006 18:20 schrieb Christian Christmann: ich suche eine globale bashrc, die Ergaenzungen zu den lokalen ~/.bashrc's macht. Wo finde ich solch eine globale Konfigurationsdatei, die die o.b. Ergaenzungen durchfuehrt? Am Ende von man bash das wäre ja dann die /etc/profile und was man da einträgt, gilt für alle shells? Gruß Chris -- Viele Gruesse, Kind regards, Jim Knuth [EMAIL PROTECTED] ICQ #277289867 -- Zufalls-Zitat -- Würdest Du mir bitte sagen, wie ich von hier aus weitergehen soll? Das hängt zum großen Teil davon ab, wohin Du möchtest, sagte die Katze. (Lewis Carroll, Alice im Wunderland) -- Der Text hat nichts mit dem Empfaenger der Mail zu tun -- Virus free. Checked by NOD32 Version 1.1789 Build 8129 04.10.2006
Re: Globale bashrc
at Mittwoch, 4. Oktober 2006 18:20 wrote Christian Christmann: Hallo, ich suche eine globale bashrc, die Ergänzungen zu den lokalen ~/.bashrc's macht. Im Wesentlichen sollen einige Umgebungsvariablen, aliase und kleine Programme ausgeführt werden. Da auf der Maschine bereits mehrere NFS-Homeverzeichnisse exisitieren, bringt eine Ergänzung in die /etc/skel/... nichts. Wo finde ich solch eine globale Konfigurationsdatei, die die o.b. Ergänzungen durchführt? /etc/profile /etc/bash.bashrc sind deine Freunde. -- Grüße, Simon
Re: Globale bashrc
Jim Knuth [EMAIL PROTECTED] wrote: das wäre ja dann die /etc/profile und was man da einträgt, gilt für alle shells? Bei Dir steht da nur /etc/profile? Deine bash(1) ist kaputt. , | FILES |/bin/bash | The bash executable |/etc/profile | The systemwide initialization file, executed for login shells |/etc/bash.bashrc | The systemwide per-interactive-shell startup file |/etc/bash.logout | The systemwide login shell cleanup file, executed when a login shell exits |~/.bash_profile | The personal initialization file, executed for login shells |~/.bashrc | The individual per-interactive-shell startup file |~/.bash_logout | The individual login shell cleanup file, executed when a login shell exits |~/.inputrc | Individual readline initialization file ` Rob -- Ein OE Benutzer trägt quasi ein Schild um den Hals. Mir ist doch egal, ob andere Probleme mit meinen Postings haben, Hauptsache ist, ich kann mal eben rumklicken. OE erfüllt für den geneigten Leser damit dieselbe Aufgabe wie die Glocke eines mittelalterlichen Leprotikers. (RSS) -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Globale bashrc
Gestern (04.10.2006/23:06 Uhr) schrieb Robert Grimm, Jim Knuth [EMAIL PROTECTED] wrote: das waere ja dann die /etc/profile und was man da eintraegt, gilt fuer alle shells? Bei Dir steht da nur /etc/profile? Deine bash(1) ist kaputt. nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen Inhalt, den root hat. Denn da funktionierts. , | FILES |/bin/bash | The bash executable |/etc/profile | The systemwide initialization file, executed for login shells |/etc/bash.bashrc | The systemwide per-interactive-shell startup file |/etc/bash.logout | The systemwide login shell cleanup file, executed when a login shell exits |~/.bash_profile | The personal initialization file, executed for login shells |~/.bashrc | The individual per-interactive-shell startup file |~/.bash_logout | The individual login shell cleanup file, executed when a login shell exits |~/.inputrc | Individual readline initialization file ` Rob -- Viele Gruesse, Kind regards, Jim Knuth [EMAIL PROTECTED] ICQ #277289867 -- Zufalls-Zitat -- Manche Leute heiraten, weil es die Eltern so wollen oder damit das Kind nicht ledig auf die Welt kommt. -- Der Text hat nichts mit dem Empfaenger der Mail zu tun -- Virus free. Checked by NOD32 Version 1.1790 Build 8132 04.10.2006
Re: Globale bashrc
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Jim Knuth wrote: nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen Usern die shell farbig haben. Kriegs nicht hin. shell farbig? nur falls du die anzeige von 'ls' meinst, dann musst du die environment variable LS_COLORS setzen. Wenn du das in der /etc/profile machst, dann sollte das auch fuer alle user funktionieren. bei mir sieht die so aus: LS_COLORS='no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.flac=01;35:*.mp3=01;35:*.mpc=01;35:*.ogg=01;35:*.wav=01;35:' gruss, Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFJFlH58nJkn8diosRA4VEAJ9bxEVRF8rySsh2vya8KTccSmXsTACgoLCq Zr2djtZF74eNrD/Pe44GwkY= =L9oo -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Globale bashrc
Heute (05.10.2006/03:00 Uhr) schrieb Jan Kechel, -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Jim Knuth wrote: nein. Steht auch alles drin. ;) Ich wuerde nur gern auch bei allen Usern die shell farbig haben. Kriegs nicht hin. shell farbig? nur falls du die anzeige von 'ls' meinst, dann musst du die environment variable LS_COLORS setzen. Wenn du das in der /etc/profile machst, dann sollte das auch fuer alle user funktionieren. und das funktioniert eben bei mir NICHT :( bei mir sieht die so aus: LS_COLORS='no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.flac=01;35:*.mp3=01;35:*.mpc=01;35:*.ogg=01;35:*.wav=01;35:' gruss, Jan -- Viele Gruesse, Kind regards, Jim Knuth [EMAIL PROTECTED] ICQ #277289867 -- Zufalls-Zitat -- Ein großer Mensch ist derjenige, der sein Kinderherz nicht verliert. (James Legge) -- Der Text hat nichts mit dem Empfaenger der Mail zu tun -- Virus free. Checked by NOD32 Version 1.1790 Build 8132 04.10.2006
Re: Globale bashrc
On Thu, Oct 05, 2006 at 02:53:02AM +0200, Jim Knuth wrote: nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen Inhalt, den root hat. Denn da funktionierts. Was genau soll farbig sein? Alles Gute Helmut H. Franke -- Avatar Chat Systeme: http://www.amiculi.net http://pgm.amoris.org -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Globale bashrc
Heute (05.10.2006/03:19 Uhr) schrieb Helmut Franke, On Thu, Oct 05, 2006 at 02:53:02AM +0200, Jim Knuth wrote: nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen Inhalt, den root hat. Denn da funktionierts. Was genau soll farbig sein? na die folder, files, etc. Unterschiedliche Farben eben Alles Gute Helmut H. Franke -- Avatar Chat Systeme: http://www.amiculi.net http://pgm.amoris.org -- Viele Gruesse, Kind regards, Jim Knuth [EMAIL PROTECTED] ICQ #277289867 -- Zufalls-Zitat -- Jedes neue Projekt macht die folgenden Entwicklungen durch: Enthusiasmus, Komplikationen, Desillusionierung, Suche nach den Schuldigen und Auszeichnung derjenigen die gar nichts getan haben. (unbekannt) -- Der Text hat nichts mit dem Empfaenger der Mail zu tun -- Virus free. Checked by NOD32 Version 1.1790 Build 8132 04.10.2006
