ezjail, branch RELEASE_3_1

Attaching the ZFS-dataset and configuring the CPUset didn't work when doing "start" without explicit jailnames. e.g. this happened during normal boot.

2010-02-18T12:22:26+00:00

Missing &&

2010-02-16T22:33:52+00:00

$0 is /etc/rc here, so doing rm -f "${0}" would leave the jail without /etc/rc after the first start.

2010-02-16T22:19:49+00:00

Oops, commited local change :-/

2010-02-16T22:03:37+00:00

fix the eval syntax

2010-02-16T22:02:10+00:00

* Create new jails with jail_JAILNAME_exec_start instead of jail_JAILNAME_exec

2010-02-14T23:34:37+00:00

* ezjail.sh replaces empty _exec_start with _exec and unsets _exec
* When writing the config obey old settings, don't overwrite with defaults

Make ezjail-list not wider than 80 chars, if possible

2010-02-11T17:32:25+00:00

Explain default and multiple flavours

2010-02-08T05:15:20+00:00

Consider this to be the second part of the changes that started in 1.247

2010-02-08T05:05:04+00:00

We no allow multiple flavours to be installed at once, feed them space separated to the -f option in ezjail-admin create
This installs several ezjail.flavour scripts into / of the new jail, enumerating them /ezjail.flavour.0001 through 9999
It also adds a new script to /etc/rc.d/ezjail-config in the new jail which executes /ezjail.flavour.* as it finds them.

On an unrelated note ezjail-admin delete and console will now use the onestop and onestart parameters if used with -f, so they even work with ezjail_enable not set.

Removing flavourizing shell scripts now is done in the installed ezjail-config

2010-02-08T04:57:35+00:00