The issue:
A PXE client boots into a Kubuntu (Fiesty) 7.04 server running LTSP 5. The
client's root file system is exactly the same as the server's root file
system.
The question:
Is this by design, a bug or a configuration issue? What can I do to fix it?
I haven't seen this issue documented, but there have been a couple of other
people who have had the same behavior.
More details:
The PXE client cannot login using chrooted adduser accounts under
/opt/ltsp/$ARCH; however, it CAN login using the server's local accounts
(except root). The login screen is what you'd expect from a ubuntu-desktop
install, but while logging in, it changes over to a kubuntu-desktop
environment and appears to login using the root file system of the server,
not /opt/ltsp/$ARCH.
Setup details:
- Installed Kubuntu on server with kubuntu-desktop
- Installed openssh-server and ltsp-server-standalone using aptitude
- Configured dhcpd.conf file to boot pxe clients in my network
environment
- Run ltsp-build-client, which appears to have created and filled the
/opt/ltsp/i386 folder appropriately
- To create an account for client, on the server, I did chroot
/opt/ltsp/i386 followed by adduser test.
- PXE client boots up with a Kubuntu splash screen into the login
screen, but I cannot login using "test".
Troubleshooting steps taken:
- On the client, tried to login using an account local to the server -
it worked
- On the server, tried to chroot /opt/ltsp/i386 THEN aptitude install
ubuntu-desktop
- On the server, tried to chroot /opt/ltsp/i386 THEN aptitude remove
kubuntu-desktop THEN aptitude install ubuntu-desktop (tried with ubuntu,
edubuntu, kubuntu and xubuntu with the same results)
- Tried booting client from a live Edubuntu disc THEN from the client
apt-get install ltsp-server THEN mount
server.ip.address:/opt/ltsp/opt/ltsp THEN ltsp-build-client THEN
ltsp-update-kernels (on server) THEN
ltsp-update-sshkeys (on server). The client at this point will boot up with
a Ubuntu splash screen and show an Edubuntu login screen. During login, it
shows the Kubuntu desktop environment and boots into the server's local
Kubuntu desktop environment
- Tried some other things, but I haven't made progress.
What I think:
It was my belief that the client should use the server's /opt/ltsp/$ARCH as
$ROOT, not the server's root file system. If this is by design, this seems
like a huge issue with security and practicality. Any ideas?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_____________________________________________________________________
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
