execution problems and executable size questions

[Alfonso Acosta]

> Could you run dropbear with -F -E, and let me know what
> output it gives (if any)? Also, you can compile with
> DEBUG_TRACE set in debug.h, and it should give very verbose
> output. It'll make the binary a bit larger, though I think
> it should still fit.

Ok, that showed what the problem is, I paste what dropbear printed to stderr

# dropbear -F -p 22
[461] Jan 01 10:22:42 Not forking
[462] Jan 01 10:23:28 Child connection from 192.168.200.2:38096
[462] Jan 01 10:23:37 password auth succeeded for 'admin'
[462] Jan 01 10:23:37 exit after auth (admin): chmod(/dev/ttyp1, 0622)
failed: Read-only file system
[462] Jan 01 10:23:37 chown /dev/ttyp1 0 0 failed: Read-only file system
[462] Jan 01 10:23:37 chmod /dev/ttyp1 0666 failed: Read-only file system

/dev is part of the root file system (which is recorded into the flash
memory and it uses cramfs filesystem, so it can only be read)

Any ideas about how to solve the problem? (I can modify dropbear code
myself but I prefer asking you first if you don't mind)

-- 
Alfonso Acosta
http://babel.ls.fi.upm.es/~aacosta/