Which is why I would _avoid_ all setup and implementation-specifics,
and just focus on the logic.

E.g., the fact that SWAT doesn't write out configuration lines for
default settings.  That's the one that gets sysadmins the most,
especially since defaults can change from revision to revision.

-- bjs



On Wed, Jul 8, 2015 at 2:02 PM, Alessandro Selli
<[email protected]> wrote:
> On 08/07/2015 at 13:11, Martin Møller Skarbiniks Pedersen wrote:
>
> [...]
>
>>   Also I am missing the great tools swat for configuration of samba in
>> objective 209.1
>
>   I read that SWAT was removed as of version 4.1:
> https://wiki.samba.org/index.php/Samba_4.1_Features_added/changed
>
>  REMOVED COMPONENTS
>
> The Samba Web Administration Tool (SWAT) has been removed. Details why SWAT
> has been removed can be found on the samba-technical mailing list:
>
> https://lists.samba.org/archive/samba-technical/2013-February/090572.html
>
>
>   Looks like it's now a separate project from Samba, led by Ricardo Velhote
> who reimplemented it in Python and called it SWAT2:
>
> https://wiki.samba.org/index.php/SWAT
>
> Samba 3 includes a web tool for configuring Samba named SWAT. This is a
> simple CGI program.
>
> Samba 4 has a completely rewritten, more user-friendly SWAT implementation
> (SWAT2) that is not included in Samba but developed separately.
>
> https://wiki.samba.org/index.php/SWAT2
>
>
>   I don't know if SWAT2 should be mentioned in the objectives, maybe just as
> a "good to know", optional item.
>
>
>
> --
> Alessandro Selli
> Tel: 340.839.73.05
> VOIP: sip:[email protected]
> Chiave firma PGP/GPG signing key: B7FD89FD
> Chiave crittografia PGP/GPG encrypting key: A6023DD5
> _______________________________________________
> lpi-examdev mailing list
> [email protected]
> http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev



-- 
-- 
Bryan J Smith - http://www.linkedin.com/in/bjsmith
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev

Reply via email to