I recently started using the ltsp-server package from the Ubuntu
repository. On several occasions, I made mistakes while customizing
because I didn't realize that I was (or was not) working inside the LTSP
chroot. I suggest the following change to the ltsp-chroot command:
--- ltsp-choot.orig 2012-09-07 15:14:22.408467764 -0400
+++ ltsp-choot 2012-09-07 15:14:07.908472651 -0400
@@ -133,4 +133,4 @@
trap "post_chroot" 0 HUP INT QUIT KILL SEGV PIPE TERM
pre_chroot
-eval LTSP_HANDLE_DAEMONS=false chroot "$ROOT" $COMMAND
+eval LTSP_HANDLE_DAEMONS=false debian_chroot="remaster" chroot "$ROOT"
$COMMAND
This causes the shell instance running in the chroot to have a visibly
different prompt, making it easier to distinguish when one is running in
the chroot or not. Replace "remaster" with something more appropriate
if you like.
-Chad
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_____________________________________________________________________
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
