https://wiki.archlinux.jp/api.php?action=feedcontributions&feedformat=atom&user=%E3%81%AF%E3%81%A4%E3%81%9BArchWiki - 利用者の投稿記録 [ja]2026-04-23T08:46:19Z利用者の投稿記録MediaWiki 1.44.3https://wiki.archlinux.jp/index.php?title=Fish&diff=3812Fish2015-10-25T07:51:26Z<p>はつせ: /* 設定 */</p>
<hr />
<div>{{lowercase title}}<br />
[[Category:コマンドシェル]]<br />
[[de:Fish]]<br />
[[en:Fish]]<br />
[[ru:Fish]]<br />
'''fish''' ('''friendly interactive shell''') は主に対話的に使用することを意図されたユーザフレンドリーなコマンドラインシェルです。<br />
<br />
== インストール ==<br />
<br />
[[公式リポジトリ]]より、[http://fishshell.com/ 主流フォーク] の安定版 {{Pkg|fish}} パッケージを[[pacman|インストール]]できます。<br />
<br />
最新の開発版は [[AUR]] より {{AUR|fish-shell-git}}{{Broken package link|{{aur-mirror|fish-shell-git}}}} を[[pacman|インストール]]します。 <br />
<br />
2011年に [https://github.com/liljencrantz オリジナルの開発者] による [http://www.mail-archive.com/fish-users@lists.sourceforge.net/msg02893.html 開発が中止された] 従来のバージョンは [[AUR]] より {{AUR|fish-git}} を[[pacman|インストール]]します。<br />
<br />
fish をデフォルトシェルにするには、{{ic|chsh -s /usr/bin/fish}} を実行します。<br />
<br />
== 入出力 ==<br />
<br />
=== File descriptors ===<br />
Like other shells, fish lets you redirect input/output streams. This is useful when using text files to save programs output or errors, or when using text files as input. Most programs use three input/output streams, represented by numbers called file descriptors (FD). These are:<br />
<br />
* Standard input (FD 0), used for reading (keyboard by default).<br />
* Standard output (FD 1), used for writing (screen by default).<br />
* Standard error (FD 2), used for displaying errors and warnings (screen by default).<br />
<br />
=== リダイレクト ===<br />
Any file descriptor can be directed to other files through a mechanism called redirection:<br />
<br />
{{bc|''Redirecting standard input:''<br />
$ command < source_file<br />
<br />
''Redirecting standard output:''<br />
$ command > destination<br />
<br />
''Appending standard output to an existing file:''<br />
$ command >> destination<br />
<br />
''Redirecting standard error:''<br />
$ command ^ destination<br />
<br />
''Appending standard error to an existing file:''<br />
$ command ^^ destination}}<br />
<br />
You can use one of the following as {{ic|destination}}:<br />
<br />
* A filename (the output will be written to the specified file).<br />
* An {{ic|&}} followed by the number of another file descriptor. The output will be written to the other file descriptor.<br />
* An {{ic|&}} followed by a {{ic|-}} sign. The output will not be written anywhere.<br />
<br />
Examples:<br />
{{bc|''Redirecting standard output to a file:''<br />
$ command > destination_file.txt<br />
<br />
''Redirecting both standard output and standard error to the same file:''<br />
$ command > destination_file.txt ^ &1<br />
<br />
''Silencing standard output:''<br />
$ command > &-}}<br />
<br />
=== パイプ ===<br />
<br />
You can redirect standard output of one command to standard input of the next command. This is done by separating the commands by the pipe character ({{ic|<nowiki>|</nowiki>}}). Example:<br />
<br />
cat example.txt | head<br />
<br />
You can redirect other file descriptors to the pipe (besides standard output). The next example shows how to use standard error of one command as standard input of another command, prepending standard error file descriptor's number and {{ic|>}} to the pipe:<br />
<br />
$ command 2>| less<br />
<br />
This will run {{ic|command}} and redirect its standard error to the {{ic|less}} command.<br />
<br />
== 設定 ==<br />
fishのユーザ設定ファイルは {{ic|~/.config/fish/config.fish}} に位置しています。<br />
<br />
{{ic|.bashrc}} と同じように、ターミナルが開かれる時に実行/定義されるコマンド、関数を追加します。<br />
<br />
=== ウェブインターフェイス ===<br />
<br />
fish のプロンプトとターミナルの色はウェブインターフェイスで対話的に設定できます:<br />
<br />
fish_config<br />
<br />
選択した設定は、個人用の設定ファイルに書き込まれます。また、定義された関数と履歴を表示することができます<br />
<br />
=== プロンプト ===<br />
<br />
If you would like fish to display the branch and dirty status when you are in a git directory, you can add the following to your {{ic|~/.config/fish/config.fish}}:<br />
{{bc|<nowiki><br />
# fish git prompt<br />
set __fish_git_prompt_showdirtystate 'yes'<br />
set __fish_git_prompt_showstashstate 'yes'<br />
set __fish_git_prompt_showupstream 'yes'<br />
set __fish_git_prompt_color_branch yellow<br />
<br />
# Status Chars<br />
set __fish_git_prompt_char_dirtystate '⚡'<br />
set __fish_git_prompt_char_stagedstate '→'<br />
set __fish_git_prompt_char_stashstate '↩'<br />
set __fish_git_prompt_char_upstream_ahead '↑'<br />
set __fish_git_prompt_char_upstream_behind '↓'<br />
<br />
function fish_prompt<br />
set last_status $status<br />
set_color $fish_color_cwd<br />
printf '%s' (prompt_pwd)<br />
set_color normal<br />
printf '%s ' (__fish_git_prompt)<br />
set_color normal<br />
end<br />
</nowiki>}}<br />
<br />
=== コマンド補完 ===<br />
<br />
fish は man ページから自動補完を生成できます。{{ic|~/.config/fish/generated_completions/}} に補完が書き込まれており、以下を呼び出すことによって生成することができます:<br />
<br />
fish_update_completions<br />
<br />
また、独自の補完を {{ic|~/.config/fish/completions/}} に定義できます。{{ic|/usr/share/fish/completions/}} でいくつかの例を見ることができます。<br />
<br />
fish の開発元のポリシーが、上流の tarball に存在する補完を全て含めるというものなので ''pacman'', ''pacman-key'', ''makepkg'', ''cower'', ''pbget'', ''pacmatic'' などの Arch Linux 固有のコマンドの文脈に沿った補完も fish に含まれています。メモリ管理が賢いために、リソースに悪影響を与えることはありません。<br />
<br />
=== /etc/profile と ~/.profile の互換性 ===<br />
<br />
Since standard POSIX {{ic|sh}} syntax is not compatible with fish, fish will not be able to source {{ic|/etc/profile}} (and thus all {{ic|*.sh}} in {{ic|/etc/profile.d}}) and {{ic|~/.profile}}<br />
<br />
If you want fish to source those files, install {{Pkg|dash}} and add this line to your {{ic|config.fish}}:<br />
env -i HOME=$HOME dash -l -c printenv | sed -e '/PATH/s/:/ /g;s/=/ /;s/^/set -x /' | source<br />
<br />
an alternative variant will save you one executable invocation by using a builtin command:<br />
env -i HOME=$HOME dash -l -c 'export -p' | sed -e "/PATH/s/'//g;/PATH/s/:/ /g;s/=/ /;s/^export/set -x/" | source<br />
<br />
==Tips and Tricks==<br />
===History Substitution===<br />
Fish does not implement history substitution (e.g. {{ic|sudo !!}}), and the fish developers have said that they [http://fishshell.com/docs/current/faq.html#faq-history do not plan to]. Still, this is an essential piece of many users' workflow. Reddit user, [http://www.reddit.com/u/crossroads1112 crossroads1112], created a function that regains some of the functionality of history substitution and with another syntax. The function is on [https://gist.github.com/crossroads1112/77badb2c3455e23b873b github] and instructions are included as comments in it. There is a [https://gist.github.com/b-/981892a65837ab0a387e forked version] that is closer to the original syntax and allows for {{ic|command !!}} if you specify the command in the helper function.<br />
<br />
== トラブルシューティング ==<br />
<br />
In Arch, there are a lot of shell scripts written for Bash, and these have not been translated to fish. It is advisable not to set fish as your default shell because of this. The best option is to open your terminal emulator with a command line option that executes fish. For most terminals this is the {{ic|-e}} switch, so for example, to open gnome-terminal using fish, change your shortcut to use:<br />
<br />
gnome-terminal -e fish<br />
<br />
With LilyTerm and other light terminal emulators that do not support setting the shell it would look like this:<br />
<br />
SHELL=/usr/bin/fish lilyterm<br />
<br />
Another option is to set fish as the default shell for the terminal in the terminal's configuration or for a terminal profile if your terminal emulator has a profiles feature. This is contrast to changing the default shell for the user which would cause the above mentioned problem.<br />
<br />
To set fish as the shell started in tmux, put this into your {{ic|~/.tmux.conf}}:<br />
<br />
set-option -g default-shell "/usr/bin/fish"<br />
<br />
Not setting fish as system wide default allows the arch scripts to run on startup, ensure the environment variables are set correctly, and generally reduces the issues associated with using a non-Bash compatible terminal like fish.<br />
<br />
If you decide to set fish as your default shell, you may find that you no longer have very much in your path.<br />
You can add a section to your {{ic|~/.config/fish/config.fish}} file that will set your path correctly on login. This is much like {{ic|.profile}} or {{ic|.bash_profile}} as it is only executed for login shells.<br />
<br />
{{bc|<br />
if status --is-login<br />
set PATH $PATH /usr/bin /sbin<br />
end<br />
}}<br />
<br />
Note that you will need to manually add various other environment variables, such as {{ic|$MOZ_PLUGIN_PATH}}. It is a huge amount of work to get a seamless experience with fish as your default shell.<br />
<br />
=== su で bash が起動する ===<br />
<br />
su で bash が起動する場合 (Bash がデフォルトシェルのため)、fish に関数を定義してください:<br />
<br />
$ funced su<br />
function su<br />
/bin/su --shell=/usr/bin/fish $argv<br />
end<br />
$ funcsave su<br />
<br />
=== ログイン時に X を起動 ===<br />
<br />
{{ic|~/.config/fish/config.fish}} の一番下に以下を追加します:<br />
<br />
{{bc|1=<nowiki><br />
# start X at login<br />
if status --is-login<br />
if test -z "$DISPLAY" -a $XDG_VTNR -eq 1<br />
exec startx -- -keeptty<br />
end<br />
end<br />
</nowiki>}}<br />
<br />
{{Note|fish 使用時に {{ic|startx}} が {{ic|-keeptty}} フラグを必要とする理由については [https://github.com/fish-shell/fish-shell/issues/1772 この記事] を参照してください。}}<br />
<br />
== 参照 ==<br />
<br />
* http://fishshell.com/ - ホームページ<br />
* http://fishshell.com/docs/2.1/index.html - ドキュメント</div>はつせhttps://wiki.archlinux.jp/index.php?title=Fish&diff=3790Fish2015-10-24T09:41:01Z<p>はつせ: </p>
<hr />
<div>{{lowercase title}}<br />
[[Category:Command shells]]<br />
[[de:Fish]]<br />
[[en:Fish]]<br />
[[ru:Fish]]<br />
'''fish''' ('''friendly interactive shell''')は主に対話的に使用することを意図されたユーザフレンドリーなコマンドラインシェルです。<br />
<br />
== インストール ==<br />
<br />
[[公式リポジトリ]]より、[http://fishshell.com/ 主流fork]の安定版{{Pkg|fish}}パッケージを[[pacman|インストール]]できます。<br />
<br />
最新の開発版は[[AUR]]より {{AUR|fish-shell-git}}{{Broken package link|{{aur-mirror|fish-shell-git}}}}を[[pacman|インストール]]します。 <br />
<br />
2011年に[https://github.com/liljencrantz オリジナルの開発者]によって[http://www.mail-archive.com/fish-users@lists.sourceforge.net/msg02893.html 中止された]従来のバージョンは[[AUR]]より<br />
{{AUR|fish-git}}を[[pacman|インストール]]します。<br />
<br />
fishをデフォルトシェルにするには、{{ic|chsh -s /usr/bin/fish}}を実行します。<br />
<br />
== 入出力 ==<br />
<br />
=== File descriptors ===<br />
Like other shells, fish lets you redirect input/output streams. This is useful when using text files to save programs output or errors, or when using text files as input. Most programs use three input/output streams, represented by numbers called file descriptors (FD). These are:<br />
<br />
* Standard input (FD 0), used for reading (keyboard by default).<br />
* Standard output (FD 1), used for writing (screen by default).<br />
* Standard error (FD 2), used for displaying errors and warnings (screen by default).<br />
<br />
=== リダイレクト ===<br />
Any file descriptor can be directed to other files through a mechanism called redirection:<br />
<br />
{{bc|''Redirecting standard input:''<br />
$ command < source_file<br />
<br />
''Redirecting standard output:''<br />
$ command > destination<br />
<br />
''Appending standard output to an existing file:''<br />
$ command >> destination<br />
<br />
''Redirecting standard error:''<br />
$ command ^ destination<br />
<br />
''Appending standard error to an existing file:''<br />
$ command ^^ destination}}<br />
<br />
You can use one of the following as {{ic|destination}}:<br />
<br />
* A filename (the output will be written to the specified file).<br />
* An {{ic|&}} followed by the number of another file descriptor. The output will be written to the other file descriptor.<br />
* An {{ic|&}} followed by a {{ic|-}} sign. The output will not be written anywhere.<br />
<br />
Examples:<br />
{{bc|''Redirecting standard output to a file:''<br />
$ command > destination_file.txt<br />
<br />
''Redirecting both standard output and standard error to the same file:''<br />
$ command > destination_file.txt ^ &1<br />
<br />
''Silencing standard output:''<br />
$ command > &-}}<br />
<br />
=== パイプ ===<br />
<br />
You can redirect standard output of one command to standard input of the next command. This is done by separating the commands by the pipe character ({{ic|<nowiki>|</nowiki>}}). Example:<br />
<br />
cat example.txt | head<br />
<br />
You can redirect other file descriptors to the pipe (besides standard output). The next example shows how to use standard error of one command as standard input of another command, prepending standard error file descriptor's number and {{ic|>}} to the pipe:<br />
<br />
$ command 2>| less<br />
<br />
This will run {{ic|command}} and redirect its standard error to the {{ic|less}} command.<br />
<br />
== Configuration ==<br />
<br />
User configurations for fish are located at {{ic|~/.config/fish/config.fish}}. Adding commands or functions to the file will execute/define them when opening a terminal, similar to {{ic|.bashrc}}.<br />
<br />
=== Web interface ===<br />
<br />
The fish prompt and terminal colors can be set with the interactive web interface:<br />
<br />
fish_config<br />
<br />
Selected settings are written to your personal configuration file. You can also view defined functions and your history.<br />
<br />
=== プロンプト ===<br />
<br />
If you would like fish to display the branch and dirty status when you are in a git directory, you can add the following to your {{ic|~/.config/fish/config.fish}}:<br />
{{bc|<nowiki><br />
# fish git prompt<br />
set __fish_git_prompt_showdirtystate 'yes'<br />
set __fish_git_prompt_showstashstate 'yes'<br />
set __fish_git_prompt_showupstream 'yes'<br />
set __fish_git_prompt_color_branch yellow<br />
<br />
# Status Chars<br />
set __fish_git_prompt_char_dirtystate '⚡'<br />
set __fish_git_prompt_char_stagedstate '→'<br />
set __fish_git_prompt_char_stashstate '↩'<br />
set __fish_git_prompt_char_upstream_ahead '↑'<br />
set __fish_git_prompt_char_upstream_behind '↓'<br />
<br />
function fish_prompt<br />
set last_status $status<br />
set_color $fish_color_cwd<br />
printf '%s' (prompt_pwd)<br />
set_color normal<br />
printf '%s ' (__fish_git_prompt)<br />
set_color normal<br />
end<br />
</nowiki>}}<br />
<br />
=== コマンド補完 ===<br />
<br />
fishはmanページより自動補完を生成できます。{{ic|~/.config/fish/generated_completions/}} に補完が書き込まれており、以下を呼び出すことによって生成することができます。<br />
<br />
fish_update_completions<br />
<br />
また、独自の補完を {{ic|~/.config/fish/completions/}}に定義できます。{{ic|/usr/share/fish/completions/}}でいくつかの例を見ることができる。<br />
<br />
fish開発のポリシーが上流のtarball内に存在する補完を全て含んで以来、''pacman'', ''pacman-key'', ''makepkg'', ''cower'', ''pbget'', ''pacmatic''のようなArch Linux固有のコマンドのための文脈補完がfishに含まれています。メモリ管理は、リソースへの悪影響を回避するのに十分賢いです。<br />
<br />
=== /etc/profile and ~/.profile compatibility ===<br />
<br />
Since standard POSIX {{ic|sh}} syntax is not compatible with fish, fish will not be able to source {{ic|/etc/profile}} (and thus all {{ic|*.sh}} in {{ic|/etc/profile.d}}) and {{ic|~/.profile}}<br />
<br />
If you want fish to source those files, install {{Pkg|dash}} and add this line to your {{ic|config.fish}}:<br />
env -i HOME=$HOME dash -l -c printenv | sed -e '/PATH/s/:/ /g;s/=/ /;s/^/set -x /' | source<br />
<br />
an alternative variant will save you one executable invocation by using a builtin command:<br />
env -i HOME=$HOME dash -l -c 'export -p' | sed -e "/PATH/s/'//g;/PATH/s/:/ /g;s/=/ /;s/^export/set -x/" | source<br />
<br />
==Tips and Tricks==<br />
===History Substitution===<br />
Fish does not implement history substitution (e.g. {{ic|sudo !!}}), and the fish developers have said that they [http://fishshell.com/docs/current/faq.html#faq-history do not plan to]. Still, this is an essential piece of many users' workflow. Reddit user, [http://www.reddit.com/u/crossroads1112 crossroads1112], created a function that regains some of the functionality of history substitution and with another syntax. The function is on [https://gist.github.com/crossroads1112/77badb2c3455e23b873b github] and instructions are included as comments in it. There is a [https://gist.github.com/b-/981892a65837ab0a387e forked version] that is closer to the original syntax and allows for {{ic|command !!}} if you specify the command in the helper function.<br />
<br />
== トラブルシューティング ==<br />
<br />
{{Accuracy|Changing the default shell should not interfere with the execution of shell scripts, so long as they begin with a proper [https://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang line].}}<br />
<br />
In Arch, there are a lot of shell scripts written for Bash, and these have not been translated to fish. It is advisable not to set fish as your default shell because of this. The best option is to open your terminal emulator with a command line option that executes fish. For most terminals this is the {{ic|-e}} switch, so for example, to open gnome-terminal using fish, change your shortcut to use:<br />
<br />
gnome-terminal -e fish<br />
<br />
With LilyTerm and other light terminal emulators that do not support setting the shell it would look like this:<br />
<br />
SHELL=/usr/bin/fish lilyterm<br />
<br />
Another option is to set fish as the default shell for the terminal in the terminal's configuration or for a terminal profile if your terminal emulator has a profiles feature. This is contrast to changing the default shell for the user which would cause the above mentioned problem.<br />
<br />
To set fish as the shell started in tmux, put this into your {{ic|~/.tmux.conf}}:<br />
<br />
set-option -g default-shell "/usr/bin/fish"<br />
<br />
Not setting fish as system wide default allows the arch scripts to run on startup, ensure the environment variables are set correctly, and generally reduces the issues associated with using a non-Bash compatible terminal like fish.<br />
<br />
If you decide to set fish as your default shell, you may find that you no longer have very much in your path.<br />
You can add a section to your {{ic|~/.config/fish/config.fish}} file that will set your path correctly on login. This is much like {{ic|.profile}} or {{ic|.bash_profile}} as it is only executed for login shells.<br />
<br />
{{bc|<br />
if status --is-login<br />
set PATH $PATH /usr/bin /sbin<br />
end<br />
}}<br />
<br />
Note that you will need to manually add various other environment variables, such as {{ic|$MOZ_PLUGIN_PATH}}. It is a huge amount of work to get a seamless experience with fish as your default shell.<br />
<br />
=== suでbashが起動 ===<br />
<br />
もし、suでbashが起動する場合(Bashがデフォルトシェルのため), fishに関数を定義します。<br />
<br />
$ funced su<br />
function su<br />
/bin/su --shell=/usr/bin/fish $argv<br />
end<br />
$ funcsave su<br />
<br />
=== ログイン時にXを起動 ===<br />
<br />
{{ic|~/.config/fish/config.fish}}の一番下に以下を追加します。<br />
<br />
{{bc|1=<nowiki><br />
# start X at login<br />
if status --is-login<br />
if test -z "$DISPLAY" -a $XDG_VTNR -eq 1<br />
exec startx -- -keeptty<br />
end<br />
end<br />
</nowiki>}}<br />
<br />
{{Note|fish使用時に{{ic|startx}}が{{ic|-keeptty}}フラグを必要とする理由については[https://github.com/fish-shell/fish-shell/issues/1772 この記事]を参照してください。}}<br />
<br />
== 参照 ==<br />
<br />
* http://fishshell.com/ - ホームページ<br />
* http://fishshell.com/docs/2.1/index.html - ドキュメント</div>はつせhttps://wiki.archlinux.jp/index.php?title=Fish&diff=3789Fish2015-10-24T08:12:18Z<p>はつせ: </p>
<hr />
<div>{{lowercase title}}<br />
[[Category:Command shells]]<br />
[[de:Fish]]<br />
[[en:Fish]]<br />
[[ru:Fish]]<br />
'''fish''' ('''friendly interactive shell''')は主に対話的に使用することを意図されたユーザフレンドリーなコマンドラインシェルです。<br />
<br />
== インストール ==<br />
<br />
[[公式リポジトリ]]より、[http://fishshell.com/ 主流fork]の安定版{{Pkg|fish}}パッケージを[[pacman|インストール]]できます。<br />
<br />
最新の開発版は[[AUR]]より {{AUR|fish-shell-git}}{{Broken package link|{{aur-mirror|fish-shell-git}}}}を[[pacman|インストール]]します。 <br />
<br />
2011年に[https://github.com/liljencrantz オリジナルの開発者]によって[http://www.mail-archive.com/fish-users@lists.sourceforge.net/msg02893.html 中止された]従来のバージョンは[[AUR]]より<br />
{{AUR|fish-git}}を[[pacman|インストール]]します。<br />
<br />
fishをデフォルトシェルにするには、{{ic|chsh -s /usr/bin/fish}}を実行します。<br />
<br />
== 入力/出力 ==<br />
<br />
=== File descriptors ===<br />
Like other shells, fish lets you redirect input/output streams. This is useful when using text files to save programs output or errors, or when using text files as input. Most programs use three input/output streams, represented by numbers called file descriptors (FD). These are:<br />
<br />
* Standard input (FD 0), used for reading (keyboard by default).<br />
* Standard output (FD 1), used for writing (screen by default).<br />
* Standard error (FD 2), used for displaying errors and warnings (screen by default).<br />
<br />
=== リダイレクト ===<br />
Any file descriptor can be directed to other files through a mechanism called redirection:<br />
<br />
{{bc|''Redirecting standard input:''<br />
$ command < source_file<br />
<br />
''Redirecting standard output:''<br />
$ command > destination<br />
<br />
''Appending standard output to an existing file:''<br />
$ command >> destination<br />
<br />
''Redirecting standard error:''<br />
$ command ^ destination<br />
<br />
''Appending standard error to an existing file:''<br />
$ command ^^ destination}}<br />
<br />
You can use one of the following as {{ic|destination}}:<br />
<br />
* A filename (the output will be written to the specified file).<br />
* An {{ic|&}} followed by the number of another file descriptor. The output will be written to the other file descriptor.<br />
* An {{ic|&}} followed by a {{ic|-}} sign. The output will not be written anywhere.<br />
<br />
Examples:<br />
{{bc|''Redirecting standard output to a file:''<br />
$ command > destination_file.txt<br />
<br />
''Redirecting both standard output and standard error to the same file:''<br />
$ command > destination_file.txt ^ &1<br />
<br />
''Silencing standard output:''<br />
$ command > &-}}<br />
<br />
=== パイプ ===<br />
<br />
You can redirect standard output of one command to standard input of the next command. This is done by separating the commands by the pipe character ({{ic|<nowiki>|</nowiki>}}). Example:<br />
<br />
cat example.txt | head<br />
<br />
You can redirect other file descriptors to the pipe (besides standard output). The next example shows how to use standard error of one command as standard input of another command, prepending standard error file descriptor's number and {{ic|>}} to the pipe:<br />
<br />
$ command 2>| less<br />
<br />
This will run {{ic|command}} and redirect its standard error to the {{ic|less}} command.<br />
<br />
== Configuration ==<br />
<br />
User configurations for fish are located at {{ic|~/.config/fish/config.fish}}. Adding commands or functions to the file will execute/define them when opening a terminal, similar to {{ic|.bashrc}}.<br />
<br />
=== Web interface ===<br />
<br />
The fish prompt and terminal colors can be set with the interactive web interface:<br />
<br />
fish_config<br />
<br />
Selected settings are written to your personal configuration file. You can also view defined functions and your history.<br />
<br />
=== プロンプト ===<br />
<br />
If you would like fish to display the branch and dirty status when you are in a git directory, you can add the following to your {{ic|~/.config/fish/config.fish}}:<br />
{{bc|<nowiki><br />
# fish git prompt<br />
set __fish_git_prompt_showdirtystate 'yes'<br />
set __fish_git_prompt_showstashstate 'yes'<br />
set __fish_git_prompt_showupstream 'yes'<br />
set __fish_git_prompt_color_branch yellow<br />
<br />
# Status Chars<br />
set __fish_git_prompt_char_dirtystate '⚡'<br />
set __fish_git_prompt_char_stagedstate '→'<br />
set __fish_git_prompt_char_stashstate '↩'<br />
set __fish_git_prompt_char_upstream_ahead '↑'<br />
set __fish_git_prompt_char_upstream_behind '↓'<br />
<br />
function fish_prompt<br />
set last_status $status<br />
set_color $fish_color_cwd<br />
printf '%s' (prompt_pwd)<br />
set_color normal<br />
printf '%s ' (__fish_git_prompt)<br />
set_color normal<br />
end<br />
</nowiki>}}<br />
<br />
=== Command completion ===<br />
<br />
fish can generate autocompletions from man pages. Completions are written to {{ic|~/.config/fish/generated_completions/}} and can be generated by calling:<br />
<br />
fish_update_completions<br />
<br />
You can also define your own completions in {{ic|~/.config/fish/completions/}}. See {{ic|/usr/share/fish/completions/}} for a few examples.<br />
<br />
Context-aware completions for Arch Linux-specific commands like ''pacman'', ''pacman-key'', ''makepkg'', ''cower'', ''pbget'', ''pacmatic'' are built into fish, since the policy of the fish development is to include all the existent completions in the upstream tarball. The memory management is clever enough to avoid any negative impact on resources.<br />
<br />
=== /etc/profile and ~/.profile compatibility ===<br />
<br />
Since standard POSIX {{ic|sh}} syntax is not compatible with fish, fish will not be able to source {{ic|/etc/profile}} (and thus all {{ic|*.sh}} in {{ic|/etc/profile.d}}) and {{ic|~/.profile}}<br />
<br />
If you want fish to source those files, install {{Pkg|dash}} and add this line to your {{ic|config.fish}}:<br />
env -i HOME=$HOME dash -l -c printenv | sed -e '/PATH/s/:/ /g;s/=/ /;s/^/set -x /' | source<br />
<br />
an alternative variant will save you one executable invocation by using a builtin command:<br />
env -i HOME=$HOME dash -l -c 'export -p' | sed -e "/PATH/s/'//g;/PATH/s/:/ /g;s/=/ /;s/^export/set -x/" | source<br />
<br />
==Tips and Tricks==<br />
===History Substitution===<br />
Fish does not implement history substitution (e.g. {{ic|sudo !!}}), and the fish developers have said that they [http://fishshell.com/docs/current/faq.html#faq-history do not plan to]. Still, this is an essential piece of many users' workflow. Reddit user, [http://www.reddit.com/u/crossroads1112 crossroads1112], created a function that regains some of the functionality of history substitution and with another syntax. The function is on [https://gist.github.com/crossroads1112/77badb2c3455e23b873b github] and instructions are included as comments in it. There is a [https://gist.github.com/b-/981892a65837ab0a387e forked version] that is closer to the original syntax and allows for {{ic|command !!}} if you specify the command in the helper function.<br />
<br />
== トラブルシューティング ==<br />
<br />
{{Accuracy|Changing the default shell should not interfere with the execution of shell scripts, so long as they begin with a proper [https://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang line].}}<br />
<br />
In Arch, there are a lot of shell scripts written for Bash, and these have not been translated to fish. It is advisable not to set fish as your default shell because of this. The best option is to open your terminal emulator with a command line option that executes fish. For most terminals this is the {{ic|-e}} switch, so for example, to open gnome-terminal using fish, change your shortcut to use:<br />
<br />
gnome-terminal -e fish<br />
<br />
With LilyTerm and other light terminal emulators that do not support setting the shell it would look like this:<br />
<br />
SHELL=/usr/bin/fish lilyterm<br />
<br />
Another option is to set fish as the default shell for the terminal in the terminal's configuration or for a terminal profile if your terminal emulator has a profiles feature. This is contrast to changing the default shell for the user which would cause the above mentioned problem.<br />
<br />
To set fish as the shell started in tmux, put this into your {{ic|~/.tmux.conf}}:<br />
<br />
set-option -g default-shell "/usr/bin/fish"<br />
<br />
Not setting fish as system wide default allows the arch scripts to run on startup, ensure the environment variables are set correctly, and generally reduces the issues associated with using a non-Bash compatible terminal like fish.<br />
<br />
If you decide to set fish as your default shell, you may find that you no longer have very much in your path.<br />
You can add a section to your {{ic|~/.config/fish/config.fish}} file that will set your path correctly on login. This is much like {{ic|.profile}} or {{ic|.bash_profile}} as it is only executed for login shells.<br />
<br />
{{bc|<br />
if status --is-login<br />
set PATH $PATH /usr/bin /sbin<br />
end<br />
}}<br />
<br />
Note that you will need to manually add various other environment variables, such as {{ic|$MOZ_PLUGIN_PATH}}. It is a huge amount of work to get a seamless experience with fish as your default shell.<br />
<br />
=== suでbashが起動 ===<br />
<br />
もし、suでbashが起動する場合(Bashがデフォルトシェルのため), fishに関数を定義します。<br />
<br />
$ funced su<br />
function su<br />
/bin/su --shell=/usr/bin/fish $argv<br />
end<br />
$ funcsave su<br />
<br />
=== ログイン時にXを起動 ===<br />
<br />
{{ic|~/.config/fish/config.fish}}の一番下に以下を追加します。<br />
<br />
{{bc|1=<nowiki><br />
# start X at login<br />
if status --is-login<br />
if test -z "$DISPLAY" -a $XDG_VTNR -eq 1<br />
exec startx -- -keeptty<br />
end<br />
end<br />
</nowiki>}}<br />
<br />
{{Note|fish使用時に{{ic|startx}}が{{ic|-keeptty}}フラグを必要とする理由については[https://github.com/fish-shell/fish-shell/issues/1772 この記事]を参照してください。}}<br />
<br />
== 参照 ==<br />
<br />
* http://fishshell.com/ - ホームページ<br />
* http://fishshell.com/docs/2.1/index.html - ドキュメント</div>はつせhttps://wiki.archlinux.jp/index.php?title=Fish&diff=3788Fish2015-10-24T08:11:50Z<p>はつせ: </p>
<hr />
<div>{{lowercase title}}<br />
[[Category:Command shells]]<br />
[[de:Fish]]<br />
[[en:Fish]]<br />
[[ru:Fish]]<br />
'''fish''' ('''friendly interactive shell''')は主に対話的に使用することを意図されたユーザフレンドリーなコマンドラインシェルです。<br />
<br />
== インストール ==<br />
<br />
[[公式リポジトリ]]より、[http://fishshell.com/ 主流fork]の安定版{{Pkg|fish}}パッケージを[[pacman|インストール]]できます。<br />
<br />
最新の開発版は[[AUR]]より {{AUR|fish-shell-git}}{{Broken package link|{{aur-mirror|fish-shell-git}}}} を[[pacman|インストール]]します。 <br />
<br />
2011年に[https://github.com/liljencrantz オリジナルの開発者]によって[http://www.mail-archive.com/fish-users@lists.sourceforge.net/msg02893.html 中止された]従来のバージョンは[[AUR]]より<br />
{{AUR|fish-git}}を[[pacman|インストール]]します。<br />
<br />
fishをデフォルトシェルにするには、{{ic|chsh -s /usr/bin/fish}}を実行します。<br />
<br />
== 入力/出力 ==<br />
<br />
=== File descriptors ===<br />
Like other shells, fish lets you redirect input/output streams. This is useful when using text files to save programs output or errors, or when using text files as input. Most programs use three input/output streams, represented by numbers called file descriptors (FD). These are:<br />
<br />
* Standard input (FD 0), used for reading (keyboard by default).<br />
* Standard output (FD 1), used for writing (screen by default).<br />
* Standard error (FD 2), used for displaying errors and warnings (screen by default).<br />
<br />
=== リダイレクト ===<br />
Any file descriptor can be directed to other files through a mechanism called redirection:<br />
<br />
{{bc|''Redirecting standard input:''<br />
$ command < source_file<br />
<br />
''Redirecting standard output:''<br />
$ command > destination<br />
<br />
''Appending standard output to an existing file:''<br />
$ command >> destination<br />
<br />
''Redirecting standard error:''<br />
$ command ^ destination<br />
<br />
''Appending standard error to an existing file:''<br />
$ command ^^ destination}}<br />
<br />
You can use one of the following as {{ic|destination}}:<br />
<br />
* A filename (the output will be written to the specified file).<br />
* An {{ic|&}} followed by the number of another file descriptor. The output will be written to the other file descriptor.<br />
* An {{ic|&}} followed by a {{ic|-}} sign. The output will not be written anywhere.<br />
<br />
Examples:<br />
{{bc|''Redirecting standard output to a file:''<br />
$ command > destination_file.txt<br />
<br />
''Redirecting both standard output and standard error to the same file:''<br />
$ command > destination_file.txt ^ &1<br />
<br />
''Silencing standard output:''<br />
$ command > &-}}<br />
<br />
=== パイプ ===<br />
<br />
You can redirect standard output of one command to standard input of the next command. This is done by separating the commands by the pipe character ({{ic|<nowiki>|</nowiki>}}). Example:<br />
<br />
cat example.txt | head<br />
<br />
You can redirect other file descriptors to the pipe (besides standard output). The next example shows how to use standard error of one command as standard input of another command, prepending standard error file descriptor's number and {{ic|>}} to the pipe:<br />
<br />
$ command 2>| less<br />
<br />
This will run {{ic|command}} and redirect its standard error to the {{ic|less}} command.<br />
<br />
== Configuration ==<br />
<br />
User configurations for fish are located at {{ic|~/.config/fish/config.fish}}. Adding commands or functions to the file will execute/define them when opening a terminal, similar to {{ic|.bashrc}}.<br />
<br />
=== Web interface ===<br />
<br />
The fish prompt and terminal colors can be set with the interactive web interface:<br />
<br />
fish_config<br />
<br />
Selected settings are written to your personal configuration file. You can also view defined functions and your history.<br />
<br />
=== プロンプト ===<br />
<br />
If you would like fish to display the branch and dirty status when you are in a git directory, you can add the following to your {{ic|~/.config/fish/config.fish}}:<br />
{{bc|<nowiki><br />
# fish git prompt<br />
set __fish_git_prompt_showdirtystate 'yes'<br />
set __fish_git_prompt_showstashstate 'yes'<br />
set __fish_git_prompt_showupstream 'yes'<br />
set __fish_git_prompt_color_branch yellow<br />
<br />
# Status Chars<br />
set __fish_git_prompt_char_dirtystate '⚡'<br />
set __fish_git_prompt_char_stagedstate '→'<br />
set __fish_git_prompt_char_stashstate '↩'<br />
set __fish_git_prompt_char_upstream_ahead '↑'<br />
set __fish_git_prompt_char_upstream_behind '↓'<br />
<br />
function fish_prompt<br />
set last_status $status<br />
set_color $fish_color_cwd<br />
printf '%s' (prompt_pwd)<br />
set_color normal<br />
printf '%s ' (__fish_git_prompt)<br />
set_color normal<br />
end<br />
</nowiki>}}<br />
<br />
=== Command completion ===<br />
<br />
fish can generate autocompletions from man pages. Completions are written to {{ic|~/.config/fish/generated_completions/}} and can be generated by calling:<br />
<br />
fish_update_completions<br />
<br />
You can also define your own completions in {{ic|~/.config/fish/completions/}}. See {{ic|/usr/share/fish/completions/}} for a few examples.<br />
<br />
Context-aware completions for Arch Linux-specific commands like ''pacman'', ''pacman-key'', ''makepkg'', ''cower'', ''pbget'', ''pacmatic'' are built into fish, since the policy of the fish development is to include all the existent completions in the upstream tarball. The memory management is clever enough to avoid any negative impact on resources.<br />
<br />
=== /etc/profile and ~/.profile compatibility ===<br />
<br />
Since standard POSIX {{ic|sh}} syntax is not compatible with fish, fish will not be able to source {{ic|/etc/profile}} (and thus all {{ic|*.sh}} in {{ic|/etc/profile.d}}) and {{ic|~/.profile}}<br />
<br />
If you want fish to source those files, install {{Pkg|dash}} and add this line to your {{ic|config.fish}}:<br />
env -i HOME=$HOME dash -l -c printenv | sed -e '/PATH/s/:/ /g;s/=/ /;s/^/set -x /' | source<br />
<br />
an alternative variant will save you one executable invocation by using a builtin command:<br />
env -i HOME=$HOME dash -l -c 'export -p' | sed -e "/PATH/s/'//g;/PATH/s/:/ /g;s/=/ /;s/^export/set -x/" | source<br />
<br />
==Tips and Tricks==<br />
===History Substitution===<br />
Fish does not implement history substitution (e.g. {{ic|sudo !!}}), and the fish developers have said that they [http://fishshell.com/docs/current/faq.html#faq-history do not plan to]. Still, this is an essential piece of many users' workflow. Reddit user, [http://www.reddit.com/u/crossroads1112 crossroads1112], created a function that regains some of the functionality of history substitution and with another syntax. The function is on [https://gist.github.com/crossroads1112/77badb2c3455e23b873b github] and instructions are included as comments in it. There is a [https://gist.github.com/b-/981892a65837ab0a387e forked version] that is closer to the original syntax and allows for {{ic|command !!}} if you specify the command in the helper function.<br />
<br />
== トラブルシューティング ==<br />
<br />
{{Accuracy|Changing the default shell should not interfere with the execution of shell scripts, so long as they begin with a proper [https://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang line].}}<br />
<br />
In Arch, there are a lot of shell scripts written for Bash, and these have not been translated to fish. It is advisable not to set fish as your default shell because of this. The best option is to open your terminal emulator with a command line option that executes fish. For most terminals this is the {{ic|-e}} switch, so for example, to open gnome-terminal using fish, change your shortcut to use:<br />
<br />
gnome-terminal -e fish<br />
<br />
With LilyTerm and other light terminal emulators that do not support setting the shell it would look like this:<br />
<br />
SHELL=/usr/bin/fish lilyterm<br />
<br />
Another option is to set fish as the default shell for the terminal in the terminal's configuration or for a terminal profile if your terminal emulator has a profiles feature. This is contrast to changing the default shell for the user which would cause the above mentioned problem.<br />
<br />
To set fish as the shell started in tmux, put this into your {{ic|~/.tmux.conf}}:<br />
<br />
set-option -g default-shell "/usr/bin/fish"<br />
<br />
Not setting fish as system wide default allows the arch scripts to run on startup, ensure the environment variables are set correctly, and generally reduces the issues associated with using a non-Bash compatible terminal like fish.<br />
<br />
If you decide to set fish as your default shell, you may find that you no longer have very much in your path.<br />
You can add a section to your {{ic|~/.config/fish/config.fish}} file that will set your path correctly on login. This is much like {{ic|.profile}} or {{ic|.bash_profile}} as it is only executed for login shells.<br />
<br />
{{bc|<br />
if status --is-login<br />
set PATH $PATH /usr/bin /sbin<br />
end<br />
}}<br />
<br />
Note that you will need to manually add various other environment variables, such as {{ic|$MOZ_PLUGIN_PATH}}. It is a huge amount of work to get a seamless experience with fish as your default shell.<br />
<br />
=== suでbashが起動 ===<br />
<br />
もし、suでbashが起動する場合(Bashがデフォルトシェルのため), fishに関数を定義します。<br />
<br />
$ funced su<br />
function su<br />
/bin/su --shell=/usr/bin/fish $argv<br />
end<br />
$ funcsave su<br />
<br />
=== ログイン時にXを起動 ===<br />
<br />
{{ic|~/.config/fish/config.fish}}の一番下に以下を追加します。<br />
<br />
{{bc|1=<nowiki><br />
# start X at login<br />
if status --is-login<br />
if test -z "$DISPLAY" -a $XDG_VTNR -eq 1<br />
exec startx -- -keeptty<br />
end<br />
end<br />
</nowiki>}}<br />
<br />
{{Note|fish使用時に{{ic|startx}}が{{ic|-keeptty}}フラグを必要とする理由については[https://github.com/fish-shell/fish-shell/issues/1772 この記事]を参照してください。}}<br />
<br />
== 参照 ==<br />
<br />
* http://fishshell.com/ - ホームページ<br />
* http://fishshell.com/docs/2.1/index.html - ドキュメント</div>はつせhttps://wiki.archlinux.jp/index.php?title=Fish&diff=3787Fish2015-10-24T07:36:30Z<p>はつせ: /* suがbashで起動 */</p>
<hr />
<div>{{lowercase title}}<br />
[[Category:Command shells]]<br />
[[de:Fish]]<br />
[[en:Fish]]<br />
[[ru:Fish]]<br />
'''fish''' ('''friendly interactive shell''')は主に対話的に使用することを意図されたユーザフレンドリーなコマンドラインシェルです。<br />
<br />
== インストール ==<br />
<br />
[[pacman|Install]] the {{Pkg|fish}} package from the [[official repositories]] for the stable version of the [http://fishshell.com/ mainstream fork] of the project.<br />
<br />
[[pacman|Install]] {{AUR|fish-shell-git}}{{Broken package link|{{aur-mirror|fish-shell-git}}}} from the [[AUR]] for the latest development version.<br />
<br />
[[pacman|Install]] {{AUR|fish-git}} from the [[AUR]] for the legacy version that was [http://www.mail-archive.com/fish-users@lists.sourceforge.net/msg02893.html discontinued] by its [https://github.com/liljencrantz original developer] in 2011.<br />
<br />
To make fish the default shell, run {{ic|chsh -s /usr/bin/fish}}.<br />
<br />
== 入力/出力 ==<br />
<br />
=== File descriptors ===<br />
Like other shells, fish lets you redirect input/output streams. This is useful when using text files to save programs output or errors, or when using text files as input. Most programs use three input/output streams, represented by numbers called file descriptors (FD). These are:<br />
<br />
* Standard input (FD 0), used for reading (keyboard by default).<br />
* Standard output (FD 1), used for writing (screen by default).<br />
* Standard error (FD 2), used for displaying errors and warnings (screen by default).<br />
<br />
=== リダイレクト ===<br />
Any file descriptor can be directed to other files through a mechanism called redirection:<br />
<br />
{{bc|''Redirecting standard input:''<br />
$ command < source_file<br />
<br />
''Redirecting standard output:''<br />
$ command > destination<br />
<br />
''Appending standard output to an existing file:''<br />
$ command >> destination<br />
<br />
''Redirecting standard error:''<br />
$ command ^ destination<br />
<br />
''Appending standard error to an existing file:''<br />
$ command ^^ destination}}<br />
<br />
You can use one of the following as {{ic|destination}}:<br />
<br />
* A filename (the output will be written to the specified file).<br />
* An {{ic|&}} followed by the number of another file descriptor. The output will be written to the other file descriptor.<br />
* An {{ic|&}} followed by a {{ic|-}} sign. The output will not be written anywhere.<br />
<br />
Examples:<br />
{{bc|''Redirecting standard output to a file:''<br />
$ command > destination_file.txt<br />
<br />
''Redirecting both standard output and standard error to the same file:''<br />
$ command > destination_file.txt ^ &1<br />
<br />
''Silencing standard output:''<br />
$ command > &-}}<br />
<br />
=== パイプ ===<br />
<br />
You can redirect standard output of one command to standard input of the next command. This is done by separating the commands by the pipe character ({{ic|<nowiki>|</nowiki>}}). Example:<br />
<br />
cat example.txt | head<br />
<br />
You can redirect other file descriptors to the pipe (besides standard output). The next example shows how to use standard error of one command as standard input of another command, prepending standard error file descriptor's number and {{ic|>}} to the pipe:<br />
<br />
$ command 2>| less<br />
<br />
This will run {{ic|command}} and redirect its standard error to the {{ic|less}} command.<br />
<br />
== Configuration ==<br />
<br />
User configurations for fish are located at {{ic|~/.config/fish/config.fish}}. Adding commands or functions to the file will execute/define them when opening a terminal, similar to {{ic|.bashrc}}.<br />
<br />
=== Web interface ===<br />
<br />
The fish prompt and terminal colors can be set with the interactive web interface:<br />
<br />
fish_config<br />
<br />
Selected settings are written to your personal configuration file. You can also view defined functions and your history.<br />
<br />
=== プロンプト ===<br />
<br />
If you would like fish to display the branch and dirty status when you are in a git directory, you can add the following to your {{ic|~/.config/fish/config.fish}}:<br />
{{bc|<nowiki><br />
# fish git prompt<br />
set __fish_git_prompt_showdirtystate 'yes'<br />
set __fish_git_prompt_showstashstate 'yes'<br />
set __fish_git_prompt_showupstream 'yes'<br />
set __fish_git_prompt_color_branch yellow<br />
<br />
# Status Chars<br />
set __fish_git_prompt_char_dirtystate '⚡'<br />
set __fish_git_prompt_char_stagedstate '→'<br />
set __fish_git_prompt_char_stashstate '↩'<br />
set __fish_git_prompt_char_upstream_ahead '↑'<br />
set __fish_git_prompt_char_upstream_behind '↓'<br />
<br />
function fish_prompt<br />
set last_status $status<br />
set_color $fish_color_cwd<br />
printf '%s' (prompt_pwd)<br />
set_color normal<br />
printf '%s ' (__fish_git_prompt)<br />
set_color normal<br />
end<br />
</nowiki>}}<br />
<br />
=== Command completion ===<br />
<br />
fish can generate autocompletions from man pages. Completions are written to {{ic|~/.config/fish/generated_completions/}} and can be generated by calling:<br />
<br />
fish_update_completions<br />
<br />
You can also define your own completions in {{ic|~/.config/fish/completions/}}. See {{ic|/usr/share/fish/completions/}} for a few examples.<br />
<br />
Context-aware completions for Arch Linux-specific commands like ''pacman'', ''pacman-key'', ''makepkg'', ''cower'', ''pbget'', ''pacmatic'' are built into fish, since the policy of the fish development is to include all the existent completions in the upstream tarball. The memory management is clever enough to avoid any negative impact on resources.<br />
<br />
=== /etc/profile and ~/.profile compatibility ===<br />
<br />
Since standard POSIX {{ic|sh}} syntax is not compatible with fish, fish will not be able to source {{ic|/etc/profile}} (and thus all {{ic|*.sh}} in {{ic|/etc/profile.d}}) and {{ic|~/.profile}}<br />
<br />
If you want fish to source those files, install {{Pkg|dash}} and add this line to your {{ic|config.fish}}:<br />
env -i HOME=$HOME dash -l -c printenv | sed -e '/PATH/s/:/ /g;s/=/ /;s/^/set -x /' | source<br />
<br />
an alternative variant will save you one executable invocation by using a builtin command:<br />
env -i HOME=$HOME dash -l -c 'export -p' | sed -e "/PATH/s/'//g;/PATH/s/:/ /g;s/=/ /;s/^export/set -x/" | source<br />
<br />
==Tips and Tricks==<br />
===History Substitution===<br />
Fish does not implement history substitution (e.g. {{ic|sudo !!}}), and the fish developers have said that they [http://fishshell.com/docs/current/faq.html#faq-history do not plan to]. Still, this is an essential piece of many users' workflow. Reddit user, [http://www.reddit.com/u/crossroads1112 crossroads1112], created a function that regains some of the functionality of history substitution and with another syntax. The function is on [https://gist.github.com/crossroads1112/77badb2c3455e23b873b github] and instructions are included as comments in it. There is a [https://gist.github.com/b-/981892a65837ab0a387e forked version] that is closer to the original syntax and allows for {{ic|command !!}} if you specify the command in the helper function.<br />
<br />
== トラブルシューティング ==<br />
<br />
{{Accuracy|Changing the default shell should not interfere with the execution of shell scripts, so long as they begin with a proper [https://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang line].}}<br />
<br />
In Arch, there are a lot of shell scripts written for Bash, and these have not been translated to fish. It is advisable not to set fish as your default shell because of this. The best option is to open your terminal emulator with a command line option that executes fish. For most terminals this is the {{ic|-e}} switch, so for example, to open gnome-terminal using fish, change your shortcut to use:<br />
<br />
gnome-terminal -e fish<br />
<br />
With LilyTerm and other light terminal emulators that do not support setting the shell it would look like this:<br />
<br />
SHELL=/usr/bin/fish lilyterm<br />
<br />
Another option is to set fish as the default shell for the terminal in the terminal's configuration or for a terminal profile if your terminal emulator has a profiles feature. This is contrast to changing the default shell for the user which would cause the above mentioned problem.<br />
<br />
To set fish as the shell started in tmux, put this into your {{ic|~/.tmux.conf}}:<br />
<br />
set-option -g default-shell "/usr/bin/fish"<br />
<br />
Not setting fish as system wide default allows the arch scripts to run on startup, ensure the environment variables are set correctly, and generally reduces the issues associated with using a non-Bash compatible terminal like fish.<br />
<br />
If you decide to set fish as your default shell, you may find that you no longer have very much in your path.<br />
You can add a section to your {{ic|~/.config/fish/config.fish}} file that will set your path correctly on login. This is much like {{ic|.profile}} or {{ic|.bash_profile}} as it is only executed for login shells.<br />
<br />
{{bc|<br />
if status --is-login<br />
set PATH $PATH /usr/bin /sbin<br />
end<br />
}}<br />
<br />
Note that you will need to manually add various other environment variables, such as {{ic|$MOZ_PLUGIN_PATH}}. It is a huge amount of work to get a seamless experience with fish as your default shell.<br />
<br />
=== suでbashが起動 ===<br />
<br />
もし、suでbashが起動する場合(Bashがデフォルトシェルのため), fishに関数を定義します。<br />
<br />
$ funced su<br />
function su<br />
/bin/su --shell=/usr/bin/fish $argv<br />
end<br />
$ funcsave su<br />
<br />
=== ログイン時にXを起動 ===<br />
<br />
{{ic|~/.config/fish/config.fish}}の一番下に以下を追加します。<br />
<br />
{{bc|1=<nowiki><br />
# start X at login<br />
if status --is-login<br />
if test -z "$DISPLAY" -a $XDG_VTNR -eq 1<br />
exec startx -- -keeptty<br />
end<br />
end<br />
</nowiki>}}<br />
<br />
{{Note|fish使用時に{{ic|startx}}が{{ic|-keeptty}}フラグを必要とする理由については[https://github.com/fish-shell/fish-shell/issues/1772 この記事]を参照してください。}}<br />
<br />
== 参照 ==<br />
<br />
* http://fishshell.com/ - ホームページ<br />
* http://fishshell.com/docs/2.1/index.html - ドキュメント</div>はつせhttps://wiki.archlinux.jp/index.php?title=Fish&diff=3786Fish2015-10-24T07:35:19Z<p>はつせ: /* suでbash起動 */</p>
<hr />
<div>{{lowercase title}}<br />
[[Category:Command shells]]<br />
[[de:Fish]]<br />
[[en:Fish]]<br />
[[ru:Fish]]<br />
'''fish''' ('''friendly interactive shell''')は主に対話的に使用することを意図されたユーザフレンドリーなコマンドラインシェルです。<br />
<br />
== インストール ==<br />
<br />
[[pacman|Install]] the {{Pkg|fish}} package from the [[official repositories]] for the stable version of the [http://fishshell.com/ mainstream fork] of the project.<br />
<br />
[[pacman|Install]] {{AUR|fish-shell-git}}{{Broken package link|{{aur-mirror|fish-shell-git}}}} from the [[AUR]] for the latest development version.<br />
<br />
[[pacman|Install]] {{AUR|fish-git}} from the [[AUR]] for the legacy version that was [http://www.mail-archive.com/fish-users@lists.sourceforge.net/msg02893.html discontinued] by its [https://github.com/liljencrantz original developer] in 2011.<br />
<br />
To make fish the default shell, run {{ic|chsh -s /usr/bin/fish}}.<br />
<br />
== 入力/出力 ==<br />
<br />
=== File descriptors ===<br />
Like other shells, fish lets you redirect input/output streams. This is useful when using text files to save programs output or errors, or when using text files as input. Most programs use three input/output streams, represented by numbers called file descriptors (FD). These are:<br />
<br />
* Standard input (FD 0), used for reading (keyboard by default).<br />
* Standard output (FD 1), used for writing (screen by default).<br />
* Standard error (FD 2), used for displaying errors and warnings (screen by default).<br />
<br />
=== リダイレクト ===<br />
Any file descriptor can be directed to other files through a mechanism called redirection:<br />
<br />
{{bc|''Redirecting standard input:''<br />
$ command < source_file<br />
<br />
''Redirecting standard output:''<br />
$ command > destination<br />
<br />
''Appending standard output to an existing file:''<br />
$ command >> destination<br />
<br />
''Redirecting standard error:''<br />
$ command ^ destination<br />
<br />
''Appending standard error to an existing file:''<br />
$ command ^^ destination}}<br />
<br />
You can use one of the following as {{ic|destination}}:<br />
<br />
* A filename (the output will be written to the specified file).<br />
* An {{ic|&}} followed by the number of another file descriptor. The output will be written to the other file descriptor.<br />
* An {{ic|&}} followed by a {{ic|-}} sign. The output will not be written anywhere.<br />
<br />
Examples:<br />
{{bc|''Redirecting standard output to a file:''<br />
$ command > destination_file.txt<br />
<br />
''Redirecting both standard output and standard error to the same file:''<br />
$ command > destination_file.txt ^ &1<br />
<br />
''Silencing standard output:''<br />
$ command > &-}}<br />
<br />
=== パイプ ===<br />
<br />
You can redirect standard output of one command to standard input of the next command. This is done by separating the commands by the pipe character ({{ic|<nowiki>|</nowiki>}}). Example:<br />
<br />
cat example.txt | head<br />
<br />
You can redirect other file descriptors to the pipe (besides standard output). The next example shows how to use standard error of one command as standard input of another command, prepending standard error file descriptor's number and {{ic|>}} to the pipe:<br />
<br />
$ command 2>| less<br />
<br />
This will run {{ic|command}} and redirect its standard error to the {{ic|less}} command.<br />
<br />
== Configuration ==<br />
<br />
User configurations for fish are located at {{ic|~/.config/fish/config.fish}}. Adding commands or functions to the file will execute/define them when opening a terminal, similar to {{ic|.bashrc}}.<br />
<br />
=== Web interface ===<br />
<br />
The fish prompt and terminal colors can be set with the interactive web interface:<br />
<br />
fish_config<br />
<br />
Selected settings are written to your personal configuration file. You can also view defined functions and your history.<br />
<br />
=== プロンプト ===<br />
<br />
If you would like fish to display the branch and dirty status when you are in a git directory, you can add the following to your {{ic|~/.config/fish/config.fish}}:<br />
{{bc|<nowiki><br />
# fish git prompt<br />
set __fish_git_prompt_showdirtystate 'yes'<br />
set __fish_git_prompt_showstashstate 'yes'<br />
set __fish_git_prompt_showupstream 'yes'<br />
set __fish_git_prompt_color_branch yellow<br />
<br />
# Status Chars<br />
set __fish_git_prompt_char_dirtystate '⚡'<br />
set __fish_git_prompt_char_stagedstate '→'<br />
set __fish_git_prompt_char_stashstate '↩'<br />
set __fish_git_prompt_char_upstream_ahead '↑'<br />
set __fish_git_prompt_char_upstream_behind '↓'<br />
<br />
function fish_prompt<br />
set last_status $status<br />
set_color $fish_color_cwd<br />
printf '%s' (prompt_pwd)<br />
set_color normal<br />
printf '%s ' (__fish_git_prompt)<br />
set_color normal<br />
end<br />
</nowiki>}}<br />
<br />
=== Command completion ===<br />
<br />
fish can generate autocompletions from man pages. Completions are written to {{ic|~/.config/fish/generated_completions/}} and can be generated by calling:<br />
<br />
fish_update_completions<br />
<br />
You can also define your own completions in {{ic|~/.config/fish/completions/}}. See {{ic|/usr/share/fish/completions/}} for a few examples.<br />
<br />
Context-aware completions for Arch Linux-specific commands like ''pacman'', ''pacman-key'', ''makepkg'', ''cower'', ''pbget'', ''pacmatic'' are built into fish, since the policy of the fish development is to include all the existent completions in the upstream tarball. The memory management is clever enough to avoid any negative impact on resources.<br />
<br />
=== /etc/profile and ~/.profile compatibility ===<br />
<br />
Since standard POSIX {{ic|sh}} syntax is not compatible with fish, fish will not be able to source {{ic|/etc/profile}} (and thus all {{ic|*.sh}} in {{ic|/etc/profile.d}}) and {{ic|~/.profile}}<br />
<br />
If you want fish to source those files, install {{Pkg|dash}} and add this line to your {{ic|config.fish}}:<br />
env -i HOME=$HOME dash -l -c printenv | sed -e '/PATH/s/:/ /g;s/=/ /;s/^/set -x /' | source<br />
<br />
an alternative variant will save you one executable invocation by using a builtin command:<br />
env -i HOME=$HOME dash -l -c 'export -p' | sed -e "/PATH/s/'//g;/PATH/s/:/ /g;s/=/ /;s/^export/set -x/" | source<br />
<br />
==Tips and Tricks==<br />
===History Substitution===<br />
Fish does not implement history substitution (e.g. {{ic|sudo !!}}), and the fish developers have said that they [http://fishshell.com/docs/current/faq.html#faq-history do not plan to]. Still, this is an essential piece of many users' workflow. Reddit user, [http://www.reddit.com/u/crossroads1112 crossroads1112], created a function that regains some of the functionality of history substitution and with another syntax. The function is on [https://gist.github.com/crossroads1112/77badb2c3455e23b873b github] and instructions are included as comments in it. There is a [https://gist.github.com/b-/981892a65837ab0a387e forked version] that is closer to the original syntax and allows for {{ic|command !!}} if you specify the command in the helper function.<br />
<br />
== トラブルシューティング ==<br />
<br />
{{Accuracy|Changing the default shell should not interfere with the execution of shell scripts, so long as they begin with a proper [https://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang line].}}<br />
<br />
In Arch, there are a lot of shell scripts written for Bash, and these have not been translated to fish. It is advisable not to set fish as your default shell because of this. The best option is to open your terminal emulator with a command line option that executes fish. For most terminals this is the {{ic|-e}} switch, so for example, to open gnome-terminal using fish, change your shortcut to use:<br />
<br />
gnome-terminal -e fish<br />
<br />
With LilyTerm and other light terminal emulators that do not support setting the shell it would look like this:<br />
<br />
SHELL=/usr/bin/fish lilyterm<br />
<br />
Another option is to set fish as the default shell for the terminal in the terminal's configuration or for a terminal profile if your terminal emulator has a profiles feature. This is contrast to changing the default shell for the user which would cause the above mentioned problem.<br />
<br />
To set fish as the shell started in tmux, put this into your {{ic|~/.tmux.conf}}:<br />
<br />
set-option -g default-shell "/usr/bin/fish"<br />
<br />
Not setting fish as system wide default allows the arch scripts to run on startup, ensure the environment variables are set correctly, and generally reduces the issues associated with using a non-Bash compatible terminal like fish.<br />
<br />
If you decide to set fish as your default shell, you may find that you no longer have very much in your path.<br />
You can add a section to your {{ic|~/.config/fish/config.fish}} file that will set your path correctly on login. This is much like {{ic|.profile}} or {{ic|.bash_profile}} as it is only executed for login shells.<br />
<br />
{{bc|<br />
if status --is-login<br />
set PATH $PATH /usr/bin /sbin<br />
end<br />
}}<br />
<br />
Note that you will need to manually add various other environment variables, such as {{ic|$MOZ_PLUGIN_PATH}}. It is a huge amount of work to get a seamless experience with fish as your default shell.<br />
<br />
=== suがbashで起動 ===<br />
<br />
もし、suをbashで始める場合(Bashがデフォルトシェルのため), fishに関数を定義します。<br />
<br />
$ funced su<br />
function su<br />
/bin/su --shell=/usr/bin/fish $argv<br />
end<br />
$ funcsave su<br />
<br />
=== ログイン時にXを起動 ===<br />
<br />
{{ic|~/.config/fish/config.fish}}の一番下に以下を追加します。<br />
<br />
{{bc|1=<nowiki><br />
# start X at login<br />
if status --is-login<br />
if test -z "$DISPLAY" -a $XDG_VTNR -eq 1<br />
exec startx -- -keeptty<br />
end<br />
end<br />
</nowiki>}}<br />
<br />
{{Note|fish使用時に{{ic|startx}}が{{ic|-keeptty}}フラグを必要とする理由については[https://github.com/fish-shell/fish-shell/issues/1772 この記事]を参照してください。}}<br />
<br />
== 参照 ==<br />
<br />
* http://fishshell.com/ - ホームページ<br />
* http://fishshell.com/docs/2.1/index.html - ドキュメント</div>はつせhttps://wiki.archlinux.jp/index.php?title=Fish&diff=3785Fish2015-10-24T07:26:23Z<p>はつせ: </p>
<hr />
<div>{{lowercase title}}<br />
[[Category:Command shells]]<br />
[[de:Fish]]<br />
[[en:Fish]]<br />
[[ru:Fish]]<br />
'''fish''' ('''friendly interactive shell''')は主に対話的に使用することを意図されたユーザフレンドリーなコマンドラインシェルです。<br />
<br />
== インストール ==<br />
<br />
[[pacman|Install]] the {{Pkg|fish}} package from the [[official repositories]] for the stable version of the [http://fishshell.com/ mainstream fork] of the project.<br />
<br />
[[pacman|Install]] {{AUR|fish-shell-git}}{{Broken package link|{{aur-mirror|fish-shell-git}}}} from the [[AUR]] for the latest development version.<br />
<br />
[[pacman|Install]] {{AUR|fish-git}} from the [[AUR]] for the legacy version that was [http://www.mail-archive.com/fish-users@lists.sourceforge.net/msg02893.html discontinued] by its [https://github.com/liljencrantz original developer] in 2011.<br />
<br />
To make fish the default shell, run {{ic|chsh -s /usr/bin/fish}}.<br />
<br />
== 入力/出力 ==<br />
<br />
=== File descriptors ===<br />
Like other shells, fish lets you redirect input/output streams. This is useful when using text files to save programs output or errors, or when using text files as input. Most programs use three input/output streams, represented by numbers called file descriptors (FD). These are:<br />
<br />
* Standard input (FD 0), used for reading (keyboard by default).<br />
* Standard output (FD 1), used for writing (screen by default).<br />
* Standard error (FD 2), used for displaying errors and warnings (screen by default).<br />
<br />
=== リダイレクト ===<br />
Any file descriptor can be directed to other files through a mechanism called redirection:<br />
<br />
{{bc|''Redirecting standard input:''<br />
$ command < source_file<br />
<br />
''Redirecting standard output:''<br />
$ command > destination<br />
<br />
''Appending standard output to an existing file:''<br />
$ command >> destination<br />
<br />
''Redirecting standard error:''<br />
$ command ^ destination<br />
<br />
''Appending standard error to an existing file:''<br />
$ command ^^ destination}}<br />
<br />
You can use one of the following as {{ic|destination}}:<br />
<br />
* A filename (the output will be written to the specified file).<br />
* An {{ic|&}} followed by the number of another file descriptor. The output will be written to the other file descriptor.<br />
* An {{ic|&}} followed by a {{ic|-}} sign. The output will not be written anywhere.<br />
<br />
Examples:<br />
{{bc|''Redirecting standard output to a file:''<br />
$ command > destination_file.txt<br />
<br />
''Redirecting both standard output and standard error to the same file:''<br />
$ command > destination_file.txt ^ &1<br />
<br />
''Silencing standard output:''<br />
$ command > &-}}<br />
<br />
=== パイプ ===<br />
<br />
You can redirect standard output of one command to standard input of the next command. This is done by separating the commands by the pipe character ({{ic|<nowiki>|</nowiki>}}). Example:<br />
<br />
cat example.txt | head<br />
<br />
You can redirect other file descriptors to the pipe (besides standard output). The next example shows how to use standard error of one command as standard input of another command, prepending standard error file descriptor's number and {{ic|>}} to the pipe:<br />
<br />
$ command 2>| less<br />
<br />
This will run {{ic|command}} and redirect its standard error to the {{ic|less}} command.<br />
<br />
== Configuration ==<br />
<br />
User configurations for fish are located at {{ic|~/.config/fish/config.fish}}. Adding commands or functions to the file will execute/define them when opening a terminal, similar to {{ic|.bashrc}}.<br />
<br />
=== Web interface ===<br />
<br />
The fish prompt and terminal colors can be set with the interactive web interface:<br />
<br />
fish_config<br />
<br />
Selected settings are written to your personal configuration file. You can also view defined functions and your history.<br />
<br />
=== プロンプト ===<br />
<br />
If you would like fish to display the branch and dirty status when you are in a git directory, you can add the following to your {{ic|~/.config/fish/config.fish}}:<br />
{{bc|<nowiki><br />
# fish git prompt<br />
set __fish_git_prompt_showdirtystate 'yes'<br />
set __fish_git_prompt_showstashstate 'yes'<br />
set __fish_git_prompt_showupstream 'yes'<br />
set __fish_git_prompt_color_branch yellow<br />
<br />
# Status Chars<br />
set __fish_git_prompt_char_dirtystate '⚡'<br />
set __fish_git_prompt_char_stagedstate '→'<br />
set __fish_git_prompt_char_stashstate '↩'<br />
set __fish_git_prompt_char_upstream_ahead '↑'<br />
set __fish_git_prompt_char_upstream_behind '↓'<br />
<br />
function fish_prompt<br />
set last_status $status<br />
set_color $fish_color_cwd<br />
printf '%s' (prompt_pwd)<br />
set_color normal<br />
printf '%s ' (__fish_git_prompt)<br />
set_color normal<br />
end<br />
</nowiki>}}<br />
<br />
=== Command completion ===<br />
<br />
fish can generate autocompletions from man pages. Completions are written to {{ic|~/.config/fish/generated_completions/}} and can be generated by calling:<br />
<br />
fish_update_completions<br />
<br />
You can also define your own completions in {{ic|~/.config/fish/completions/}}. See {{ic|/usr/share/fish/completions/}} for a few examples.<br />
<br />
Context-aware completions for Arch Linux-specific commands like ''pacman'', ''pacman-key'', ''makepkg'', ''cower'', ''pbget'', ''pacmatic'' are built into fish, since the policy of the fish development is to include all the existent completions in the upstream tarball. The memory management is clever enough to avoid any negative impact on resources.<br />
<br />
=== /etc/profile and ~/.profile compatibility ===<br />
<br />
Since standard POSIX {{ic|sh}} syntax is not compatible with fish, fish will not be able to source {{ic|/etc/profile}} (and thus all {{ic|*.sh}} in {{ic|/etc/profile.d}}) and {{ic|~/.profile}}<br />
<br />
If you want fish to source those files, install {{Pkg|dash}} and add this line to your {{ic|config.fish}}:<br />
env -i HOME=$HOME dash -l -c printenv | sed -e '/PATH/s/:/ /g;s/=/ /;s/^/set -x /' | source<br />
<br />
an alternative variant will save you one executable invocation by using a builtin command:<br />
env -i HOME=$HOME dash -l -c 'export -p' | sed -e "/PATH/s/'//g;/PATH/s/:/ /g;s/=/ /;s/^export/set -x/" | source<br />
<br />
==Tips and Tricks==<br />
===History Substitution===<br />
Fish does not implement history substitution (e.g. {{ic|sudo !!}}), and the fish developers have said that they [http://fishshell.com/docs/current/faq.html#faq-history do not plan to]. Still, this is an essential piece of many users' workflow. Reddit user, [http://www.reddit.com/u/crossroads1112 crossroads1112], created a function that regains some of the functionality of history substitution and with another syntax. The function is on [https://gist.github.com/crossroads1112/77badb2c3455e23b873b github] and instructions are included as comments in it. There is a [https://gist.github.com/b-/981892a65837ab0a387e forked version] that is closer to the original syntax and allows for {{ic|command !!}} if you specify the command in the helper function.<br />
<br />
== トラブルシューティング ==<br />
<br />
{{Accuracy|Changing the default shell should not interfere with the execution of shell scripts, so long as they begin with a proper [https://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang line].}}<br />
<br />
In Arch, there are a lot of shell scripts written for Bash, and these have not been translated to fish. It is advisable not to set fish as your default shell because of this. The best option is to open your terminal emulator with a command line option that executes fish. For most terminals this is the {{ic|-e}} switch, so for example, to open gnome-terminal using fish, change your shortcut to use:<br />
<br />
gnome-terminal -e fish<br />
<br />
With LilyTerm and other light terminal emulators that do not support setting the shell it would look like this:<br />
<br />
SHELL=/usr/bin/fish lilyterm<br />
<br />
Another option is to set fish as the default shell for the terminal in the terminal's configuration or for a terminal profile if your terminal emulator has a profiles feature. This is contrast to changing the default shell for the user which would cause the above mentioned problem.<br />
<br />
To set fish as the shell started in tmux, put this into your {{ic|~/.tmux.conf}}:<br />
<br />
set-option -g default-shell "/usr/bin/fish"<br />
<br />
Not setting fish as system wide default allows the arch scripts to run on startup, ensure the environment variables are set correctly, and generally reduces the issues associated with using a non-Bash compatible terminal like fish.<br />
<br />
If you decide to set fish as your default shell, you may find that you no longer have very much in your path.<br />
You can add a section to your {{ic|~/.config/fish/config.fish}} file that will set your path correctly on login. This is much like {{ic|.profile}} or {{ic|.bash_profile}} as it is only executed for login shells.<br />
<br />
{{bc|<br />
if status --is-login<br />
set PATH $PATH /usr/bin /sbin<br />
end<br />
}}<br />
<br />
Note that you will need to manually add various other environment variables, such as {{ic|$MOZ_PLUGIN_PATH}}. It is a huge amount of work to get a seamless experience with fish as your default shell.<br />
<br />
=== suでbash起動 ===<br />
<br />
もし、suでbashが始まる場合(Bashがデフォルトシェルのため), fishに関数を定義します。<br />
<br />
$ funced su<br />
function su<br />
/bin/su --shell=/usr/bin/fish $argv<br />
end<br />
$ funcsave su<br />
<br />
=== ログイン時にXを起動 ===<br />
<br />
{{ic|~/.config/fish/config.fish}}の一番下に以下を追加します。<br />
<br />
{{bc|1=<nowiki><br />
# start X at login<br />
if status --is-login<br />
if test -z "$DISPLAY" -a $XDG_VTNR -eq 1<br />
exec startx -- -keeptty<br />
end<br />
end<br />
</nowiki>}}<br />
<br />
{{Note|fish使用時に{{ic|startx}}が{{ic|-keeptty}}フラグを必要とする理由については[https://github.com/fish-shell/fish-shell/issues/1772 この記事]を参照してください。}}<br />
<br />
== 参照 ==<br />
<br />
* http://fishshell.com/ - ホームページ<br />
* http://fishshell.com/docs/2.1/index.html - ドキュメント</div>はつせhttps://wiki.archlinux.jp/index.php?title=Arch_%E3%83%95%E3%82%A1%E3%82%A4%E3%83%AB%E3%82%B7%E3%82%B9%E3%83%86%E3%83%A0%E9%9A%8E%E5%B1%A4&diff=3617Arch ファイルシステム階層2015-08-29T06:46:00Z<p>はつせ: </p>
<hr />
<div>[[Category:ファイルシステム]]<br />
[[en:Arch filesystem hierarchy]]<br />
[[it:Filesystem Hierarchy Standard]]<br />
[[ru:Filesystem Hierarchy Standard]]<br />
[[zh-CN:Arch filesystem hierarchy]]<br />
Arch Linux は他の多数のディストリビューションと同じようにファイルシステム階層標準に従っています。それぞれのディレクトリについてその目的を説明するのに加えて、この記事では Arch 固有の事情についても説明しています。<br />
<br />
== ファイルシステム階層標準 ==<br />
[http://www.pathname.com/fhs Filesystem Hierarchy Standard (FHS) のホームページ] より:<br />
:"''ファイルシステムスタンダードは Unix ディストリビューションの開発者やパッケージの開発者、そしてシステムの実装者によって使われることを想定して策定されました。ただし、この標準はあくまでリファレンスであり、Unix のファイルシステムやディレクトリ階層を管理する方法のチュートリアルではありません。''"<br />
<br />
===共有可能ファイルと共有不能ファイル===<br />
'''共有可能'''ファイルとはあるホストで保存されていながら他者からも利用できるファイルです。'''共有不能'''ファイルは共有できないファイルのことです。例えば、ユーザーのホームディレクトリ内のファイルは共有可能であり、デバイスのロックファイルは共有不能です。<br />
<br />
===静的ファイルと可変ファイル===<br />
'''静的'''ファイルとは例えば、バイナリやライブラリ、ドキュメントなどのシステムの管理者以外からは変更を加えられることがないファイルを意味します。'''可変'''ファイルは静的ファイルでないファイルとして定義されます。<br />
<br />
== ディレクトリ ==<br />
===root ファイルシステム===<br />
root ファイルシステム (スラッシュ記号 ('''/''') で表されます) は他の全てのファイルシステムの根幹となるファイルシステムです。階層の一番上に位置します。たとえファイルやディレクトリが別の物理デバイスに保存されていたとしても、全てのファイルとディレクトリは root ディレクトリ "/" 下に配置されます。root ファイルシステムの中身だけでシステムを起動・復旧・修復できるようになっている必要があります。<br />
<br />
===<strike>/bin: 重要なコマンドラインバイナリ</strike> (廃止)===<br />
シングルユーザーモードで、全てのユーザーから利用できるバイナリを置くための伝統的なディレクトリです (例: cat, ls, cp)。/bin のプログラムはたとえ / を含むパーティションしかマウントされてないときも利用することができます。実際には、Arch では必要なライブラリは全て /usr/lib に存在しています。2013年6月から、[https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /bin は /usr/bin に統合されました]。{{Pkg|filesystem}} パッケージには /bin から /usr/bin へのシンボリックリンクが含まれており、全てのパッケージは /usr/bin にインストールされるようになっています。<br />
<br />
===/boot: ブートローダーの静的なファイル===<br />
共有不能の、静的なディレクトリです。ブートローダーの設定ファイルやブートローダーのステージだけでなく、カーネルや ramdisk イメージも含みます。/boot にはカーネルがユーザー空間のプログラムを実行する前に使用されるデータも保存されます。マスターブートセクタやセクターマップファイルなどです。<br />
<br />
===/dev: デバイスファイル===<br />
Essential device nodes created by udev during the boot process and as machine hardware is discovered by events. This directory highlights one important aspect of the UNIX filesystem - everything is a file or a directory. Exploring this directory will reveal many files, each representing a hardware component of the system. The majority of devices are either block or character devices; however other types of devices exist and can be created. In general, 'block devices' are devices that store or hold data, whereas 'character devices' can be thought of as devices that transmit or transfer data. For example, hard disk drives and optical drives are categorized as block devices while serial ports, mice and USB ports are all character devices.<br />
<br />
===/etc: ホスト固有の設定===<br />
Host-specific, unsharable configuration files shall be placed in the /etc directory. If more than one configuration file is required for an application, it is customary to use a subdirectory in order to keep the /etc/ area as clean as possible. It is considered good practice to make frequent backups of this directory as it contains all system related configuration files. <br />
<br />
====/etc/X11====<br />
X Window System の設定ファイル。<br />
<br />
=====/etc/X11/xinit=====<br />
xinit configuration files. 'xinit' is a configuration method of starting up an X session that is designed to be used as part of a script. <br />
<br />
=====/etc/X11/xinit/xinitrc=====<br />
Global xinitrc file, used by all X sessions started by xinit (startx). Its usage is of course overridden by a .xinitrc file located in the home directory of a user.<br />
<br />
===/home: ユーザーディレクトリ===<br />
UNIX is a multi-user environment. Therefore, each user is also assigned a specific directory that is accessible only to them and to the root user. These are the user home directories, which can be found under '/home/$USER' (~/). Within their home directory, a user can write files, delete them, install programs, etc. Users' home directories contain their data and personal configuration files, the so-called 'dot files' (their name is preceded by a dot), which are 'hidden'. To view dotfiles, enable the appropriate option in your file manager or run ls with the -a switch. If there is a conflict between personal and system wide configuration files, the settings in the personal file will prevail. Dotfiles most likely to be altered by the end user include .xinitrc and .bashrc files. The configuration files for xinit and Bash respectively. They allow the user the ability to change the window manager to be started upon login and also aliases, user-specified commands and environment variables respectively. When a user is created, their dotfiles shall be taken from the /etc/skel directory where system sample files reside. <br />
<br />
Directory /home can become quite large as it is typically used for storing downloads, compiling, installing and running programs, mail, collections of multimedia files etc.<br />
<br />
===/lost+found: ファイルシステム固有の復元可能なデータ===<br />
UNIX-like operating systems must execute a proper shutdown sequence. At times, a system might crash or a power failure might take the machine down. Either way, at the next boot, a filesystem check using the ''fsck'' program shall be performed. ''Fsck'' will go through the system and try to recover any corrupt files that it finds. The result of this recovery operation will be placed in this directory. The files recovered are not likely to be complete or make much sense but there always is a chance that something worthwhile is recovered.<br />
<br />
===/mnt: 一時的なマウントポイント===<br />
This is a generic mount point for temporary filesystems or devices. Mounting is the process of making a filesystem available to the system. After mounting, files will be accessible under the mount-point. Additional mount-points (subdirectories) may be created under /mnt/. There is no limitation to creating a mount-point anywhere on the system, but by convention and for practicality, littering a file system with mount-points should be avoided.<br />
<br />
===/opt: 問題のあるパッケージ===<br />
Packages and large static files that do not fit cleanly into the above GNU filesystem layout can be placed in /opt. FHS 2.3 denotes /opt as reserved for the installation of add-on application software packages. A package placing files in the /opt/ directory creates a directory bearing the same name as the package. This directory in turn holds files that otherwise would be scattered throughout the file system.<br />
For example, the acrobat package has Browser, Reader, and Resource<br />
directories sitting at the same level as the bin directory. This<br />
doesn't fit into a normal GNU filesystem layout, so Arch places all the<br />
files in a subdirectory of /opt.<br />
<br />
===/proc: プロセス情報===<br />
Directory /proc is very special in that it is also a virtual filesystem. It is sometimes referred to as the ''process information pseudo-file system''. It doesn't contain 'real' files, but rather, runtime system information (e.g. system memory, devices mounted, hardware configuration, etc). For this reason it can be regarded as a control and information center for the kernel. In fact, quite a lot of system utilities are simply calls to files in this directory. For example, 'lsmod' is the same as 'cat /proc/modules' while 'lspci' is a synonym for 'cat /proc/pci'. By altering files located in this directory, kernel parameters may be read/changed (sysctl) while the system is running.<br />
<br />
The most distinctive facet about files in this directory is the fact that all of them have a file size of 0, with the exception of '''kcore, mounts''' and '''self'''. <br />
<br />
===/root: 管理者ディレクトリ===<br />
Home directory of the System Administrator, 'root'. This may be somewhat confusing, ('/root under root') but historically, '/' was root's home directory (hence the name of the Administrator account). To keep things tidier, 'root' eventually got its own home directory. Why not '/home/root'? Because '/home' is often located on a different partition or even on another system and would thus be inaccessible to 'root' when - for whatever reason - only '/' is mounted.<br />
<br />
=== /run: 一時的な実行時データ===<br />
The /run mountpoint is supposed to be a tmpfs mounted during early boot, available and writable to for all tools at any time during bootup. [[systemd]], [[udev]] or mdadm that are required early in the boot process require this directory, because /var can be implemented as a separate file system to be mounted at a later stage in the start-up process. It replaces /var/run/, which becomes a symlink of /run.<br />
<br />
===<strike>/sbin: システムバイナリ</strike> (廃止)===<br />
Traditionally UNIX discriminates between 'normal' executables and those used for system maintenance and/or administrative tasks. The latter were supposed to reside either here or - the less important ones - in /usr/sbin. Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. In practice, programs in /sbin require /usr to be mounted as all the necessary libraries are in /usr/lib. As of June 2013, [https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /sbin and /usr/sbin were merged into /usr/bin]. The {{Pkg|filesystem}} package provides symlinks from /sbin and /usr/sbin to /usr/bin, and all packages should be updated to explicitly install to /usr/bin.<br />
<br />
===/srv: サービスデータ===<br />
Site-specific data which is served by the system. The main purpose of specifying this is so that users may find the location of the data files for a particular service, and so that services which require a single tree for read-only data, writable data and scripts (such as CGI scripts) can be reasonably placed. Data of interest to a specific user shall be placed in that user's home directory.<br />
<br />
===/sys: 仮想ファイルシステム===<br />
Virtual file system provided by the Linux kernel. By using virtual files, sysfs exports information about various kernel subsystems, hardware devices and associated device drivers from the kernel's device model to user space. In addition to providing information about various devices and kernel subsystems, exported virtual files are also used for their configuring.<br />
<br />
===/tmp: 一時的なファイル===<br />
This directory contains files that are required temporarily. Many programs use this to create lock files and for temporary storage of data. Do not remove files from this directory unless you know exactly what you are doing! Many of these files are important for currently running programs and deleting them may result in a system crash. On most systems, old files in this directory are cleared out at boot or at daily intervals.<br />
<br />
===/usr: 共有可能な、読み取り専用データ=== <br />
While root is the primary filesystem, /usr is the secondary hierarchy, for user data, containing the majority of (multi-)user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except by the package manager (installation, update, upgrade). Any information that is host-specific or varies with time is stored elsewhere. <br />
<br />
Aside from /home, /usr usually contains by far the largest share of data on a system. Hence, this is one of the most important directories in the system as it contains all the user binaries, their documentation, libraries, header files, etc. X and its supporting libraries can be found here. User programs like telnet, ftp, etc., are also placed here. In the original UNIX implementations, /usr (for ''user''), was where the home directories of the system's users were placed (that is to say, /usr/''username'' was then the directory now known as /home/''username''). Over time, /usr has become where userspace programs and data (as opposed to 'kernelspace' programs and data) reside. The name has not changed, but its meaning has narrowed and lengthened from ''everything user related'' to ''user usable programs and data''. As such, the backronym ''''U'''ser '''S'''ystem '''R'''esources' was created.<br />
<br />
====/usr/bin: バイナリ====<br />
コマンドバイナリ。このディレクトリにはシステム上のバイナリ (アプリケーション) のほとんどが含まれます。このディレクトリ内の実行ファイルは様々です。例えば vim や gcc、gnome-session などがここに置かれます。昔は、このディレクトリには root 権限を必要としない、そしてシングルユーザーモードで必要ないバイナリだけを置くことになっていました。しかしながら、この決まりごとは既に強制ではなくなっており、Arch の開発陣は <strike>全てのバイナリをこのディレクトリに移動することを計画</strike> 全てのバイナリをこのディレクトリに移動しています。<br />
<br />
====/usr/include: ヘッダーファイル====<br />
ユーザー空間のソースコードをコンパイルするのに必要なヘッダーファイル。<br />
<br />
====/usr/lib: ライブラリ====<br />
{{Note|The {{ic|/lib}} directory becomes a symlink to {{ic|/usr/lib}}. [https://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/ Here] is the news. If you encounter error during this update. Please see [[DeveloperWiki:usrlib]] for solution.}}<br />
Contains application private data (kernel modules, systemd services, udev rules, etc) and shared library images (the C programming code library). Libraries are collections of frequently used program routines and are readily identifiable through their filename extension of *.so. They are essential for basic system functionality. Kernel modules (drivers) are in the subdirectory /lib/modules/<kernel-version>.<br />
<br />
====<strike>/usr/sbin: システムバイナリ</strike> (廃止)====<br />
Non-essential system binaries of use to the system administrator. As of June 2013, [https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /usr/sbin was merged into /usr/bin]. The {{Pkg|filesystem}} package provides symlinks from /usr/sbin to /usr/bin, and all packages should now explicitly install to /usr/bin.<br />
<br />
====/usr/share: アーキテクチャに依存しないデータ====<br />
This directory contains 'shareable', architecture-independent files (docs, icons, fonts etc). Note, however, that /usr/share is generally not intended to be shared by different operating systems or by different releases of the same operating system. Any program or package which contains or requires data that do not need to be modified should store these data in /usr/share (or /usr/local/share, if manually installed - see below). It is recommended that a subdirectory be used in /usr/share for this purpose.<br />
<br />
====/usr/src: ソースコード====<br />
<!-- The 'linux' sub-directory holds the Linux kernel sources, and header-files. --><br />
'linux'のサブディレクトリは、Linuxのカーネルのソースコードとヘッダファイルを格納しています。<br />
<br />
====/usr/local: ローカル階層====<br />
Optional tertiary hierarchy for local data. The original idea behind /usr/local was to have a separate ('local') '/usr' directory on every machine besides /usr itself, which might be mounted read-only from somewhere else. It copies the structure of /usr. These days, /usr/local is widely regarded as a good place in which to keep self-compiled or third-party programs. This directory is empty by default in Arch Linux. It may be used for manually compiled software installations if desired. [[pacman]] installs to /usr, therefore, manually compiled/installed software installed to /usr/local may peacefully co-exist with pacman-tracked system software.<br />
<br />
===/var: 可変ファイル===<br />
Variable files, such as logs, spool files, and temporary e-mail files. On Arch, the [[ABS]] tree and pacman cache also reside here. Why not put the variable and transient data into /usr/? Because there might be circumstances when /usr/ is mounted as read-only, e.g. if it is on a CD or on another computer. '/var/' contains variable data, i.e. files and directories the system must be able to write to during operation, whereas /usr/ shall only contain static data.<br />
Some directories can be put onto separate partitions or systems, e.g. for easier backups, due to network topology or security concerns. Other directories have to be on the root partition, because they are vital for the boot process. 'Mountable' directories are: '/home', '/mnt', '/tmp' and '/var'. Essential for booting are: '/bin', '/boot', '/dev', '/etc', '/lib', '/proc', '/sbin' and '/usr'. <br />
<br />
====/var/abs====<br />
<!-- The [[ABS]] tree. A ports-like package build system hierarchy containing build scripts within subdirectories corresponding to all installable Arch software. --><br />
[[ABS]]ツリー。インストール可能な全てのArch softwareに対応するサブディレクトリ内のビルドスクリプトを含んでいる''ports''のようなパッケージビルドシステム階層構造です。<br />
<br />
====/var/cache/pacman/pkg====<br />
pacman のパッケージキャッシュ。<br />
<br />
====/var/lib: 状態情報====<br />
<!-- Persistent data modified by programs as they run (e.g. databases, packaging system metadata etc.). --><br />
<br />
プログラムが実行すると変更される永続データです。(例: データベース、パッケージシステムのメタデータなど)<br />
<br />
====/var/log: ログファイル====<br />
ログファイル。<br />
<br />
====/var/mail: ユーザのメール====<br />
<!-- Deprecated location for users' mailboxes. --><br />
ユーザのメールボックスに推奨されていない場所です。<br />
<br />
====/var/spool: キュー====<br />
<!-- Spool for tasks waiting to be processed (e.g. print queues and unread mail). --><br />
処理されるのを待っているタスクのためのスプールです。(例: プリントキュー、未読メール).<br />
<br />
=====/var/spool/mail=====<br />
<!-- Shareable directory for users' mailboxes. --><br />
ユーザメールボックスのための共有可能なディレクトリです。<br />
<br />
====/var/tmp: 保持される可能性がある一時的なファイル====<br />
<!-- Temporary files to be preserved between reboots. --><br />
再起動の間に一時的なファイルは保持されます。<br />
<br />
==参照==<br />
*[[wikipedia:ja:Filesystem Hierarchy Standard]]<br />
*[http://www.pathname.com/fhs/ Linux FHS ホームページ]</div>はつせhttps://wiki.archlinux.jp/index.php?title=Arch_%E3%83%95%E3%82%A1%E3%82%A4%E3%83%AB%E3%82%B7%E3%82%B9%E3%83%86%E3%83%A0%E9%9A%8E%E5%B1%A4&diff=3616Arch ファイルシステム階層2015-08-29T06:10:44Z<p>はつせ: /* /var/mail: ユーザーのメール */</p>
<hr />
<div>[[Category:ファイルシステム]]<br />
[[en:Arch filesystem hierarchy]]<br />
[[it:Filesystem Hierarchy Standard]]<br />
[[ru:Filesystem Hierarchy Standard]]<br />
[[zh-CN:Arch filesystem hierarchy]]<br />
Arch Linux は他の多数のディストリビューションと同じようにファイルシステム階層標準に従っています。それぞれのディレクトリについてその目的を説明するのに加えて、この記事では Arch 固有の事情についても説明しています。<br />
<br />
== ファイルシステム階層標準 ==<br />
[http://www.pathname.com/fhs Filesystem Hierarchy Standard (FHS) のホームページ] より:<br />
:"''ファイルシステムスタンダードは Unix ディストリビューションの開発者やパッケージの開発者、そしてシステムの実装者によって使われることを想定して策定されました。ただし、この標準はあくまでリファレンスであり、Unix のファイルシステムやディレクトリ階層を管理する方法のチュートリアルではありません。''"<br />
<br />
===共有可能ファイルと共有不能ファイル===<br />
'''共有可能'''ファイルとはあるホストで保存されていながら他者からも利用できるファイルです。'''共有不能'''ファイルは共有できないファイルのことです。例えば、ユーザーのホームディレクトリ内のファイルは共有可能であり、デバイスのロックファイルは共有不能です。<br />
<br />
===静的ファイルと可変ファイル===<br />
'''静的'''ファイルとは例えば、バイナリやライブラリ、ドキュメントなどのシステムの管理者以外からは変更を加えられることがないファイルを意味します。'''可変'''ファイルは静的ファイルでないファイルとして定義されます。<br />
<br />
== ディレクトリ ==<br />
===root ファイルシステム===<br />
root ファイルシステム (スラッシュ記号 ('''/''') で表されます) は他の全てのファイルシステムの根幹となるファイルシステムです。階層の一番上に位置します。たとえファイルやディレクトリが別の物理デバイスに保存されていたとしても、全てのファイルとディレクトリは root ディレクトリ "/" 下に配置されます。root ファイルシステムの中身だけでシステムを起動・復旧・修復できるようになっている必要があります。<br />
<br />
===<strike>/bin: 重要なコマンドラインバイナリ</strike> (廃止)===<br />
シングルユーザーモードで、全てのユーザーから利用できるバイナリを置くための伝統的なディレクトリです (例: cat, ls, cp)。/bin のプログラムはたとえ / を含むパーティションしかマウントされてないときも利用することができます。実際には、Arch では必要なライブラリは全て /usr/lib に存在しています。2013年6月から、[https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /bin は /usr/bin に統合されました]。{{Pkg|filesystem}} パッケージには /bin から /usr/bin へのシンボリックリンクが含まれており、全てのパッケージは /usr/bin にインストールされるようになっています。<br />
<br />
===/boot: ブートローダーの静的なファイル===<br />
共有不能の、静的なディレクトリです。ブートローダーの設定ファイルやブートローダーのステージだけでなく、カーネルや ramdisk イメージも含みます。/boot にはカーネルがユーザー空間のプログラムを実行する前に使用されるデータも保存されます。マスターブートセクタやセクターマップファイルなどです。<br />
<br />
===/dev: デバイスファイル===<br />
Essential device nodes created by udev during the boot process and as machine hardware is discovered by events. This directory highlights one important aspect of the UNIX filesystem - everything is a file or a directory. Exploring this directory will reveal many files, each representing a hardware component of the system. The majority of devices are either block or character devices; however other types of devices exist and can be created. In general, 'block devices' are devices that store or hold data, whereas 'character devices' can be thought of as devices that transmit or transfer data. For example, hard disk drives and optical drives are categorized as block devices while serial ports, mice and USB ports are all character devices.<br />
<br />
===/etc: ホスト固有の設定===<br />
Host-specific, unsharable configuration files shall be placed in the /etc directory. If more than one configuration file is required for an application, it is customary to use a subdirectory in order to keep the /etc/ area as clean as possible. It is considered good practice to make frequent backups of this directory as it contains all system related configuration files. <br />
<br />
====/etc/X11====<br />
X Window System の設定ファイル。<br />
<br />
=====/etc/X11/xinit=====<br />
xinit configuration files. 'xinit' is a configuration method of starting up an X session that is designed to be used as part of a script. <br />
<br />
=====/etc/X11/xinit/xinitrc=====<br />
Global xinitrc file, used by all X sessions started by xinit (startx). Its usage is of course overridden by a .xinitrc file located in the home directory of a user.<br />
<br />
===/home: ユーザーディレクトリ===<br />
UNIX is a multi-user environment. Therefore, each user is also assigned a specific directory that is accessible only to them and to the root user. These are the user home directories, which can be found under '/home/$USER' (~/). Within their home directory, a user can write files, delete them, install programs, etc. Users' home directories contain their data and personal configuration files, the so-called 'dot files' (their name is preceded by a dot), which are 'hidden'. To view dotfiles, enable the appropriate option in your file manager or run ls with the -a switch. If there is a conflict between personal and system wide configuration files, the settings in the personal file will prevail. Dotfiles most likely to be altered by the end user include .xinitrc and .bashrc files. The configuration files for xinit and Bash respectively. They allow the user the ability to change the window manager to be started upon login and also aliases, user-specified commands and environment variables respectively. When a user is created, their dotfiles shall be taken from the /etc/skel directory where system sample files reside. <br />
<br />
Directory /home can become quite large as it is typically used for storing downloads, compiling, installing and running programs, mail, collections of multimedia files etc.<br />
<br />
===/lost+found: ファイルシステム固有の復元可能なデータ===<br />
UNIX-like operating systems must execute a proper shutdown sequence. At times, a system might crash or a power failure might take the machine down. Either way, at the next boot, a filesystem check using the ''fsck'' program shall be performed. ''Fsck'' will go through the system and try to recover any corrupt files that it finds. The result of this recovery operation will be placed in this directory. The files recovered are not likely to be complete or make much sense but there always is a chance that something worthwhile is recovered.<br />
<br />
===/mnt: 一時的なマウントポイント===<br />
This is a generic mount point for temporary filesystems or devices. Mounting is the process of making a filesystem available to the system. After mounting, files will be accessible under the mount-point. Additional mount-points (subdirectories) may be created under /mnt/. There is no limitation to creating a mount-point anywhere on the system, but by convention and for practicality, littering a file system with mount-points should be avoided.<br />
<br />
===/opt: 問題のあるパッケージ===<br />
Packages and large static files that do not fit cleanly into the above GNU filesystem layout can be placed in /opt. FHS 2.3 denotes /opt as reserved for the installation of add-on application software packages. A package placing files in the /opt/ directory creates a directory bearing the same name as the package. This directory in turn holds files that otherwise would be scattered throughout the file system.<br />
For example, the acrobat package has Browser, Reader, and Resource<br />
directories sitting at the same level as the bin directory. This<br />
doesn't fit into a normal GNU filesystem layout, so Arch places all the<br />
files in a subdirectory of /opt.<br />
<br />
===/proc: プロセス情報===<br />
Directory /proc is very special in that it is also a virtual filesystem. It is sometimes referred to as the ''process information pseudo-file system''. It doesn't contain 'real' files, but rather, runtime system information (e.g. system memory, devices mounted, hardware configuration, etc). For this reason it can be regarded as a control and information center for the kernel. In fact, quite a lot of system utilities are simply calls to files in this directory. For example, 'lsmod' is the same as 'cat /proc/modules' while 'lspci' is a synonym for 'cat /proc/pci'. By altering files located in this directory, kernel parameters may be read/changed (sysctl) while the system is running.<br />
<br />
The most distinctive facet about files in this directory is the fact that all of them have a file size of 0, with the exception of '''kcore, mounts''' and '''self'''. <br />
<br />
===/root: 管理者ディレクトリ===<br />
Home directory of the System Administrator, 'root'. This may be somewhat confusing, ('/root under root') but historically, '/' was root's home directory (hence the name of the Administrator account). To keep things tidier, 'root' eventually got its own home directory. Why not '/home/root'? Because '/home' is often located on a different partition or even on another system and would thus be inaccessible to 'root' when - for whatever reason - only '/' is mounted.<br />
<br />
=== /run: 一時的な実行時データ===<br />
The /run mountpoint is supposed to be a tmpfs mounted during early boot, available and writable to for all tools at any time during bootup. [[systemd]], [[udev]] or mdadm that are required early in the boot process require this directory, because /var can be implemented as a separate file system to be mounted at a later stage in the start-up process. It replaces /var/run/, which becomes a symlink of /run.<br />
<br />
===<strike>/sbin: システムバイナリ</strike> (廃止)===<br />
Traditionally UNIX discriminates between 'normal' executables and those used for system maintenance and/or administrative tasks. The latter were supposed to reside either here or - the less important ones - in /usr/sbin. Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. In practice, programs in /sbin require /usr to be mounted as all the necessary libraries are in /usr/lib. As of June 2013, [https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /sbin and /usr/sbin were merged into /usr/bin]. The {{Pkg|filesystem}} package provides symlinks from /sbin and /usr/sbin to /usr/bin, and all packages should be updated to explicitly install to /usr/bin.<br />
<br />
===/srv: サービスデータ===<br />
Site-specific data which is served by the system. The main purpose of specifying this is so that users may find the location of the data files for a particular service, and so that services which require a single tree for read-only data, writable data and scripts (such as CGI scripts) can be reasonably placed. Data of interest to a specific user shall be placed in that user's home directory.<br />
<br />
===/sys: 仮想ファイルシステム===<br />
Virtual file system provided by the Linux kernel. By using virtual files, sysfs exports information about various kernel subsystems, hardware devices and associated device drivers from the kernel's device model to user space. In addition to providing information about various devices and kernel subsystems, exported virtual files are also used for their configuring.<br />
<br />
===/tmp: 一時的なファイル===<br />
This directory contains files that are required temporarily. Many programs use this to create lock files and for temporary storage of data. Do not remove files from this directory unless you know exactly what you are doing! Many of these files are important for currently running programs and deleting them may result in a system crash. On most systems, old files in this directory are cleared out at boot or at daily intervals.<br />
<br />
===/usr: 共有可能な、読み取り専用データ=== <br />
While root is the primary filesystem, /usr is the secondary hierarchy, for user data, containing the majority of (multi-)user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except by the package manager (installation, update, upgrade). Any information that is host-specific or varies with time is stored elsewhere. <br />
<br />
Aside from /home, /usr usually contains by far the largest share of data on a system. Hence, this is one of the most important directories in the system as it contains all the user binaries, their documentation, libraries, header files, etc. X and its supporting libraries can be found here. User programs like telnet, ftp, etc., are also placed here. In the original UNIX implementations, /usr (for ''user''), was where the home directories of the system's users were placed (that is to say, /usr/''username'' was then the directory now known as /home/''username''). Over time, /usr has become where userspace programs and data (as opposed to 'kernelspace' programs and data) reside. The name has not changed, but its meaning has narrowed and lengthened from ''everything user related'' to ''user usable programs and data''. As such, the backronym ''''U'''ser '''S'''ystem '''R'''esources' was created.<br />
<br />
====/usr/bin: バイナリ====<br />
コマンドバイナリ。このディレクトリにはシステム上のバイナリ (アプリケーション) のほとんどが含まれます。このディレクトリ内の実行ファイルは様々です。例えば vim や gcc、gnome-session などがここに置かれます。昔は、このディレクトリには root 権限を必要としない、そしてシングルユーザーモードで必要ないバイナリだけを置くことになっていました。しかしながら、この決まりごとは既に強制ではなくなっており、Arch の開発陣は <strike>全てのバイナリをこのディレクトリに移動することを計画</strike> 全てのバイナリをこのディレクトリに移動しています。<br />
<br />
====/usr/include: ヘッダーファイル====<br />
ユーザー空間のソースコードをコンパイルするのに必要なヘッダーファイル。<br />
<br />
====/usr/lib: ライブラリ====<br />
{{Note|The {{ic|/lib}} directory becomes a symlink to {{ic|/usr/lib}}. [https://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/ Here] is the news. If you encounter error during this update. Please see [[DeveloperWiki:usrlib]] for solution.}}<br />
Contains application private data (kernel modules, systemd services, udev rules, etc) and shared library images (the C programming code library). Libraries are collections of frequently used program routines and are readily identifiable through their filename extension of *.so. They are essential for basic system functionality. Kernel modules (drivers) are in the subdirectory /lib/modules/<kernel-version>.<br />
<br />
====<strike>/usr/sbin: システムバイナリ</strike> (廃止)====<br />
Non-essential system binaries of use to the system administrator. As of June 2013, [https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /usr/sbin was merged into /usr/bin]. The {{Pkg|filesystem}} package provides symlinks from /usr/sbin to /usr/bin, and all packages should now explicitly install to /usr/bin.<br />
<br />
====/usr/share: アーキテクチャに依存しないデータ====<br />
This directory contains 'shareable', architecture-independent files (docs, icons, fonts etc). Note, however, that /usr/share is generally not intended to be shared by different operating systems or by different releases of the same operating system. Any program or package which contains or requires data that do not need to be modified should store these data in /usr/share (or /usr/local/share, if manually installed - see below). It is recommended that a subdirectory be used in /usr/share for this purpose.<br />
<br />
====/usr/src: ソースコード====<br />
<!-- The 'linux' sub-directory holds the Linux kernel sources, and header-files. --><br />
'linux'のサブディレクトリは、Linuxのカーネルのソースとヘッダファイルを格納しています。<br />
<br />
====/usr/local: ローカル階層====<br />
Optional tertiary hierarchy for local data. The original idea behind /usr/local was to have a separate ('local') '/usr' directory on every machine besides /usr itself, which might be mounted read-only from somewhere else. It copies the structure of /usr. These days, /usr/local is widely regarded as a good place in which to keep self-compiled or third-party programs. This directory is empty by default in Arch Linux. It may be used for manually compiled software installations if desired. [[pacman]] installs to /usr, therefore, manually compiled/installed software installed to /usr/local may peacefully co-exist with pacman-tracked system software.<br />
<br />
===/var: 可変ファイル===<br />
Variable files, such as logs, spool files, and temporary e-mail files. On Arch, the [[ABS]] tree and pacman cache also reside here. Why not put the variable and transient data into /usr/? Because there might be circumstances when /usr/ is mounted as read-only, e.g. if it is on a CD or on another computer. '/var/' contains variable data, i.e. files and directories the system must be able to write to during operation, whereas /usr/ shall only contain static data.<br />
Some directories can be put onto separate partitions or systems, e.g. for easier backups, due to network topology or security concerns. Other directories have to be on the root partition, because they are vital for the boot process. 'Mountable' directories are: '/home', '/mnt', '/tmp' and '/var'. Essential for booting are: '/bin', '/boot', '/dev', '/etc', '/lib', '/proc', '/sbin' and '/usr'. <br />
<br />
====/var/abs====<br />
The [[ABS]] tree. A ports-like package build system hierarchy containing build scripts within subdirectories corresponding to all installable Arch software.<br />
<br />
====/var/cache/pacman/pkg====<br />
pacman のパッケージキャッシュ。<br />
<br />
====/var/lib: 状態情報====<br />
Persistent data modified by programs as they run (e.g. databases, packaging system metadata etc.).<br />
<br />
====/var/log: ログファイル====<br />
ログファイル。<br />
<br />
====/var/mail: ユーザーのメール====<br />
<!-- Deprecated location for users' mailboxes. --><br />
ユーザのメールボックスに推奨されていない場所です。<br />
<br />
====/var/spool: キュー====<br />
Spool for tasks waiting to be processed (e.g. print queues and unread mail).<br />
<br />
=====/var/spool/mail=====<br />
Shareable directory for users' mailboxes.<br />
<br />
====/var/tmp: 保持される可能性がある一時的なファイル====<br />
Temporary files to be preserved between reboots.<br />
<br />
==参照==<br />
*[[wikipedia:ja:Filesystem Hierarchy Standard]]<br />
*[http://www.pathname.com/fhs/ Linux FHS ホームページ]</div>はつせhttps://wiki.archlinux.jp/index.php?title=Arch_%E3%83%95%E3%82%A1%E3%82%A4%E3%83%AB%E3%82%B7%E3%82%B9%E3%83%86%E3%83%A0%E9%9A%8E%E5%B1%A4&diff=3615Arch ファイルシステム階層2015-08-29T06:08:31Z<p>はつせ: /* /usr/src: ソースコード */</p>
<hr />
<div>[[Category:ファイルシステム]]<br />
[[en:Arch filesystem hierarchy]]<br />
[[it:Filesystem Hierarchy Standard]]<br />
[[ru:Filesystem Hierarchy Standard]]<br />
[[zh-CN:Arch filesystem hierarchy]]<br />
Arch Linux は他の多数のディストリビューションと同じようにファイルシステム階層標準に従っています。それぞれのディレクトリについてその目的を説明するのに加えて、この記事では Arch 固有の事情についても説明しています。<br />
<br />
== ファイルシステム階層標準 ==<br />
[http://www.pathname.com/fhs Filesystem Hierarchy Standard (FHS) のホームページ] より:<br />
:"''ファイルシステムスタンダードは Unix ディストリビューションの開発者やパッケージの開発者、そしてシステムの実装者によって使われることを想定して策定されました。ただし、この標準はあくまでリファレンスであり、Unix のファイルシステムやディレクトリ階層を管理する方法のチュートリアルではありません。''"<br />
<br />
===共有可能ファイルと共有不能ファイル===<br />
'''共有可能'''ファイルとはあるホストで保存されていながら他者からも利用できるファイルです。'''共有不能'''ファイルは共有できないファイルのことです。例えば、ユーザーのホームディレクトリ内のファイルは共有可能であり、デバイスのロックファイルは共有不能です。<br />
<br />
===静的ファイルと可変ファイル===<br />
'''静的'''ファイルとは例えば、バイナリやライブラリ、ドキュメントなどのシステムの管理者以外からは変更を加えられることがないファイルを意味します。'''可変'''ファイルは静的ファイルでないファイルとして定義されます。<br />
<br />
== ディレクトリ ==<br />
===root ファイルシステム===<br />
root ファイルシステム (スラッシュ記号 ('''/''') で表されます) は他の全てのファイルシステムの根幹となるファイルシステムです。階層の一番上に位置します。たとえファイルやディレクトリが別の物理デバイスに保存されていたとしても、全てのファイルとディレクトリは root ディレクトリ "/" 下に配置されます。root ファイルシステムの中身だけでシステムを起動・復旧・修復できるようになっている必要があります。<br />
<br />
===<strike>/bin: 重要なコマンドラインバイナリ</strike> (廃止)===<br />
シングルユーザーモードで、全てのユーザーから利用できるバイナリを置くための伝統的なディレクトリです (例: cat, ls, cp)。/bin のプログラムはたとえ / を含むパーティションしかマウントされてないときも利用することができます。実際には、Arch では必要なライブラリは全て /usr/lib に存在しています。2013年6月から、[https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /bin は /usr/bin に統合されました]。{{Pkg|filesystem}} パッケージには /bin から /usr/bin へのシンボリックリンクが含まれており、全てのパッケージは /usr/bin にインストールされるようになっています。<br />
<br />
===/boot: ブートローダーの静的なファイル===<br />
共有不能の、静的なディレクトリです。ブートローダーの設定ファイルやブートローダーのステージだけでなく、カーネルや ramdisk イメージも含みます。/boot にはカーネルがユーザー空間のプログラムを実行する前に使用されるデータも保存されます。マスターブートセクタやセクターマップファイルなどです。<br />
<br />
===/dev: デバイスファイル===<br />
Essential device nodes created by udev during the boot process and as machine hardware is discovered by events. This directory highlights one important aspect of the UNIX filesystem - everything is a file or a directory. Exploring this directory will reveal many files, each representing a hardware component of the system. The majority of devices are either block or character devices; however other types of devices exist and can be created. In general, 'block devices' are devices that store or hold data, whereas 'character devices' can be thought of as devices that transmit or transfer data. For example, hard disk drives and optical drives are categorized as block devices while serial ports, mice and USB ports are all character devices.<br />
<br />
===/etc: ホスト固有の設定===<br />
Host-specific, unsharable configuration files shall be placed in the /etc directory. If more than one configuration file is required for an application, it is customary to use a subdirectory in order to keep the /etc/ area as clean as possible. It is considered good practice to make frequent backups of this directory as it contains all system related configuration files. <br />
<br />
====/etc/X11====<br />
X Window System の設定ファイル。<br />
<br />
=====/etc/X11/xinit=====<br />
xinit configuration files. 'xinit' is a configuration method of starting up an X session that is designed to be used as part of a script. <br />
<br />
=====/etc/X11/xinit/xinitrc=====<br />
Global xinitrc file, used by all X sessions started by xinit (startx). Its usage is of course overridden by a .xinitrc file located in the home directory of a user.<br />
<br />
===/home: ユーザーディレクトリ===<br />
UNIX is a multi-user environment. Therefore, each user is also assigned a specific directory that is accessible only to them and to the root user. These are the user home directories, which can be found under '/home/$USER' (~/). Within their home directory, a user can write files, delete them, install programs, etc. Users' home directories contain their data and personal configuration files, the so-called 'dot files' (their name is preceded by a dot), which are 'hidden'. To view dotfiles, enable the appropriate option in your file manager or run ls with the -a switch. If there is a conflict between personal and system wide configuration files, the settings in the personal file will prevail. Dotfiles most likely to be altered by the end user include .xinitrc and .bashrc files. The configuration files for xinit and Bash respectively. They allow the user the ability to change the window manager to be started upon login and also aliases, user-specified commands and environment variables respectively. When a user is created, their dotfiles shall be taken from the /etc/skel directory where system sample files reside. <br />
<br />
Directory /home can become quite large as it is typically used for storing downloads, compiling, installing and running programs, mail, collections of multimedia files etc.<br />
<br />
===/lost+found: ファイルシステム固有の復元可能なデータ===<br />
UNIX-like operating systems must execute a proper shutdown sequence. At times, a system might crash or a power failure might take the machine down. Either way, at the next boot, a filesystem check using the ''fsck'' program shall be performed. ''Fsck'' will go through the system and try to recover any corrupt files that it finds. The result of this recovery operation will be placed in this directory. The files recovered are not likely to be complete or make much sense but there always is a chance that something worthwhile is recovered.<br />
<br />
===/mnt: 一時的なマウントポイント===<br />
This is a generic mount point for temporary filesystems or devices. Mounting is the process of making a filesystem available to the system. After mounting, files will be accessible under the mount-point. Additional mount-points (subdirectories) may be created under /mnt/. There is no limitation to creating a mount-point anywhere on the system, but by convention and for practicality, littering a file system with mount-points should be avoided.<br />
<br />
===/opt: 問題のあるパッケージ===<br />
Packages and large static files that do not fit cleanly into the above GNU filesystem layout can be placed in /opt. FHS 2.3 denotes /opt as reserved for the installation of add-on application software packages. A package placing files in the /opt/ directory creates a directory bearing the same name as the package. This directory in turn holds files that otherwise would be scattered throughout the file system.<br />
For example, the acrobat package has Browser, Reader, and Resource<br />
directories sitting at the same level as the bin directory. This<br />
doesn't fit into a normal GNU filesystem layout, so Arch places all the<br />
files in a subdirectory of /opt.<br />
<br />
===/proc: プロセス情報===<br />
Directory /proc is very special in that it is also a virtual filesystem. It is sometimes referred to as the ''process information pseudo-file system''. It doesn't contain 'real' files, but rather, runtime system information (e.g. system memory, devices mounted, hardware configuration, etc). For this reason it can be regarded as a control and information center for the kernel. In fact, quite a lot of system utilities are simply calls to files in this directory. For example, 'lsmod' is the same as 'cat /proc/modules' while 'lspci' is a synonym for 'cat /proc/pci'. By altering files located in this directory, kernel parameters may be read/changed (sysctl) while the system is running.<br />
<br />
The most distinctive facet about files in this directory is the fact that all of them have a file size of 0, with the exception of '''kcore, mounts''' and '''self'''. <br />
<br />
===/root: 管理者ディレクトリ===<br />
Home directory of the System Administrator, 'root'. This may be somewhat confusing, ('/root under root') but historically, '/' was root's home directory (hence the name of the Administrator account). To keep things tidier, 'root' eventually got its own home directory. Why not '/home/root'? Because '/home' is often located on a different partition or even on another system and would thus be inaccessible to 'root' when - for whatever reason - only '/' is mounted.<br />
<br />
=== /run: 一時的な実行時データ===<br />
The /run mountpoint is supposed to be a tmpfs mounted during early boot, available and writable to for all tools at any time during bootup. [[systemd]], [[udev]] or mdadm that are required early in the boot process require this directory, because /var can be implemented as a separate file system to be mounted at a later stage in the start-up process. It replaces /var/run/, which becomes a symlink of /run.<br />
<br />
===<strike>/sbin: システムバイナリ</strike> (廃止)===<br />
Traditionally UNIX discriminates between 'normal' executables and those used for system maintenance and/or administrative tasks. The latter were supposed to reside either here or - the less important ones - in /usr/sbin. Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. In practice, programs in /sbin require /usr to be mounted as all the necessary libraries are in /usr/lib. As of June 2013, [https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /sbin and /usr/sbin were merged into /usr/bin]. The {{Pkg|filesystem}} package provides symlinks from /sbin and /usr/sbin to /usr/bin, and all packages should be updated to explicitly install to /usr/bin.<br />
<br />
===/srv: サービスデータ===<br />
Site-specific data which is served by the system. The main purpose of specifying this is so that users may find the location of the data files for a particular service, and so that services which require a single tree for read-only data, writable data and scripts (such as CGI scripts) can be reasonably placed. Data of interest to a specific user shall be placed in that user's home directory.<br />
<br />
===/sys: 仮想ファイルシステム===<br />
Virtual file system provided by the Linux kernel. By using virtual files, sysfs exports information about various kernel subsystems, hardware devices and associated device drivers from the kernel's device model to user space. In addition to providing information about various devices and kernel subsystems, exported virtual files are also used for their configuring.<br />
<br />
===/tmp: 一時的なファイル===<br />
This directory contains files that are required temporarily. Many programs use this to create lock files and for temporary storage of data. Do not remove files from this directory unless you know exactly what you are doing! Many of these files are important for currently running programs and deleting them may result in a system crash. On most systems, old files in this directory are cleared out at boot or at daily intervals.<br />
<br />
===/usr: 共有可能な、読み取り専用データ=== <br />
While root is the primary filesystem, /usr is the secondary hierarchy, for user data, containing the majority of (multi-)user utilities and applications. /usr is shareable, read-only data. This means that /usr shall be shareable between various hosts and must not be written to, except by the package manager (installation, update, upgrade). Any information that is host-specific or varies with time is stored elsewhere. <br />
<br />
Aside from /home, /usr usually contains by far the largest share of data on a system. Hence, this is one of the most important directories in the system as it contains all the user binaries, their documentation, libraries, header files, etc. X and its supporting libraries can be found here. User programs like telnet, ftp, etc., are also placed here. In the original UNIX implementations, /usr (for ''user''), was where the home directories of the system's users were placed (that is to say, /usr/''username'' was then the directory now known as /home/''username''). Over time, /usr has become where userspace programs and data (as opposed to 'kernelspace' programs and data) reside. The name has not changed, but its meaning has narrowed and lengthened from ''everything user related'' to ''user usable programs and data''. As such, the backronym ''''U'''ser '''S'''ystem '''R'''esources' was created.<br />
<br />
====/usr/bin: バイナリ====<br />
コマンドバイナリ。このディレクトリにはシステム上のバイナリ (アプリケーション) のほとんどが含まれます。このディレクトリ内の実行ファイルは様々です。例えば vim や gcc、gnome-session などがここに置かれます。昔は、このディレクトリには root 権限を必要としない、そしてシングルユーザーモードで必要ないバイナリだけを置くことになっていました。しかしながら、この決まりごとは既に強制ではなくなっており、Arch の開発陣は <strike>全てのバイナリをこのディレクトリに移動することを計画</strike> 全てのバイナリをこのディレクトリに移動しています。<br />
<br />
====/usr/include: ヘッダーファイル====<br />
ユーザー空間のソースコードをコンパイルするのに必要なヘッダーファイル。<br />
<br />
====/usr/lib: ライブラリ====<br />
{{Note|The {{ic|/lib}} directory becomes a symlink to {{ic|/usr/lib}}. [https://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/ Here] is the news. If you encounter error during this update. Please see [[DeveloperWiki:usrlib]] for solution.}}<br />
Contains application private data (kernel modules, systemd services, udev rules, etc) and shared library images (the C programming code library). Libraries are collections of frequently used program routines and are readily identifiable through their filename extension of *.so. They are essential for basic system functionality. Kernel modules (drivers) are in the subdirectory /lib/modules/<kernel-version>.<br />
<br />
====<strike>/usr/sbin: システムバイナリ</strike> (廃止)====<br />
Non-essential system binaries of use to the system administrator. As of June 2013, [https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ /usr/sbin was merged into /usr/bin]. The {{Pkg|filesystem}} package provides symlinks from /usr/sbin to /usr/bin, and all packages should now explicitly install to /usr/bin.<br />
<br />
====/usr/share: アーキテクチャに依存しないデータ====<br />
This directory contains 'shareable', architecture-independent files (docs, icons, fonts etc). Note, however, that /usr/share is generally not intended to be shared by different operating systems or by different releases of the same operating system. Any program or package which contains or requires data that do not need to be modified should store these data in /usr/share (or /usr/local/share, if manually installed - see below). It is recommended that a subdirectory be used in /usr/share for this purpose.<br />
<br />
====/usr/src: ソースコード====<br />
<!-- The 'linux' sub-directory holds the Linux kernel sources, and header-files. --><br />
'linux'のサブディレクトリは、Linuxのカーネルのソースとヘッダファイルを格納しています。<br />
<br />
====/usr/local: ローカル階層====<br />
Optional tertiary hierarchy for local data. The original idea behind /usr/local was to have a separate ('local') '/usr' directory on every machine besides /usr itself, which might be mounted read-only from somewhere else. It copies the structure of /usr. These days, /usr/local is widely regarded as a good place in which to keep self-compiled or third-party programs. This directory is empty by default in Arch Linux. It may be used for manually compiled software installations if desired. [[pacman]] installs to /usr, therefore, manually compiled/installed software installed to /usr/local may peacefully co-exist with pacman-tracked system software.<br />
<br />
===/var: 可変ファイル===<br />
Variable files, such as logs, spool files, and temporary e-mail files. On Arch, the [[ABS]] tree and pacman cache also reside here. Why not put the variable and transient data into /usr/? Because there might be circumstances when /usr/ is mounted as read-only, e.g. if it is on a CD or on another computer. '/var/' contains variable data, i.e. files and directories the system must be able to write to during operation, whereas /usr/ shall only contain static data.<br />
Some directories can be put onto separate partitions or systems, e.g. for easier backups, due to network topology or security concerns. Other directories have to be on the root partition, because they are vital for the boot process. 'Mountable' directories are: '/home', '/mnt', '/tmp' and '/var'. Essential for booting are: '/bin', '/boot', '/dev', '/etc', '/lib', '/proc', '/sbin' and '/usr'. <br />
<br />
====/var/abs====<br />
The [[ABS]] tree. A ports-like package build system hierarchy containing build scripts within subdirectories corresponding to all installable Arch software.<br />
<br />
====/var/cache/pacman/pkg====<br />
pacman のパッケージキャッシュ。<br />
<br />
====/var/lib: 状態情報====<br />
Persistent data modified by programs as they run (e.g. databases, packaging system metadata etc.).<br />
<br />
====/var/log: ログファイル====<br />
ログファイル。<br />
<br />
====/var/mail: ユーザーのメール====<br />
Deprecated location for users' mailboxes.<br />
<br />
====/var/spool: キュー====<br />
Spool for tasks waiting to be processed (e.g. print queues and unread mail).<br />
<br />
=====/var/spool/mail=====<br />
Shareable directory for users' mailboxes.<br />
<br />
====/var/tmp: 保持される可能性がある一時的なファイル====<br />
Temporary files to be preserved between reboots.<br />
<br />
==参照==<br />
*[[wikipedia:ja:Filesystem Hierarchy Standard]]<br />
*[http://www.pathname.com/fhs/ Linux FHS ホームページ]</div>はつせ