<div>Martin,</div>
<div>On one hand, </div>
<div>Some stuff like Network Configuration, *could* be hacked into anaconda (we'd have to push, for instance, 3G modem config, or wireless card, or pppoe into anaconda), which is a major pain, but It might get upstream. That, at least, will require some human interaction.</div>
<div> </div>
<div>About setting it up with Moodle... I could try to code a moodle admin module, it should not be that hard. The moodle admin module could set up:</div>
<div> </div>
<div>- Squid ON/OFF + maybe a squid blacklist (so some schools can blacklist potentially dangerous sites).</div>
<div>- Every future configurable thing we can think off.</div>
<div> </div>
<div>Anaconda already asks for the Hostname, we could hack it to only ask for the domain name, and always add schoolserver. in front of it, and then we could set the kickstart %post to run domain_config.</div>
<div><br><br> </div>
<div class="gmail_quote">2010/8/26 Martin Langhoff <span dir="ltr"><<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Hi SgtPepper,<br><br>I am with mixed feelings about firstboot scripts.<br><br>One one hand, some kickstart %post stuff can be done much better in a<br>
non-interactive firstboot script.<br><br>On the other hand, I would like to avoid interactive firstboot<br>scripts. Many XSs are headless, and I keep pushing deployments towards<br>headless XSs. The best rugged/embedded HW out there for XS is<br>
headless.<br><br>Are you open to a combination of<br><br> - non-interactive stuff in firstboot scripts<br><br> - interactive stuff configurable via Moodle "admin" pages, which<br>write to files monitored by incrond, which in turn invokes privileged<br>
scripts...<br><br>cheers,<br><br><br>martin<br>
<div>
<div></div>
<div class="h5"><br><br>On Thu, Aug 26, 2010 at 6:44 PM, SgtPepper <<a href="mailto:ncorrare@gmail.com">ncorrare@gmail.com</a>> wrote:<br>> To simplify the setup of the XS, I was thinking on creating some custom<br>
> firstboot modules, for some common setup operations such as:<br>><br>> 1 - Network Configuration (Internet Side: DHCP/Statip IP/PPPoE)<br>> 2- A domain_config wrapper<br>> 3- Squid (ON or OFF)<br>> 4- Show Moodle admin password<br>
> 5- Finish Screen<br>><br>> Any suggestions on any more things to add?<br>><br>><br>> PS: Once I finish the rpm, where do I push it?<br>><br></div></div>> _______________________________________________<br>
> Server-devel mailing list<br>> <a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>> <a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/listinfo/server-devel</a><br>
><br>><br><font color="#888888"><br><br><br>--<br> <a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a><br> <a href="mailto:martin@laptop.org">martin@laptop.org</a> -- School Server Architect<br>
- ask interesting questions<br> - don't get distracted with shiny stuff - working code first<br> - <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a><br>
</font></blockquote></div><br>