Zitat von Alkis Georgopoulos <alk...@gmail.com>:
> On 22/02/2017 10:37 πμ, Andreas-Christoph Bernstein wrote: >> Interesting. That is new, right? I thought ltsp-pnp doesn't create a >> chroot. That's why we are still using ltsp-server-standalone on our >> ubuntu server. >> >> So nowadays i would start with ltsp-pnp? Is ltsp-server-standalone >> obsolete (on ubuntu)? > > > ltsp-pnp has been around for more than 5 years and has been used in > thousands of installations. If it suits your needs, you can surely use > it. ltsp-build-client might be deprecated in ltsp6 in favor of other > methods to build chroots, but for ltsp5 it's of course still supported. > > The ltsp-pnp wiki page does say that you need to install the > ltsp-server-standalone package, so you have some misunderstanding there, > let's try to clear it up. > > ltsp-server: an LTSP server where we don't want DHCPD (and possibly > TFTPD) because we have those servers elsewhere in our LAN. > ltsp-server-standalone: an LTSP server which will have DHCPD and TFTPD. > > Those are true for both classic ltsp and for ltsp-pnp. > The difference is that: > The ltsp-pnp wiki page suggests that you install ltsp-server-standalone > with dnsmasq as the dhcpd and tftpd server. > While in the classic ltsp, ltsp-server-standalone installed > isc-dhcp-server and tftpd-hpa. > > The reason that ltsp-pnp prefers dnsmasq instead of those 2 others, is > because it can also function as "proxyDHCP", while isc-dhcp-server > cannot do that. > ProxyDHCP means: "I have a router that does DHCP in my network, so the > LTSP server should only send the boot filename and root path, and let > the router manage the IP leases". > > Since the "router is DHCPD" scenario is very very common, that's why > ltsp-pnp preferred dnsmasq and ProxyDHCP. > And it became the default in recent classic LTSP too, so new LTSP > installations (2017+) will get dnsmasq by default instead of the other 2 > servers. > That means that the ltsp-pnp differences from the classic ltsp are now > really really small; just running `ltsp-update-image -c /` instead of > running `ltsp-build-client` for the default image. > > Btw, `ltsp-config dnsmasq` also sets up a classic DHCPD in the > 192.168.67.x range, so if you want the old "dual nic" setup, you can > just set the second nic to 192.168.67.1 and you're ready to go. > > > > To sum up: ltsp-server-standalone used to prefer to depend on > isc-dhcp-server and tftpd-hpa, while now it prefers to depends on dnsmasq. > If someone doesn't want dnsmasq, he can just install the 2 other ones. > Thank you Alkis for your detailed response. That clears things up. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
