Re: New jail does not understand nullfs

On Sun, Dec 02, 2012 at 08:09:39AM -0700, Ian Lepore wrote:
> 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?
> 

mount.devfs means "mount devfs" :)

However, it indeed may be some issue with config parsing, e.g. some
mishandled whitespace.

Matt, in general this should work just fine. What revision are you using
to test? Can you attach this config instead of copy-pasting it?

-- 
Mateusz Guzik <mjguzik gmail.com>
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"