Re: [Ltsp-discuss] Announcing LTSP 19.08

[Alkis G. <al...@gm...>]

Btw, if someone doesn't want uefi support nor ipxe menus etc,
he could just use something like:

kernel /ltsp/x86_64/vmlinuz initrd=initrd.img initrd=ltsp.img 
root=/dev/nfs nfsroot=192.168.67.1:/srv/ltsp 
ltsp.image=images.x86_64.img loop.max_part=9
initrd /ltsp/x86_64/initrd.img
initrd /ltsp/ltsp.img

(this is 3 lines, in case email split the kernel line into more)

The kernel/initrd.img file names are always the same, they don't depend 
on version or distribution anymore.


On 8/21/19 9:19 AM, Alkis Georgopoulos wrote:
> Hi Vinícius;
> also all the other LTSP users that don't use dnsmasq should read this.
> 
> The new LTSP supports UEFI and relies on the awesome iPXE for menus and 
> kernel cmdline parameters. This means that there are at least THREE 
> different "filenames" involved now, it's not as simple as "pxelinux.0".
> 
> Please read the `ltsp dnsmasq` template file from line 35 and below:
> https://github.com/ltsp/ltsp/blob/master/ltsp/server/dnsmasq/ltsp-dnsmasq.conf#L35 
> 
> 
> This first paragraph checks "if client is UEFI... else...".
> So people using isc-dhcp or pfsense or windows, will need to find the 
> equivalent syntax for those "ifs".
> 
> In the next paragraph (line 45+), the boot filenames are assigned based 
> on the previous "ifs".
> undionly.kpxe gives ipxe support to BIOS/PXE clients
> snponly.efi gives ipxe support to UEFI/PXE clients
> ltsp.ipxe is our menu, sent to ipxe clients
> 
> So one solution would be to "translate" that dnsmasq.conf file into 
> isc-dhcp or windows dhcp server settings. When someone does that, please 
> edit the wiki or file an issue or at least send it here to the mailing 
> list so that we record it for others.
> 
> Another EASIER solution though, is to configure your external DHCP 
> server to send IPs etc but NOT the boot filename,
> and just run `ltsp dnsmasq` to configure it in proxyDHCP mode,
> so that the LTSP server will just send those appropriate filenames (but 
> not IP addresses).
> 
> If someone wants to do the previous harder solution and needs more 
> specific help, he should mention the exact dhcp server/setup he has.
> 
> Cheers,
> Alkis
> 
> 
> On 8/21/19 4:51 AM, Vinícius Ferrão via Ltsp-discuss wrote:
>> Alkis, first of all thanks for the amazing job that you are doing with 
>> LTSP.
>>
>> I have a question regarding the DHCP configuration. I don’t use 
>> dnsmasq at all in my environment because I have a full featured DHCP 
>> server running on another machine. So in the new LTSP release what is 
>> the needed steps to use an standalone DHCP server?
>>
>> Thanks,
>>
>> Sent from my iPhone
>>
>>> On 20 Aug 2019, at 03:26, Alkis Georgopoulos <al...@gm...> wrote:
>>>
>>> Hi Rolf,
>>>
>>> in about a month, I think the new LTSP will be more stable than the 
>>> old one, and it will surely be more actively developed and maintained.
>>> E.g. I'm hearing about LTSP5 issues with Buster Gnome; I don't see 
>>> any in the new LTSP.
>>> So for new installations people might want to use the new LTSP even now.
>>>
>>> Both LTSP versions can be installed in parallel. There is no 
>>> automatic migration or update from LTSP 5 to the new version.
>>> To install the new LTSP, one would follow:
>>> https://github.com/ltsp/ltsp/wiki/installation
>>>
>>> To select which LTSP version the clients will use, do the following.
>>> To activate LTSP5:
>>> rm -f /etc/dnsmasq.d/ltsp-dnsmasq.conf
>>> ltsp-config --overwrite dnsmasq
>>>
>>> To activate the new LTSP:
>>> rm -f /etc/dnsmasq.d/ltsp-server-dnsmasq.conf
>>> ltsp --overwrite dnsmasq
>>>
>>> If after some time people see that they don't need the old LTSP, they 
>>> can remove it using something like:
>>> apt purge --auto-remove ldm ldm-server ldm-ubuntu-theme \
>>> ltsp-client ltsp-client-core ltsp-server ltsp-server-standalone \
>>> ltspfs ltspfsd ltspfsd-core
>>>
>>> Note that each version uses different directories and lts.conf / 
>>> ltsp.conf configuration files; so one would have to rewrite ltsp.conf 
>>> from scratch while looking at the supported ltsp.conf options from 
>>> the man page, and maybe `cp -a` his chroots, if he's not using 
>>> chrootless.
>>>
>>> Regarding ltsp.org, I try to minimize the effort I put in the 
>>> projects I maintain, and caring about a domain is effort (and a tiny 
>>> amount of money, especially if one maintains many projects). I could 
>>> be convinced to map ltsp.org to ltsp.github.io though, if the 
>>> original LTSP authors or the LTSP users feel it's better.
>>>
>>> Note that the discussion for the new LTSP continues in github:
>>> https://github.com/ltsp/community/issues/4
>>>
>>> I've already sent updated announcements there about new PPA builds 
>>> that add support for xorg.conf options, local swap, passwordless 
>>> logins etc.
>>>
>>> Regards,
>>> Alkis
>>>
>>>
>>>> On 8/20/19 9:37 AM, Rolf-Werner Eilert wrote:
>>>> Congratulations, Alkis!
>>>> Sounds really interesting. When it's ready, will it update 
>>>> automatically or will an LTSP5 rest to be as it is?
>>>> Another question: Why didn't you connect the new site to the old 
>>>> ltsp.org site? (I know, we had this discussion, just forgot the 
>>>> reason why...)
>>>> Regards
>>>> Rolf
>>>>> Am 18.08.19 um 20:22 schrieb Alkis Georgopoulos:
>>>>> LTSP 19.08 has been released! Read the full announcement with all 
>>>>> the features and changes, and join the discussion here:
>>>>> https://github.com/ltsp/community/issues/4
>>>>>
>>>>> In short, LTSP has been redesigned and rewritten from scratch as 
>>>>> part of a GSoC 2019 project. Many thanks to everyone involved for 
>>>>> this opportunity to radically improve LTSP!
>>>>> https://summerofcode.withgoogle.com/projects/#4558570069164032
>>>>>
>>>>> LTSP 19.08 is an alpha release that can be installed in parallel 
>>>>> with the older LTSP5 version. The plan is to reach stable by the 
>>>>> end of September, so I'll actively try to fix any issues you report:
>>>>> https://github.com/ltsp/ltsp/wiki/installation
>>>>>
>>>>> Please also note that all the existing LTSP sites and mailing lists 
>>>>> will now only be used for the older LTSP5 and receive minimal 
>>>>> maintenance. For the new sites and discussion methods see the new 
>>>>> main site:
>>>>> https://ltsp.github.io
>>>>>
>>>>> I.e. please do not reply to this email unless you don't like 
>>>>> github; otherwise, all discussions for the new LTSP should happen 
>>>>> on the github ltsp community site:
>>>>> https://github.com/ltsp/community/issues
>>>>> Feel free to open new issues and ask whatever you want there; the 
>>>>> plan is to use it instead of a mailing list, so we want to be 
>>>>> relaxed, not formal.
>>>>> I will continue cross-posting announcements and replying to the 
>>>>> sourceforge mailing lists for a while though, until LTSP users get 
>>>>> familiarized with the new methods.
>>>>>
>>>>> Hope you like the new LTSP,
>>>>> Alkis Georgopoulos
>>>>>
>>>
>>>