Desktop choice/performance

Fri Sep 28 16:35:55 UTC 2012

Hi Alkis,

I can't wait to make this work today after school!

For, "answer to wiki initiative, I think you mean having "page
stewards" (bottom
of ltsp-pnp page <https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp>)?
It is a controversial approach to wikis, but then maybe this kind of info
shouldn't be on a wiki but on some authoritative document site with page
stewards taking responsibility for the page as you have for this ltsp-pnp
page.  To build on this idea, how about having a page listing page/steward
information for the whole wiki, or better for different communities on the
wiki (such as community/UbuntuLTSP/)?  This recognizes the person and makes
public their commitment--sort of like the commitment people make to be on
the Ubuntu or Edubuntu teams?  Of course, if I misunderstood your, "answer
to wiki initiative" statement, well, I'll quietly step down from soap box...

Thanks,
David

On Thu, Sep 27, 2012 at 10:11 PM, Alkis Georgopoulos <alkisg at gmail.com>wrote:

> Στις 28/09/2012 04:09 πμ, ο/η David Groos έγραψε:
> >     apt-get --yes install dnsmasq ltsp-server-standalone ltsp-client
> ldm-ubuntu-theme
> >
> > Question: it asks about config of nbd--not sure what all it means.  What
> > are the ramifications of yes disconnect all NBD devices on "stop" or
> > no?  While it says traditional is Yes, since No was highlighted
> > (thinking it may be recommended--sounds safer? I... OK I chose No.
>
> Whatever you select there doesn't make any difference for LTSP.
> It's for clients declared in /etc/nbd-client, and LTSP doesn't use that
> file.
>
> > (still as
> >   *  ltsp-config dnsmasq
> >
> > worked... then I quickly unplugged the cable because it said,
> > "*Restarting DNS forwarder and DHCP server dnsmasq".  Three years ago I
> > took down our school network with a port broadcasting on the building
> > (external) network--I can't afford to have a bad rep with the tech dept
> > here...
>
> I'm not sure what you mean there or how it was technically achieved.
> But when running `ltsp-config dnsmasq`, you should have had already
> configured your server IP addresses, so that it would automatically
> create a proper /etc/dnsmasq.d/ltsp-server-dnsmasq.conf for you:
>
> "It's recommended that you setup your network first. A static IP is
> suggested but not required for single NIC setups. If you're using a dual
> NIC setup, configure the internal NIC to 192.168.67.1. "
>
>  To investigate I went to /etc/network/interfaces and only saw
> >
> > auto lo
> > iface lo inet loopback
> >
> > Huh?
> > Stymied...
> > I'd appreciate it if you would add that part about doing a 2 nic setup :D
> > Also, what about that "Disconnect all NBD devices..." choice I made?
> > Might be good to explain a bit of that on the pnp page.
> >
>
>
> The "how to assign a static IP address" part isn't ltsp-pnp specific, so
> it doesn't belong in that wiki page.
> You're correct though in that this information is missing from the
> https://help.ubuntu.com/community/UbuntuLTSP wiki (although it isn't
> strictly LTSP-specific either).
>
> So... let's start an "an answer for a wiki page" initiative: I'll be
> answering some questions like this one in the mailing list, and people
> that receive the answers should then create nice wiki pages for others
> to get helped as well! :)
>
> So if you do write an
> https://help.ubuntu.com/community/UbuntuLTSP/StaticIP wiki page about
> it, I'll put a link to it from the ltsp-pnp wiki page.
>
> There are 2 methods to configure a static IP for your server. One, with
> network manager, and second, from /etc/network/interfaces.
> For "headless" servers the second method is preferred, but for schools
> where the teachers are working on the server I suggest going with the
> first one, so that the teachers can easily see the network properties
> from the gnome applet (connection speed, up/down status...)
>
> Network manager method:
> Read this:
>
> http://www.liberiangeek.net/2010/03/how-to-configure-a-static-ip-address-in-ubuntu/
> Copy or create some similar pictures for the UbuntuLTSP wiki page.
> Some additional remarks:
>  * The "[v] Make connection available for all users" setting should be
> checked, otherwise the connection only starts after the teacher logs in
> on the server.
>  * The
> http://www.liberiangeek.net/wp-content/uploads/2010/09/static_ip_mav_23.png
> picture applies for single NIC installations.
>  * For dual NIC installations, the internal NIC should have no DNS
> server entries, and for gateway it should have 0.0.0.0. Again the "[v]
> Make connection available for all users" setting should be checked.
>
>
> /etc/network/interfaces method:
> Don't read what's written in the
>
> www.liberiangeek.net/2010/03/how-to-configure-a-static-ip-address-in-ubuntu/
> page, don't disable network manager like it suggests etc.
>
> For single NIC cases, put something like this in /etc/network/interfaces:
> iface eth0 inet static
>     address 192.168.3.3
>     netmask 255.255.255.0
>     gateway 192.168.3.1
>     dns-search example.com
>     dns-nameservers 192.168.3.45 192.168.8.10
>
>
> For dual nic cases, the internal NIC entry should be like this:
> iface eth1 inet static
>     address 192.168.67.1
>     netmask 255.255.255.0
>
>
> That's all, if you configure your network _before_ following the
> ltsp-pnp installation steps, then `ltsp-config dnsmasq` will create an
> appropriate /etc/dnsmasq.d/ltsp-server-dnsmasq.conf for you.
> If you do it afterwards, just re-run:
> ltsp-config dnsmasq --overwrite
>
> Warning: the generated /etc/dnsmasq.d/ltsp-server-dnsmasq.conf has
> proxy-dhcp mode enabled for the external NIC. So, clients in your
> "external" network will be able to be netbooted as ltsp clients.
> If you don't want that, you should remove the respective
> dhcp-range=192.168.3.0,proxy
> line from that file.
>
>
> Cheers, let's see if the "an answer for a wiki page" initiative can work!
> :)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/edubuntu-users/attachments/20120928/76032465/attachment.html>