You could ease everything by creating 2 files: FreeIPA.conf and FreeIPA.pem, uploading them to Web and sharing links to them. FreeBSD users could the use the "fetch" command to download and use your files. Отправлено от <a href="http://r.bluemailapp.com">Blue Mail</a> <head><head><style type="text/css"> pre.blue {white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px} div, p { -ms-word-break: break-all; word-break: break-all; word-break: break-word; -webkit-hyphens: auto; -moz-hyphens: auto; -ms-hyphens: auto;hyphens: auto;} a {color: #226EF9 ;}</style></head><body style="zoom: 100%; "><div class="gmail_quote" >На 24.10.2014, в 5:36, Fraser Tweedale <<a href="mailto:ftweedal@redhat.com" target="_blank">ftweedal@redhat.com</a>> написал:п<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <pre class="blue">On Thu, Oct 23, 2014 at 02:12:47PM +0400, Орхан Касумов wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> +1. And even if talking about installation of the necessary software and not about the configuration, then why this? " The commands to enable the custom repository and install the required packages on a FreeBSD host appear below. Note that these are Bourne shell commands; this script will not work in the FreeBSD default shell csh . " 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?</blockquote> It is only for that one script (because csh heredocs are weird). There is no need whatsoever for a chsh; just that one script needs to be executed in /bin/sh. I will clarify this in the post. <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> 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 ensur! e 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 class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">On (23/10/14 11:27), Outback Dingo wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">On Thu, Oct 23, 2014 at 11:20 AM, Fraser Tweedale < <a class="linkifyplus" href="mailto:ftweedal@redhat.com" title="Linkified from plain text using Linkify Plus (0): ftweedal@redhat.com">ftweedal@redhat.com</a> > wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"> On Wed, Oct 22, 2014 at 03:23:56PM +0200, Lukas Slebodnik wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #! e9b96e; padding-left: 1ex;"> On (22/10/14 17:10), Fraser Tweedale wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">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.</blockquote> </blockquote> <a href="http://blog-ftweedal.rhcloud.com/2014/10/configuring-freebsd-as-a-freeipa-client">http://blog-ftweedal.rhcloud.com/2014/10/configuring-freebsd-as-a-freeipa-client</a>/ <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"> </blockquote> The disadvantage of this approach is that users need to rely on updating of non standard repo. <a href="https://frase.id.au/pkg">https://frase.id.au/pkg</a>/${ABI}_FreeIPA In my opinion, it's better to write howto (script) which will configure </blockquote> all <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"> necessary ports/files and portmaster will take care of updating ports. <a href="https://www.freebsd.org/doc/handbook/ports-using.html#portmaster">https://www.freebsd.org/doc/handbook/ports-using.html#portmaster</a> LS </blockquote> 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.</blockquote> </blockquote>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. <blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"> 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.</blockquote> +1 LS -- Manage your subscription for the Freeipa-users mailing list: <a href="https://www.redhat.com/mailman/listinfo/freeipa-users">https://www.redhat.com/mailman/listinfo/freeipa-users</a> Go To <a href="http://freeipa.org">http://freeipa.org</a> for more info on the project </blockquote> </lslebodn@redhat.com>: </blockquote></pre></blockquote></div></body></head>