Date: Sun, 02 Dec 2012 08:09:39 -0700 From: Ian Lepore <freebsd@damnhippie.dyndns.org> To: Matt Donovan <kitchetech@gmail.com> Cc: current@freebsd.org Subject: Re: New jail does not understand nullfs Message-ID: <1354460979.69940.627.camel@revolution.hippie.lan> In-Reply-To: <CAD-N7OCoVuusZUgNqK8JH8D-8Fj%2BZsgqt83D7cj5wcu6h8E7qA@mail.gmail.com> References: <CAD-N7OCoVuusZUgNqK8JH8D-8Fj%2BZsgqt83D7cj5wcu6h8E7qA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2012-12-02 at 01:17 -0600, Matt Donovan wrote:
> When attempting to start the jail in question the following happens
>
>
> server# jail -c poudriere
> jail: poudriere: unknown parameter: allow.mount.nullfs
>
>
> Below is my jail.conf
>
> poudriere {
> name=poudriere;
> host.hostname=poudriere;
> ip4.addr="192.168.1.30";
> persist;
> children.max=10;
> allow.mount;
> mount.devfs;
> allow.mount.nullfs;
> allow.raw_sockets;
> allow.socket_af;
> allow.sysvipc;
> enforce_statfs=1;
> path=/newsystem/jail/poudriere;
> exec.stop="umount -a";
> }
>
> Does the switch not work yet? As I am using CURRENT with the latest
> revision.
>
That "mount.devfs" doesn't look right, should that have "allow." on the
front? I wonder if that's the problem and the error report is off by
one line or something?
-- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1354460979.69940.627.camel>