Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
W dniu 2014-01-12 10:09, wishmaster pisze:
>> I would also recommend ezjails. Using fat jails is often completely
>> unnecessary.
>
> Do you think using ezjail you will obtain "thin" jails? You are wrong. Setup
> 5...10 jails for applications: one jail for web-applications on php, one for
> j
> W dniu 2014-01-12 10:09, wishmaster pisze:
>
> >> I would also recommend ezjails. Using fat jails is often completely
> >> unnecessary.
> >
> > Do you think using ezjail you will obtain "thin" jails?
> > You are wrong. Setup 5...10 jails for applications: one jail for
> > web-applications on
I like to use jails.conf and the sysutils/jail2/ port.
I create a very basic jail and later just clone it taking advantage of ZFS.
I share the /usr/ports from the host with the jails, but let each jail have
their own files, so that later if needed, I can just dump the full jail and
move it to a
I know, top posting
Hi.
Other than the directory structure illustrated there, you've confused me. (Not
difficult!)
The problem I'm finding, is that everyone assumes everyone else knows what
everyone is talking about, in detail! I freely admit I don't! (But I'm
slowly
learning.)
So..
Hi, Reference:
> From: g8kbvd...@googlemail.com
> Date: Mon, 13 Jan 2014 14:41:53 -
g8kbvd...@googlemail.com wrote:
> I know, top posting
So don't, too many lately.
Comply with the project's mail list rules !
On average top posters are less clued up & less conformant to
Hi, sorry for the confusion, I will go a little more in detail trying to
explain more my use case.
To what it concerns to jails:
Basic setup:
FreeBSD Host with N jails.
For this I create a basic, light jail (custom src.conf) , the one later is
cloned (ZFS), and configuration is in jails.conf.
