Date: Wed, 21 Mar 2007 11:30:26 -0400 From: Bill Moran <wmoran@potentialtech.com> To: "Jonathan Horne" <freebsd@dfwlp.com> Cc: freebsd-questions@freebsd.org Subject: Re: started playing with jails Message-ID: <20070321113026.73d33795.wmoran@potentialtech.com> In-Reply-To: <42991.167.246.36.14.1174490156.squirrel@webmail.dfwlp.org> References: <42991.167.246.36.14.1174490156.squirrel@webmail.dfwlp.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to "Jonathan Horne" <freebsd@dfwlp.com>: > i started playing with jails today, and after following and re-following the man > page and the freebsddiary article a few times, i finally got it to work! i have > one jail that starts on startup, and actually the hump i was getting over was > getting the jail to actually kick off the sshd daemon. all that is working, and > i can reboot my host, and then log into the jail that auto-starts via ssh. > > a couple of general questions that i cannot find the answers to: > > 1) if i want more than one jail, what is the proper syntax in the host's > /etc/rc.conf file for the jail_list="jailed" statement? multiple jail_list > lines, or a single line that specifies more than one jail? > 2) what happens to a jail when i 'shutdown -p now' on the host? what caveats do > i need to watch for when rebooting or shutting down the host? > 3) i would like to build some ports in my jailed process, but for my > environment, this requires mounting the export from my main box on my network. > so far, i am not able to mount a NFS share to /usr/ports (mount_nfs: /usr/ports: > Operation not permitted). If you're shooting purely for usability, I recommend the ezjail port, which adds some additional admin scripts on top of the stock jail system that (in my opinion) make things a lot easier. -- Bill Moran http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070321113026.73d33795.wmoran>