i'm well aware of the use of the pseudo tty ports under /dev/pts,
but i never understood the value of having a distinct "devpts"
filesystem, until today.
i was working with an embedded system with a flashed root filesystem
that included /dev so, obviously, everything under /dev was also read
only. i installed dropbear for an ssh server, but every attempt to
ssh to that system failed.
after tracing the operation of dropbear, i tracked it down to the
fact that dropbear was trying to open a pseudo-port corresponding to
the connection and was, of course, failing since all of /dev was
read-only.
after i mounted /dev/pts (rw), ssh connections started to work. is
this why /dev/pts was developed? to work around RO /dev directories?
or was there some other reason?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [email protected]
Please read the FAQ at http://kernelnewbies.org/FAQ
