On emerging (or re-emerging) ltsp-4.1-r1 several key directories and a symlink are not created in the /opt/ltsp-4.1/i386 directory tree. The problem shows up when a thin client is booting as: --[snip]-- Doing the pivot_root pivot_root: pivot_root: No such file or directory Mounting the devfs filesystem mount: Mounting /devfs on /dev failed: device or resource busy Running /sbin/init exec: /sbin/init: no such file or directory --[snip]-- (Followed by a kernel panic message & total lockup) The missing/required directories on the server are as follows: /opt/ltsp-4.1/i386/oldroot /opt/ltsp-4.1/i386/proc /opt/ltsp-4.1/i386/dev Also, a symlink is missing which causes the following error on a think client atempting to start X: fatal server error: cannot open log file /var/log/Xorg.0.log The missing/required symlink on the server is: /opt/ltsp-4.1/i386/var -> /tmp/var Reproducible: Always Steps to Reproduce: 1. emerge ltsp 2. 3. Not sure if this is relevant, but here is the emerge info output on this (4) processor system: # emerge info Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.5-r0, 2.6.11-gentoo-r9 i686) ================================================================= System uname: 2.6.11-gentoo-r9 i686 Intel(R) Xeon(TM) CPU 2.80GHz Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer" DISTDIR="/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://www.gtlib.cc.gatech.edu/pub/gentoo" MAKEOPTS="-j8" PKGDIR="/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X apm avi berkdb bitmap-fonts crypt cups curl eds emboss encode esd fam font-server foomaticdb fortran gdbm gif gpm gstreamer gtk gtk2 imlib ipv6 java jpeg kde ldap libg++ libwww mad mikmod motif mozilla mp3 mpeg mysql ncurses nls ogg oggvorbis opengl oss pam pdflibperl png postgres ppds python qt quicktime readline samba sdl spell ssl tcpd tiff truetype truetype-fonts type1-fonts usb vorbis xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
unmerge and remerge it, it's a portage bug
Hi Heinrich, thanks for your quick response. ...But it is hard to unmerge, re-emerge and then possibly have to completely reconfigure a piece of software that is being used by many clients in a production environment so that can't really be my only option can it? Will I be forced to mask ltsp from any future upgrades with /etc/portage/package.mask to prevent ltsp from getting whacked when a new package is available? Also, this problem exists on an initial "emerge ltsp" not only when the package is re-emerged. Can you point me to the portage bug so I might understand more clearly what is happening? Thanks again for the quick response. Bill
Only revision bumps (-r updates) are affected, new versions, like 4.2 not. Furthermore your config *should* not be touched.
I also experienced the problem after re-emerging net-misc/ltsp-4.1.1 and would like to know the portage bug report number, I cannot seem to find it anywhere...