Hi,

starting matlab R13 on a netbsd-3 machine with suse 9.1 packages 
installed gives me (ktrace'd):

[...]

    746 matlab   RET   ioctl 0
    746 matlab   CALL  rt_sigaction(0x11,0xbfbfa7f0,0xbfbfa760,8)
    746 matlab   RET   rt_sigaction 0
    746 matlab   CALL  rt_sigprocmask(1,0xbfbfa980,0,8)
    746 matlab   RET   rt_sigprocmask 0
    746 matlab   CALL  open(0x80b783d,2,0xbfbfc488)
    746 matlab   NAMI  "/emul/linux/dev/ptmx"
    746 matlab   NAMI  "/dev/ptmx"
    746 matlab   NAMI  "/dev/ptyp2"
    746 matlab   RET   open 3
    746 matlab   CALL  ioctl(3,_IO('T',0x1,0),0xbfbf993c)
    746 matlab   RET   ioctl 0
    746 matlab   CALL  ioctl(3,_IOW('T',0x30,0x4),0xbfbf99fc)
    746 matlab   GIO   fd 3 read 40 bytes
        "\^B\0\0\0\^B\0\0\0/dev/ptyp2\0\0\0\0\0\0/dev/ttyp2\0\0\0\0\0\0"
    746 matlab   RET   ioctl 0
    746 matlab   CALL  stat64(0xbfbf9ad0,0xbfbf9a20)
    746 matlab   NAMI  "/emul/linux/dev/pts/2"
    746 matlab   NAMI  "/dev/pts/2"
    746 matlab   RET   stat64 -1 errno -2 No such file or directory
    746 matlab   CALL  fcntl64(3,1,2)
    746 matlab   RET   fcntl64 0
    746 matlab   CALL  rt_sigaction(0x11,0xbfbfa7f0,0xbfbfa760,8)
    746 matlab   RET   rt_sigaction 0
    746 matlab   CALL  rt_sigprocmask(1,0xbfbfa980,0,8)
    746 matlab   RET   rt_sigprocmask 0
    746 matlab   CALL  fstat64(1,0xbfbf4304)
    746 matlab   RET   fstat64 0
    746 matlab   CALL  ioctl(1,_IO('T',0x1,0),0xbfbf4258)
    746 matlab   RET   ioctl 0
    746 matlab   CALL  old_mmap(0xbfbf42ec)
    746 matlab   RET   old_mmap -1141690368/0xbbf33000
    746 matlab   CALL  rt_sigprocmask(0,0xbfbf4338,0xbfbf43f8,8)
    746 matlab   RET   rt_sigprocmask 0
    746 matlab   CALL  rt_sigprocmask(1,0xbfbf4338,0,8)
    746 matlab   RET   rt_sigprocmask 0
    746 matlab   CALL  write(1,0xbbf33000,0x185)
    746 matlab   GIO   fd 1 wrote 389 bytes
        "\a??? MATLAB was unable to open a pseudo-tty: No such file or 
directory [2,1]
         The unix() and ! commands will not work in this MATLAB session. 
  Other
         commands which depend upon unix() and ! will also fail.  Your 
system may
         be running low on resources.  If the problem persists after a 
reboot,
         check with your system administrator and confirm that your pty 
subsystem
         is properly configured.

        "

Is there something to set up especially for emul_linux, or what am I 
missing? Kernel is a vanilla GENERIC_DIAGNOSTIC, the distribution built 
from sources two days ago.

Hints appreciated,

	hauke