<div dir="ltr"><div><div><div>Hi Andreas.<br></div>Thanks for your reply!<br></div>I will made a longer reply with comments asap.<br></div><div><br></div><div>I put a fist Debian Lan in production tomorrow in a non profit with 12 clients.<br>
<br></div><div>Report afterwards :)<br><br></div><div>There is still an issue on adding Windows workstations into the domain. I'm checking right now.<br><br></div><div>My pleasure for the work done. I'm glad to do it, to learn and participate in a Debian project !<br>
<br></div><div>Julien<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 28, 2013 at 9:41 AM, Andreas B. Mundt <span dir="ltr"><<a href="mailto:andi.mundt@web.de" target="_blank">andi.mundt@web.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Julien,<br>
<div class="im"><br>
On Sat, Apr 27, 2013 at 10:43:10PM +0200, Julien Lambot wrote:<br>
><br>
> I have now a working debian-lan/gosa/samba setup.<br>
> Do you have guidelines for the integration with FAI within debian-lan?<br>
> What do you expect as files or scripts in order to fit the framework?<br>
> I will do my best to provide the necessary components.<br>
<br>
</div>Hm, if it is possible, we should try to provide an extra class, say<br>
"SAMBA" or "SAMBA_SERVER" or something like that and put all stuff<br>
needed into that class. So people can add this class and end up with<br>
a working setup.<br>
<br>
In general, we should try to put all Components/Features in FAI-classes<br>
and in the best case these classes are independent, and you can pick<br>
the classes you need and build a system. (For example, split the<br>
debian-lan onto two machines, by moving some classes from the<br>
mainserver to the second machine). In reality, there are<br>
dependencies, so some classes build on other classes. However, we<br>
should try to keep the system as modularized as we can.<br>
<br>
Currently we have for the mainserver 'class/50-host-classes':<br>
<br>
## Remove GOSA class if it is not needed:<br>
MAINSERVER_A="[...] KDC_LDAP SERVER_A GOSA"<br>
<br>
I suggest to simply add a new class SAMBA at the end:<br>
<br>
## Remove GOSA and/or SAMBA class if it is not needed:<br>
MAINSERVER_A="[...] KDC_LDAP SERVER_A GOSA SAMBA"<br>
<br>
And document that the SAMBA class builts on GOSA. Does this make<br>
sense? GOSA and probably the proposed SAMBA are very specialized<br>
classes as they do specific fine-tuning of the system. However, it<br>
should be possible to just remove them and end up with a generic<br>
base-system.<br>
<br>
Feel free to suggest other ideas, I am not yet completely familiar<br>
with the needs for Windows.<br>
<div class="im"><br>
><br>
> Now, go on testing eduroaming/educlient :)<br>
><br>
<br>
</div>Wow, great! I am currently trapped in work, probably for some more<br>
weeks and I can do only some basic stuff, but the roaming client would<br>
be really, really great to have!<br>
<br>
Best regards and many thanks for your work so far,<br>
<div class="HOEnZb"><div class="h5"><br>
Andi<br>
<br>
<br>
_______________________________________________<br>
debian-lan-devel mailing list<br>
<a href="mailto:debian-lan-devel@lists.alioth.debian.org">debian-lan-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/debian-lan-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/debian-lan-devel</a><br>
</div></div></blockquote></div><br></div>