Hi
Thanks, vagrant. In short: I have been able to log in from my client machine.
Manually making the changes you recommended to my then existing setup . . .
> Your dnsmasq configuration didn't appear to include a setting for root-path:
>
> # The rootpath option is used by both NFS and NBD.
> dhcp-option=17,/opt/ltsp/i386
and
> You also may want to specify in /opt/ltsp/i386/etc/ltsp/update-kernels.conf:
>
> # Commandline used with NFS root
> CMDLINE_NFS="root=/dev/nfs ip=dhcp boot=nfs nfsroot=/opt/ltsp/i386"
> IPAPPEND=3
>
>
> And then run:
>
> ltsp-chroot /usr/share/ltsp/update-kernels
> ltsp-update-kernels
>
> You could also try the above with the corresponding CMDLINE_NBD= with nbdroot;
didn't make any perceptible difference.
So I started over from scratch.
First, remove everything (I think),
# apt-get remove --purge ltsp-server dnsmasq
# apt-get --purge autoremove
# rm -r /etc/dnsmasq.d
# rm -rf /opt/ltsp /var/lib/tftpboot/ltsp /srv/tftp/ltsp
Then back to the start:
Step 1:
# apt-get install ltsp-server dnsmasq
Whereupon I could run
# ltsp-info
and get back
server information:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux testing (jessie)
Release: testing
Codename: jessie
server packages:
un ldm-server <none>
un ltsp-client-core <none>
un ltsp-docs <none>
ii ltsp-server 5.5.1-1
un ltsp-utils <none>
un ltspfs <none>
find: `/opt/ltsp': No such file or directory
Step 2:
Then I "built a client" so to speak
# ltsp-build-client --arch i386
The lengthy response to that command ended with
WARNING: no entry for /opt/ltsp in /etc/exports,
you may want to add the following line to /etc/exports:
/opt/ltsp *(ro,no_root_squash,async,no_subtree_check)
and then run the command:
invoke-rc.d nfs-kernel-server reload
info: LTSP client installation completed successfully
Step 3:
Per those instructions, I then added
/opt/ltsp *(ro,no_root_squash,async,no_subtree_check)
to the bottom of the file at /etc/exports
and ran
# invoke-rc.d nfs-kernel-server reload
and, for good measure,
# service nfs-kernel-server restart
Step 4:
Then I followed your suggestion and ran
# ltsp-config dnsmasq
Which both created a file at /etc/dnsmasq.d/ltsp-server-dnsmasq.conf and also
restarted the "DNS forwarder and DHCP server: dnsmasq."
Step 5:
Another of your suggestions. I changed the file at
/opt/ltsp/i386/etc/ltsp/update-kernels.conf where it had
# Commandline used with NFS root
CMDLINE_NFS="root=/dev/nfs ip=dhcp boot=nfs"
to have instead
# Commandline used with NFS root
CMDLINE_NFS="root=/dev/nfs ip=dhcp boot=nfs nfsroot=/opt/ltsp/i386"
IPAPPEND=3
and then ran
# ltsp-chroot /usr/share/ltsp/update-kernels
# ltsp-update-kernels
Step 6:
When I then turned on the client machine, instead of the "connection refused"
messages, I got graphical login prompt.
Living well.
Thanks again.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_____________________________________________________________________
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
