luzar722 at gmail.com
Tue Nov 15 17:48:31 UTC 2016
> On Mon, 14 Nov 2016, Ernie Luzar wrote:
>> doug wrote:
>>> I am using ezjail-3.4.2. Changing the jail dir as defined by
>>> ezjail_jaildir in /usr/local/etc/ezjail.conf does not work. Install
>>> does not honor this change. This is easy enough to get around with a
>>> symlink. Am I missing something here?
>>> There is no option to construct the base jail without a buildworld
>>> having been done. Is there a technical reason for this?
>>> Thanks as always for any thought.
>> If I read your post correctly, you want to change the default
>> directory location for basejail. IIRC ezjail has a default config file
>> where you can change the default basejail location. First change this
>> file and then issue the install option to generate the basejail from
>> the RELEASE version that matches what your running on the host.
>> If that is not what you are trying to do then you have to post a
>> better description of what your trying to do.
> Mistake was all mine. I had a dumb error in changing ezjail.conf. Thanks.
> My other question remains. Does having the jail have (potentially) a
> different userland than the host provide some functionality? I have
> always assumed the entire system needed to be updated at the same time.
> In any case the userland can/should not be a different release.
The ezjail basejail should contain the same RELEASE level as the host.
But will still work if sub-release is different between host and basejail.
The individual jails just contain the ports you have installed and can
be kept and used across sub-releases [ie; 10.0, 10.1, 10.3] but when
crossing a major release such as going from 9.x to 10.x or 10.x to 11.x
ports need to be updated in the individual jails or recreate the jail
and populate with desired ports.
I use qjail and find it more user friendly.
More information about the freebsd-questions