<HTML><BODY>+1. And even if talking about installation of the necessary software and not about the configuration, then why this? "<span style="color: #141412; font-family: 'Source Sans Pro', Helvetica, sans-serif; font-size: 16px; line-height: 13.7142858505249px;" data-mce-style="color: #141412; font-family: 'Source Sans Pro', Helvetica, sans-serif; font-size: 16px; line-height: 13.7142858505249px;">The commands to enable the custom repository and install the required packages on a FreeBSD host appear below. Note that these are <em style="box-sizing: border-box; color: #141412; font-family: 'Source Sans Pro', Helvetica, sans-serif; font-size: 16px; line-height: 13.7142858505249px;" data-mce-style="box-sizing: border-box; color: #141412; font-family: 'Source Sans Pro', Helvetica, sans-serif; font-size: 16px; line-height: 13.7142858505249px;">Bourne<span style="color: #141412; font-family: 'Source Sans Pro', Helvetica, sans-serif; font-size: 16px; line-height: 13.7142858505249px;" data-mce-style="color: #141412; font-family: 'Source Sans Pro', Helvetica, sans-serif; font-size: 16px; line-height: 13.7142858505249px;"> shell commands; this script will not work in the FreeBSD default shell <code style="box-sizing: border-box; font-family: monospace, serif; font-size: 14px; color: #141412;" data-mce-style="box-sizing: border-box; font-family: monospace, serif; font-size: 14px; color: #141412;">csh</code><span style="color: #141412; font-family: 'Source Sans Pro', Helvetica, sans-serif; font-size: 16px; line-height: 13.7142858505249px;" data-mce-style="color: #141412; font-family: 'Source Sans Pro', Helvetica, sans-serif; font-size: 16px; line-height: 13.7142858505249px;">." After having baked ONE SET OF DEFAULTS into a custom package (to make our lives easier), you leave readers to mess with ANOTHER SET OF DEFAULTS, i.e. to change FreeBSD's shells? Aren't there some discrepancies? It may be simple / useful / interesting to change shells, but why not make a self-sufficient article? Please update your article to provide a full picture of what a user should do to install all necessary software, and also which parts should be installed from your repo, and which parts should be installed from ports (+ the correct order). You've already done a lot of work, but with this refinement your help will be even more valuable. I'm not asking for myself personally (I've already accomplished all necessary tasks) - just IMHO everyone writing instructions, tutorials and HowTos for the *nix world should stick to the rule: articles should be self-sufficient. I.e. if they rely on techniques not detailed in them, they should at least include links to other WORKING articles to ensure that a reader will be able to COMPLETE a task. Thanks for your contribution, Fraser. Thu, 23 Oct 2014 09:58:33 +0200 от Lukas Slebodnik <lslebodn@redhat.com>: <blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;"> <div id=""> <div class="js-helper js-readmsg-msg"> <style type="text/css"></style> <div> <base target="_self" href="https://e.mail.ru/"> <div id="style_14140513880000000690_BODY">On (23/10/14 11:27), Outback Dingo wrote: >On Thu, Oct 23, 2014 at 11:20 AM, Fraser Tweedale <<a href="/compose?To=ftweedal@redhat.com">ftweedal@redhat.com</a>> >wrote: > >> On Wed, Oct 22, 2014 at 03:23:56PM +0200, Lukas Slebodnik wrote: >> > On (22/10/14 17:10), Fraser Tweedale wrote: >> > >Further to my earlier email, I have written a blog post about all >> > >these matters, with a particular focus on the custom package repo. >> > > >> > >I will update it tomorrow with a bit more about the package >> > >"flavours" topic. For now, all the details for enabling and using >> > >the custom repo are in the post. Check it out and let me know if >> > >you spot any issues. >> > > >> > > >> <a href="http://blog-ftweedal.rhcloud.com/2014/10/configuring-freebsd-as-a-freeipa-client/" target="_blank">http://blog-ftweedal.rhcloud.com/2014/10/configuring-freebsd-as-a-freeipa-client/</a> >> > > >> > The disadvantage of this approach is that users need to rely on updating >> > of non standard repo. <a href="https://frase.id.au/pkg/${ABI}_FreeIPA" target="_blank">https://frase.id.au/pkg/${ABI}_FreeIPA</a> >> > >> > In my opinion, it's better to write howto (script) which will configure >> all >> > necessary ports/files and portmaster will take care of updating ports. >> > <a href="https://www.freebsd.org/doc/handbook/ports-using.html#portmaster" target="_blank">https://www.freebsd.org/doc/handbook/ports-using.html#portmaster</a> >> > >> > LS >> >> Each has its advantages and disadvantages; people can choose what >> works for them. Hopefully - not too far in the future - people >> won't have to choose, when binary package "flavours" are >> implemented. When that happens, a small effort will be needed to >> define the FreeIPA flavour and ensure it gets included in the >> official package repos. >> Fraser you missed one main point of this thread. The most problematic was to *configure* all files and not install sssd. I don't want to say that installing is super easy, but configuration is much more complicated. > >Actually I would be inclined to assist with a ports build, so it could be >done correctly from the ports tree >and work towards having it adopted into mainline. > +1 LS -- Manage your subscription for the Freeipa-users mailing list: <a href="https://www.redhat.com/mailman/listinfo/freeipa-users" target="_blank">https://www.redhat.com/mailman/listinfo/freeipa-users</a> Go To <a href="http://freeipa.org" target="_blank">http://freeipa.org</a> for more info on the project </div> <base target="_self" href="https://e.mail.ru/"> </div> </div> </div> </blockquote> </BODY></HTML>