openpty failed: 'out of pty devices' why it looks for?

pappy_mcfae · Posted: Fri Jan 09, 2009 7:51 am Post subject:

Because you don't have any defined in your kernel .config. You can set them up under Character Devices. It defaults to using 256 pty devices, which should be plenty. For reference, you can look through one of my seed kernels. I have that set up by default.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.

padoor · Advocate Joined: 30 Dec 2005 Posts: 4185 Location: india

thanks pappy
how r u doing thses days ? very busy?

it does not look like evdev unmerged.
emerge -Duav world is calling evdev also again.
which anyway i will unmerge again.
in chroot env it has difficulty in unmerging evdev.
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)

widremann · Veteran Joined: 14 Mar 2005 Posts: 1314

openpt() uses UNIX-98 style ptys, which requires the existence of /dev/ptmx (the pty master) and /dev/pts/ (a directory that gets a new entry for every pty that is actually created). /dev/pts/ is mounted as filesystem type devpts. Since you are in a chroot, my guess is that you did not do a bind mount of /dev from your live system to the chroot and so these pty device nodes don't exist in your chroot. You should do a "mount -o bind /dev /mnt/gentoo/dev" (where /mnt/gentoo is the path to your chroot) before chrooting and see if that helps.

padoor · Advocate Joined: 30 Dec 2005 Posts: 4185 Location: india

widremann

you are right .i mounted only the / partition and chrooted.
but even after booting from this partition i unmerged again.
still the update wants the evdev back again.
my same problem of keyboard putting up 3 3 charecters for each press comes back if i emerge this evdev.
i thought for merging packages only we need the /dev to be mounted in chroot and proc ofcourse.
unmerge also did not work anyway though it said unmerged.
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)

pappy_mcfae · Posted: Fri Jan 09, 2009 7:13 pm Post subject:

waebbl · n00b Joined: 06 May 2004 Posts: 42 Location: Munich, DE

I know this post is quite old, but today I ran into the same problem, so there's a chance the post might still be interesting for some people.

It happens, although /dev was bind-mounted inside the chroot. I never noticed this before inside a chrooted environment.

The key here is to use --rbind instead of --bind, which also rebinds the /dev/pts and /dev/shm filesystems. By exiting the chroot, unmount ${CHROOT}/dev and mount it again using the rbind option, it worked. I was used to use the rbind option, because the handbook uses that option before changing into the chroot, but today I just used the bind option, just because I saw it on a lot of articles on the net.

padoor · Advocate Joined: 30 Dec 2005 Posts: 4185 Location: india

thanks for sharing this info
why the doc does not say about --rbind ?[still using --bind only]
thanks waebbl

_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)

waebbl · n00b Joined: 06 May 2004 Posts: 42 Location: Munich, DE

Well, afair the installation handbook is using --rbind option.
The docs I was referring to, are some other docs around (mainly about building livecds) which are using --bind.

nickel · Posted: Sun Sep 06, 2015 4:28 pm Post subject:

i just wanted to say, thx. Even though 4 years later, it helped me