Date: Tue, 25 Apr 2017 03:49:05 +0000 From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 218849] Remove rc.conf jail configuration via jail_* variables Message-ID: <bug-218849-2597-5UEVEce6Ow@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218849-2597@https.bugs.freebsd.org/bugzilla/> References: <bug-218849-2597@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218849 Chris Hutchinson <portmaster@bsdforge.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |portmaster@bsdforge.com --- Comment #5 from Chris Hutchinson <portmaster@bsdforge.com> --- (In reply to Miroslav Lachman from comment #4) > Or maybe there should not be 3rd party tools used in Handbook. There shou= ld > be documented steps using tools in base and link to freshports to many 3rd > party jail tools. Let the users choose. Can I simply add a plus one here? I couldn't agree more on this. It seems very odd to me to read "FreeBSD" documentation. Only to have it explain how to use it through the use of 3rd party software. Isn't it supposed to teach new users how to use the features _provided by FreeBSD? I see no reason not to touch lightly on 3rd party alternatives. But, honest= ly. Making the article primarily about 3rd party software is just wrong. >=20 > This is very similar problem to portmaster / portupgrade tools - they are > (were) used in Handbook but are not maintained well. They are lacking beh= ind > ports framework features and then some features are not easily implemented > because ports team does not want to break things for these tools... Good example, Miroslav, and thanks! :-) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218849-2597-5UEVEce6Ow>