Upgrading that package to 2.11.9.4 and BTW unmerging 2.11.9.3 gives within my chrooted UML image: ... >>> Unmerging dev-db/phpmyadmin-2.11.9.3... openpty failed: 'out of pty devices' ... However unmerging was done succdessful AFAICS. Reproducible: Always
B/c the same happended for glibc too: ... >>> Emerging (1 of 1) sys-libs/glibc-2.6.1 openpty failed: 'out of pty devices' ... I changed summary to portage
Did you `mount --bind /dev' and `mount -t proc none' into that chroot?
(In reply to comment #2) > Did you `mount --bind /dev' and `mount -t proc none' into that chroot? > Yes, the 2nd I did (I mounted proc, b/c w/o that emerge of mysql failed) - however I didn't mount /dev into that chroot -probably that's the issue ?
Although I closed this bug I observed this a minute ago within the chrooted UML image : >>> Unmerging dev-util/unifdef-1.20... openpty failed: 'out of pty devices' However I mounted both /proc and /dev (furthermore some more dirs to share7save disk space) : tfoerste@n22 ~ $ mount | grep loop /dev/loop0 on /mnt/loop type ext3 (rw) none on /mnt/loop/proc type proc (rw) /dev on /mnt/loop/dev type none (rw,bind) /usr/portage on /mnt/loop/usr/portage type none (ro,bind) /usr/local/portage on /mnt/loop/usr/local/portage type none (ro,bind) /var/tmp/ccache on /mnt/loop/var/tmp/ccache type none (rw,bind) /mnt/uml/var/tmp/portage on /mnt/loop/var/tmp/portage type none (rw,bind)
And FWIW within the chrooted env this dir is empty : /dev/pts/
you have to bind-mount /dev/pts too if you wish to avoid this issue. Bindmounting /dev alone is not enough in this case. (I've hit this bug often enough in the past :) )
What about adding the additional info about bind-mounting /dev/pts to the handbook?
I solved this with: mount --rbind /dev /path/dev
This is clearly a documentation issue. The documentation should make clear that mount --rbind should be used (if it works - didn't test it myself so far). I don't have permission to reassign or reopen the bug - please change it to "Documentation" and reopen it.
re-opened per request
(In reply to comment #8) > I solved this with: mount --rbind /dev /path/dev > BTW this doesn#t work for me, b/c unmounting wasn't possible - I had to reboot the host system.
@docs-team: The handbook needs this to be added wherever /dev (or other directories which have multiple mounts inside them) are bind-mounted into a chroot. I don't know the proper procedure to get this done, but since it seems straight-forward enough, I thought I'd assign it to you (I'm CCed now).
Created attachment 247246 [details, diff] Patch for gentoo-x86-quickinstall-stage.xml
Created attachment 247248 [details, diff] Patch for gentoo-x86-tipsntricks.xml
Created attachment 247249 [details, diff] Patch for hb-install-mips-system.xml
Created attachment 247251 [details, diff] Patch for hb-install-ppc-bootloader.xml
Created attachment 247253 [details, diff] Patch for hb-install-system.xml
Created attachment 247254 [details, diff] Patch for migration-to-2.6.xml
BTW, quite a few guides in the proj/en location also use the standard bind-mounts. I don't know if those are managed by docs-team as well nowadays or not.
*** Bug 358041 has been marked as a duplicate of this bug. ***
Changing to --rbind also solves bug 358041. I can now only umount it with sudo umount -l gentooxo-1.1/dev though. @Jeroen Roovers: Sorry. You were right: It is a duplicate. Thanks for tracking it!
$ sudo mount --rbind /dev gentooxo-1.1/dev Passwort: $ sudo umount gentooxo-1.1/dev umount: /home/arne/Dokumente/eigenes/Programme/GentooXO/gentooxo-updating/gentooxo-1.1/dev: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) $ lsof gentooxo-1.1/dev $ fuser gentooxo-1.1/dev $ sudo umount -l gentooxo-1.1/dev $
Fixed in CVS. Thanks to swift for the patches!
