summaryrefslogtreecommitdiff
path: root/man1/ezjail-admin.1
diff options
context:
space:
mode:
authorerdgeist <erdgeist@erdgeist.org>2006-02-09 01:21:56 +0000
committererdgeist <erdgeist@erdgeist.org>2006-02-09 01:21:56 +0000
commit3a75a73eec35307b281342c222a9b0dfdadbbcd1 (patch)
tree631f8dbd43d8591c372d70a11b70d491c355672c /man1/ezjail-admin.1
parentc270955ae0294666d25984244588456723579b38 (diff)
Radical change of what an ezjail flavour is. The old way got me stuck.
Diffstat (limited to 'man1/ezjail-admin.1')
-rwxr-xr-xman1/ezjail-admin.150
1 files changed, 6 insertions, 44 deletions
diff --git a/man1/ezjail-admin.1 b/man1/ezjail-admin.1
index fd19f55..cb82e85 100755
--- a/man1/ezjail-admin.1
+++ b/man1/ezjail-admin.1
@@ -114,8 +114,7 @@ values for having ports in jails is created in the template jail.
114.SH FLAVOURS 114.SH FLAVOURS
115.B ezjail-admin 115.B ezjail-admin
116provides an easy way to create many jails with similar or identical 116provides an easy way to create many jails with similar or identical
117properties. Currently it supports creating users, installing files and 117properties.
118installing packages.
119 118
120A sample flavour config directory resides under 119A sample flavour config directory resides under
121.I EZJAIL_PREFIX/share/examples/ezjail/default/. 120.I EZJAIL_PREFIX/share/examples/ezjail/default/.
@@ -125,49 +124,12 @@ encouraged to use it as a template for your flavours.
125If a flavour is selected on jail creation, the flavour root is being 124If a flavour is selected on jail creation, the flavour root is being
126copied to the new Jails root, mostly containing an 125copied to the new Jails root, mostly containing an
127.I /ezjail.flavour . 126.I /ezjail.flavour .
128If the Jail starts up for the first time it runs a setup script found 127If the Jail starts up for the first time this script is run.
129at 128
130.I /etc/rc.d/ezjail-config.sh. 129In its default form it will create some groups and users, change the
131 130ownership of some files and installs all packages residing under /pkg.
132This script will create some users specified in the flavour config.
133It will then chown files specified in the flavour config. (This allows
134chown-ing files to users only created by the config script.) All
135packages residing under
136.I /pkg
137will be pkg_install-ed. Finally the script
138.I /ezjail.postinstall
139is being sourced, if it exists.
140
141.I ezjail-config.sh
142then removes all traces, including itself.
143.SH EZJAIL.FLAVOUR
144The ezjail.flavour file found in a flavour directory usually provides
145two variables:
146
147.B ezjail_flavour_users
148.br
149a white space separated list of colon separated entries passed to the
150pw command after some processing. Refer to the pw(8) man page for more
151information. Format of an entry in the list is:
152
153username:uid:group[,group2,..]:gid[,gid2,..]:comment:pw:[-]home:shell
154
155where each group specified in the group list is being created (with the
156given gid for each group) if possible and necessary, before the user is
157added to that group. The character '=' in the comment field is being
158substituted by ' ' (space) to simplify escaping. The pw is being written
159verbatim to the passwd db, see pw(8). If the home directory begins with
160a '-' (dash), it is meant not to be created by the pw command. The dash
161will of course be removed. It is not possible to specify a shell here
162that will be installed by a package in /pkg.
163
164.B ezjail_flavour_files
165.br
166a white space separated list of colon separated entries passed to the
167chown -R command after some processing. Refer to the chown(8) man page
168for more information. Format of an entry in the list is:
169 131
170user:group:file[:file2...] 132It allows you to add some post install actions.
171.SH EXAMPLES 133.SH EXAMPLES
172ezjail-admin update -p 134ezjail-admin update -p
173.br 135.br