I guess what I mean is that if I install the default ltsp-standalone-server the thin-clients boot into /opt/ltsp/i386. When I opened a terminal in a client I was in the chroot. When I made opt/ltsp/i386 a chroot for fat-clients and then try to do LTSP_FATCLIENT=False then those computers now boot into the server root. If I open a terminal on a thin client I have access to the server. I thought the purpose of a chroot enviroment was to seperate the clients from the server. If I am wrong please correct me. If this is installed in a school and a student wants to mess with the chroot it can be rebuild. But if the thin-clients are booting into the server root then they have the potential to crash the server.
If thin clients are not suppose to have their own chroot then why does the default setup give them one? On my previous install which was only thin-clients they booted into the chroot. So it only makes since that a combined fat/thin enviroment they should do the same. I do get that the thin-clients use the server root, but they should be at least booting into a chroot. Please let me know what I am missing. I might just be misinformed. On Sun, Aug 8, 2010 at 10:20 PM, Alkis Georgopoulos < 615...@bugs.launchpad.net> wrote: > (I meant it's specific to Ubuntu). > > Thin clients boot from a server chroot. > Then, when the user logs in, they connect to the server, and all the > session is on the server. > So they use the server root, because all the user processes run on the > server. If you don't want them to use the server root, then they're fat > clients. > > If you want them to boot from another chroot and not use the server > root, then that other chroot should also be a fat chroot. It should have > a desktop environment installed. You can't boot a thin client from a > thin chroot and not use the server root. Then it isn't a thin client, > and it should have plenty of ram to load a normal environment, and that > chroot should have a desktop environment (i.e. be a fat chroot) etc. > > Or did I misunderstand what you're trying to do? > > ** Changed in: ltsp (Ubuntu) > Status: New => Incomplete > > -- > LTSP_FATCLIENT=False sends thin-clients into root directory > https://bugs.launchpad.net/bugs/615216 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Linux Terminal Server Project: Invalid > Status in “ltsp” package in Ubuntu: Incomplete > > Bug description: > If I change the /var/lib/tftpboot/ltsp/i386/lts.conf to include > LTSP_FATCLIENT=False under a specific MAC address it enables me to run some > of my slower computers as thin clients. > > The problem is that those thin clients don't seem to be running in the > /opt/ltsp/i386 chroot that was designed for the fat-clients, but instead > seem to run in the normal root directory. > > For example if I 'apt-get install cheese' in the /opt/ltsp/i386 chroot it > will install only for the fat-clients, but not the thin-clients. To install > cheese for the thin clients I need to 'apt-get install cheese' from the root > directory. > > I don't want my thin-clients running in the normal root so I tried creating > a new thin-client chroot and put it at /opt/ltsp/i386thin/i386 and moved the > original fat-client chroot to /opt/ltsp/i386fat/i386. I removed gimp in > /opt/ltsp/i386thin/i386 with apt-get remove gimp for test purposes. Did > ltsp-update-kernels & ltsp-update-image -b /opt/ltsp...ect. > > Nothing changed. The thin-clients still boot into the root directory. I > need a way to tell the system that when LTSP_FATCLIENT=False is in the > lts.conf that it needs to boot from /opt/ltsp/i386thin/i386. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ltsp/+bug/615216/+subscribe > -- LTSP_FATCLIENT=False sends thin-clients into root directory https://bugs.launchpad.net/bugs/615216 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
