Dot files - Revision history

Admin at 15:59, 28 May 2011

2011-05-28T15:59:01Z

← Older revision		Revision as of 15:59, 28 May 2011
Line 76:		Line 76:

	[[Category:Unix]]		[[Category:Unix]]
	[[Category:Dot ~~Files~~]]		[[Category:Dot files]]

Admin at 15:27, 28 May 2011

2011-05-28T15:27:02Z

← Older revision		Revision as of 15:27, 28 May 2011
Line 39:		Line 39:

	= .profile =		= .profile =

			{{Main\|.profile}}

	The user analog of the <code>/etc/profile</code>, this file is useful for setting system variables, options, etc. that apply only to the user. This file does not require administrative privileges to edit, and takes precedence over any variables or options set in <code>/etc/profile</code> (since it is sourced by <code>/etc/profile</code>).		The user analog of the <code>/etc/profile</code>, this file is useful for setting system variables, options, etc. that apply only to the user. This file does not require administrative privileges to edit, and takes precedence over any variables or options set in <code>/etc/profile</code> (since it is sourced by <code>/etc/profile</code>).

	= .bashrc =		= .bashrc =

			{{Main\|.bashrc}}

	The <code>.bashrc</code> file is the place to define any bash-specific variables, settings, aliases, etc. Sometimes this can become bloated, so it can be split into sections by putting different parts into different files, and sourcing those files from the <code>.bashrc</code> file. For example, if I have a huge list of aliases (which I do), I can put those in a file in my home directory called <code>.aliases</code>, and in my <code>.bashrc</code> I put:		The <code>.bashrc</code> file is the place to define any bash-specific variables, settings, aliases, etc. Sometimes this can become bloated, so it can be split into sections by putting different parts into different files, and sourcing those files from the <code>.bashrc</code> file. For example, if I have a huge list of aliases (which I do), I can put those in a file in my home directory called <code>.aliases</code>, and in my <code>.bashrc</code> I put:
Line 58:		Line 62:

	= .bash_profile =		= .bash_profile =

			{{Main\|.bash_profile}}

	This is where (more) bash-related options, variables, etc. are set. The file is like <code>.profile</code> in that it is only sourced once per login session, but it is like <code>.bashrc</code> in that it only sets options for the bash shell. This is the place to put things like history options; you can set the maximum size of the file containing your bash history, or the maximum number of history commands for bash to remember, etc.		This is where (more) bash-related options, variables, etc. are set. The file is like <code>.profile</code> in that it is only sourced once per login session, but it is like <code>.bashrc</code> in that it only sets options for the bash shell. This is the place to put things like history options; you can set the maximum size of the file containing your bash history, or the maximum number of history commands for bash to remember, etc.
Line 67:		Line 73:
	shopt -s histappend		shopt -s histappend
	</syntaxhighlight>		</syntaxhighlight>


			[[Category:Unix]]
			[[Category:Dot Files]]

Admin at 20:44, 10 May 2011

2011-05-10T20:44:29Z

← Older revision		Revision as of 20:44, 10 May 2011
Line 8:		Line 8:
	onceperlogin [label="Once per login", shape=square]		onceperlogin [label="Once per login", shape=square]

	"~/.profile" [URL=".profile"]		"~/.profile" [URL=".profile", style=filled, fillcolor=lightblue]
	"~/.bash_profile" [URL=".bash_profile"]		"~/.bash_profile" [URL=".bash_profile", style=filled, fillcolor=lightblue]

	"~/.bashrc" [URL=".bashrc"]		"~/.bashrc" [URL=".bashrc", style=filled, fillcolor=lightblue]
	"~/.aliases" [URL=".aliases"]		"~/.aliases" [URL=".aliases", style=filled, fillcolor=lightblue]

	onceperlogin -> "/etc/profile"		onceperlogin -> "/etc/profile"

Admin at 20:43, 10 May 2011

2011-05-10T20:43:34Z

← Older revision		Revision as of 20:43, 10 May 2011
Line 7:		Line 7:
	oncepershell [label="Once per shell", shape=square]		oncepershell [label="Once per shell", shape=square]
	onceperlogin [label="Once per login", shape=square]		onceperlogin [label="Once per login", shape=square]

			"~/.profile" [URL=".profile"]
			"~/.bash_profile" [URL=".bash_profile"]

			"~/.bashrc" [URL=".bashrc"]
			"~/.aliases" [URL=".aliases"]

	onceperlogin -> "/etc/profile"		onceperlogin -> "/etc/profile"

Admin at 07:11, 24 November 2010

2010-11-24T07:11:50Z

← Older revision		Revision as of 07:11, 24 November 2010
Line 1:		Line 1:
	Dot files on Unix systems are (at first) straightforward and easy to use. However, as you dive deeper, they can get rather complicated, especially as you try to get various chains of dot-files working on various platforms.		Dot files on Unix systems are (at first) straightforward and easy to use. However, as you dive deeper, they can get rather complicated, especially as you try to get various chains of dot-files working on various platforms. Because the chain of dot files calling one another varies from one operating system to another, my general approach is to ensure a call chain of my own, or put echo statements into each dot file to figure out what the existing call chain is. This is typically (assuming only a bash shell):

			<graphviz>
			digraph G {
			rankdir="LR"

			oncepershell [label="Once per shell", shape=square]
			onceperlogin [label="Once per login", shape=square]

			onceperlogin -> "/etc/profile"
			"/etc/profile" -> "~/.profile"
			"/etc/profile" -> "~/.bash_profile"

			oncepershell -> "/etc/bashrc"
			"/etc/bashrc" -> "~/.bashrc"
			"~/.bashrc" -> "~/.aliases"
			}
			</graphviz>



	= /etc/profile =		= /etc/profile =

Admin: /* .bash_profile */

2010-11-24T07:01:48Z

.bash_profile

← Older revision		Revision as of 07:01, 24 November 2010
Line 37:		Line 37:

	<syntaxhighlight>		<syntaxhighlight>
	~~#!/bin/sh~~
	HISTFILESIZE=1000000000		HISTFILESIZE=1000000000
	HISTSIZE=1000000		HISTSIZE=1000000

Admin: /* /etc/bashrc */

2010-11-24T07:01:26Z

/etc/bashrc

← Older revision		Revision as of 07:01, 24 November 2010
Line 12:		Line 12:

	Like <code>/etc/profile</code>, this file is sourced each time the user logs in; however, it is ''also'' sourced each time the user opens a new shell (either locally or remotely). This is where you would set bash-specific settings, such as turning on tab completion (<code>source /etc/bash_completion</code>), making bash check window sizes after running commands (<code>shopt -s checkwinsize</code>), appending new history to existing history (<code>shopt -s histappend</code> and <code>shopt -s cmdhist</code>), etc.		Like <code>/etc/profile</code>, this file is sourced each time the user logs in; however, it is ''also'' sourced each time the user opens a new shell (either locally or remotely). This is where you would set bash-specific settings, such as turning on tab completion (<code>source /etc/bash_completion</code>), making bash check window sizes after running commands (<code>shopt -s checkwinsize</code>), appending new history to existing history (<code>shopt -s histappend</code> and <code>shopt -s cmdhist</code>), etc.

			= .profile =

			The user analog of the <code>/etc/profile</code>, this file is useful for setting system variables, options, etc. that apply only to the user. This file does not require administrative privileges to edit, and takes precedence over any variables or options set in <code>/etc/profile</code> (since it is sourced by <code>/etc/profile</code>).

	= .bashrc =		= .bashrc =

Admin: Created page with "Dot files on Unix systems are (at first) straightforward and easy to use. However, as you dive deeper, they can get rather complicated, especially as you try to get various chai..."

2010-11-24T06:55:30Z

Created page with "Dot files on Unix systems are (at first) straightforward and easy to use. However, as you dive deeper, they can get rather complicated, especially as you try to get various chai..."

New page

Dot files on Unix systems are (at first) straightforward and easy to use. However, as you dive deeper, they can get rather complicated, especially as you try to get various chains of dot-files working on various platforms.

= /etc/profile =

I will begin with the system-level dot files. The file doesn't have a dot in the name, but it's still a dot file due to the syntax.

Any time any user logs in, their shell will source <code>/etc/profile</code>. The <code>/etc/profile</code> file contains initializations, environmental variables, and other initialization-related things that should be performed once each time the user logs in. This will contain really top-level stuff, like the name of the machine, the shell prompt text for all users and for super-users (sudo), etc.

<code>/etc/profile</code> should also source <code>~/.profile</code> (the file named <code>.profile</code> located in each users' home directory), and <code>/etc/bashrc</code> (or something like this - it depends on your operating system and your shell).

= /etc/bashrc =

Like <code>/etc/profile</code>, this file is sourced each time the user logs in; however, it is ''also'' sourced each time the user opens a new shell (either locally or remotely). This is where you would set bash-specific settings, such as turning on tab completion (<code>source /etc/bash_completion</code>), making bash check window sizes after running commands (<code>shopt -s checkwinsize</code>), appending new history to existing history (<code>shopt -s histappend</code> and <code>shopt -s cmdhist</code>), etc.

= .bashrc =

The <code>.bashrc</code> file is the place to define any bash-specific variables, settings, aliases, etc. Sometimes this can become bloated, so it can be split into sections by putting different parts into different files, and sourcing those files from the <code>.bashrc</code> file. For example, if I have a huge list of aliases (which I do), I can put those in a file in my home directory called <code>.aliases</code>, and in my <code>.bashrc</code> I put:

<syntaxhighlight lang="bash">
source ~/.aliases
</syntaxhighlight>

and in my <code>.aliases</code> I have my aliases defined:

<syntaxhighlight lang="bash">
alias back='cd $OLDPWD'
alias u='cd ..'
</syntaxhighlight>

= .bash_profile =

This is where (more) bash-related options, variables, etc. are set. The file is like <code>.profile</code> in that it is only sourced once per login session, but it is like <code>.bashrc</code> in that it only sets options for the bash shell. This is the place to put things like history options; you can set the maximum size of the file containing your bash history, or the maximum number of history commands for bash to remember, etc.

<syntaxhighlight>
#!/bin/sh
HISTFILESIZE=1000000000
HISTSIZE=1000000
HISTTIMEFORMAT=': %Y-%m-%d_%H:%M:%S; '
shopt -s histappend
</syntaxhighlight>