Hi Ernesto, I don't have access to the test environment right now. However, I do remember following this sequence all the time. Was not mounting sys religiously though.
Once more thing - It is booting fine for me using nfs instead of nbd. With nbd it just doesn't boot. Since you are using ltsp-update-image, you are obviously getting success with nbd. I had to "downgrade" to nfs as per http://www.nabble.com/random-clients-stall-out-at-Error:-Ioctl-1.1a-failed:-Bad-file-descriptor-td20858391.html But with nfs also there is still the issue of gdm not starting even with the startgdm.sh script. A blue screen of horror ;-) pops up stating that there is something wrong with gdm and the /var/log/gdm/:0.log says this - # more /var/log/gdm/:0.log md5sum: /etc/X11/xorg.conf: No such file or directory 10784 10758 xinit /etc/gdm/failsafeXinit /etc/X11/xorg.conf.failsafe with-gdm -- /usr/bin/X :0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt9 -br -once -config /etc/X11/xorg.conf.fails afe -logfile /var/log/Xorg.failsafe.log _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running xinit: Server error. 10784 10758 Once thing I noticed - There was a difference in uid of gdm in the base system and the chroot. At first instance the system was complaining of /var/lib/gdm not belonging to uid 107 (gdm) or gid 117 (gdm) but after a reboot the blue whiptail screen appears. For gdm, I decided to remove and install gdm and have kick-started the process before leaving the test env and shall post the results tomorrow both for nfs and nbd. Regards, SB Ernesto Freyre G. wrote: > My config sometimes failed showing the BusyBox shell. Later I found that > every change I made into the chroot jail (/opt/ltsp/fati386) must be > preceded by > > when entering > # mount /proc -t proc /proc > # mount /sys -t sysfs /sys > > > # operations > # apt-get install ... > # <configuration commands> > > > to close > # update-initramfs -u > # umount /sys > # umount /proc > # exit > > outside the chroot > # ltsp-update-image ... > # ltsp-update-kernels > > Check with this procedure and let me know if it works. > > Grettings > > Ernesto > > > > > -- Shrenik Bhura IntelliAnt: Consulting and Development of Free / Open Source Software ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _____________________________________________________________________ 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
