From reading this looks like a sandbox violation when doing an ebuild of pdksh. Not sure what else to do to troubleshoot the issue. Here is the tail of the emerge output >>> Install pdksh-5.2.14-r3 into /var/tmp/portage/pdksh-5.2.14-r3/image/ category app-shells strip: /var/tmp/portage/pdksh-5.2.14-r3/image/bin/ksh >>> Completed installing into /var/tmp/portage/pdksh-5.2.14-r3/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-pdksh-5.2.14-r3-11178.log" open_wr: /dev/fd/3 -------------------------------------------------------------------------------- !!! emerge aborting on /usr/portage/app-shells/pdksh/pdksh-5.2.14-r3.ebuild .
Can you do me two favours? First, make sure your world is up to date with the latest packages like pam and things. Then, make sure you run etc-update (part of gentoolkit package). If, after updating your config files you still have this problem, then please e-mail me a tar.gz of your /etc/pam.d e-me at: seemant@gentoo.org.
I just did 'emerge rsync' yesterday and did the emerge --update system and got the same results. I'll send you the pam conf when I get back to that box. Thanks.
Ah ok, you did emerge --update system. I would rather you did emerge --update world. In other words, you should make sure that your /var/cache/edb/world file is populated. The easiest way to do that is as follows: emerge gentoolkit qpkg -I -nc | sed 's/-[[:digit:]].*//g' > /var/cache/edb/world Then, edit that file and remove the system stuff, like dev-libs, sys-libs, sys-devel Then, do emerge --update --pretend world to see what you have been missing out on :P
I got this mail late so two things I did a quick and dirty creation of a world file without removing the system pieces, what I did was the qpkg command as you suggested, I combined the existing /var/cache/edb/world file with that output and ran it through 'uniq' so there were no duplicates. Then I ran the --update --pretend world on that file, and got the following. [ebuild U ] sys-kernel/linux-headers-2.4.18 to / [ebuild U ] x11-base/xfree-4.2.0-r9 to / [ebuild U ] media-libs/gdk-pixbuf-0.16.0-r8 to / [ebuild U ] gnome-base/control-center-1.4.0.5 to / [ebuild U ] x11-misc/bbpager-0.3.0-r3 to / [ebuild U ] kde-base/kdebase-3.0-r1 to / [ebuild U ] gnome-base/ORBit-0.5.14-r2 to / [ebuild U ] gnome-base/libglade-0.17-r5 to / [ebuild U ] x11-libs/gtkmm-1.2.9 to / If I run the --update --pretend world on the existing /var/cache/edb/world I get this [ebuild U ] x11-base/xfree-4.2.0-r9 to / [ebuild U ] kde-base/kdebase-3.0-r1 to / [ebuild U ] x11-misc/bbpager-0.3.0-r3 to / I'm still not seeing anything that should indicate a problem yet. pdksh doesn't depend on any of these does it? etc-update was run already, prior to this issue with pdksh, the only two files that needed updating had to do with /etc/X11 and xdm configs. I fixed them. I'm running 2.4.19-r1 SMP built with devfs among other things if that helps at all. I'm still baffled as to why it would fail trying to write to the 4th floppy device on a system with no floppies at all
no, it is more of a PAM issue from what I can tell. Did you etc-update after xfree, btw? If you can try emerging pdksh and if it fails, please e-me a tarball of your /etc/pam.d directory.
Tarball is in the mail. I did etc-update a few times now, the only thing with X at all was two files related to xdm options after installing blackbox. The only other file offhand was make.conf and it only had the diff with my COPT flags and the default commented out.
I just committed pdksh-5.2.14-r4 which contains a work around for what I think is a bug in the sandbox. /dev/fd/<foo> is the <foo>th file descriptor for a particular process - not floppy disk (that would be /dev/floppy/foo) ;-) -r4 works just fine on my system, so I'm closing this bug.
*** Bug 1756 has been marked as a duplicate of this bug. ***
