"The system has no more ptys. Ask your system administrator to create more."

czeslafff · 01-22-2006, 04:40 PM

Hi,
everything was OK, but now when I'm in chapter 6.13.1, after

Code:

expect -c "spawn ls"

I get this message

Code:

The system has no more ptys.  Ask your system administrator to create more.
    while executing
"spawn ls"

However when I run this command as a lfs without chrooting everything is OK...
Now I really don't know what to do next... I found some wiki pages with solution of this problem, but it's all dead links...
Any ideas??

320mb · 01-23-2006, 06:24 AM

try this and see if it helps.......

Code:

chmod 777 /dev/ptmx

czeslafff · 01-23-2006, 07:55 AM

I tried to chmod /dev/ptmx... After that i get the same message...
I read in one of previous releases of LFS book about compilling MAKEDEV and I've even compiled it and made ptys, but it didn't help...

check8 · 02-08-2007, 07:47 AM

Quote:

Originally Posted by 320mb

try this and see if it helps.......

Code:

chmod 777 /dev/ptmx

I have the same problem.
Will that code work on LFS 6.2?

biniou · 02-08-2007, 08:02 AM

Sometimes it helps reading the book ...

Here the link found page 49 : http://www.linuxfromscratch.org//lfs/faq.html#no-ptys

fancylad · 02-10-2010, 11:34 AM

sometimes it helps to not be a smart ass about it either.

crts · 02-10-2010, 06:12 PM

Quote:

Originally Posted by czeslafff

Now I really don't know what to do next... I found some wiki pages with solution of this problem, but it's all dead links...
Any ideas??

Hi,
please also post which version of the book you are using and the host system that you are using to build your LFS.
It is not uncommon that an LFS-build because the host system does not meet the requirements.
That is why I recommend to use the LFS liveCD at least for the first build.

When chrooted, what is the output of

Code:

ls /dev/

If the output is something like

Code:

console null

and nothing more you probably just forgot to mount the /dev directory at the beginning of chapter 6 or you. You have to perform those mounts everytime you chroot into your build-partition. I would start bug tracing at this point before following the previously linked FAQ and recompiling the kernel.

spoovy · 03-05-2010, 02:22 PM

I had this problem, went back through the mount --bind /dev setup process, chrooted again, and it was solved.

You've probly tried that but thought i'd mention it anyway. Sometimes its the simplest thing..

xscrat · 04-24-2012, 05:35 AM

As indicated in LFS6.6
Use the following mount commands:
mount -v --bind /dev $LFS/dev
mount -vt devpts devpts $LFS/dev/pts
mount -vt tmpfs shm $LFS/dev/shm
mount -vt proc proc $LFS/proc
mount -vt sysfs sysfs $LFS/sys

then chroot, it'll help.

druuna · 04-24-2012, 06:07 AM

@xscrat:

First of all: Welcome to LQ!

This thread was started 6 years ago and the correct answer was given in post #5. Besides the fact that your answer isn't correct (this is a host kernel issue, not a mount issue), it is also not done to resurrect old threads.

Tokeii · 07-16-2012, 05:15 AM

@xscrat

Thanks for your post, I did what you said and It worked great.
there was no need to do what's specified in post 5.