Date: Sun, 20 Feb 2022 20:37:45 +0100 From: Jon Clausen <freebsd-questions@ymmv.dk> To: Doug Denault <doug@safeport.com> Cc: freebsd-questions@freebsd.org Subject: Re: jail.$jailname.conf not directly in /etc/ ? Message-ID: <20220220193745.rzbdsvqdhq7x3qih@c02qx0.local> In-Reply-To: <alpine.BSF.2.00.2202201054120.25129@bucksport.safeport.com> References: <20220219092824.6qmzo33es3w73nj5@c02qx0.local> <f9882bc-3ae-b91f-5bbc-22b6a6485c19@safeport.com> <20220220094656.3legbf6vs7wfm5vx@c02qx0.local> <alpine.BSF.2.00.2202201054120.25129@bucksport.safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-02-20 11:04:34 (-0500), Doug Denault wrote: > On Sun, 20 Feb 2022, Jon Clausen wrote: > > > On 2022-02-19 18:46:24 (+0000), doug wrote: > > > If it were me, I'd let sleeping jail configs lie :) > > > > That's probably good advice, but I'm not quite done prodding the stuff just > > yet. I see one possible "half way", as I hinted at a minute ago in another > > reply... > > Bending systems to our will or going where no one has gone before is a great > trait for sysadmins IMO. Everything learned about the innerads of FreeBSD > will most likely be useful at some point. Yeah I tend to agree. In this case, it was in large part about realizing that functions can be onverwritten, by (re)defining them "later". So essentially just shell stuff - but it's nice to be able to apply that sort of knowledge. > If however you solve your problem, > 6 months from now you likely will be the only one able to maintain and/or > extend it. Oh absolutely. But there is little risk anyone but me will ever maintain any of this, so... > Personally I find things like this fun. I've never had a job, > just a fun activity people have paid me to do. heh, yeah :) br /jon -- YMMV
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220220193745.rzbdsvqdhq7x3qih>