Building latest Unix VM - how?
lex at cc.gatech.edu
Sat Jan 19 22:14:38 UTC 2002
> Anyway, it wouldn't be too hard to fiddle a bit with code generation
> here, methinks.
This is in Unix-specific code, so that won't work directly. It would
still make sense to define these functions. Maybe with something about
"restart" in the name, e.g. "rread" and "rwrite". Put them all in a
ressys.c file, make a ressys.h with all the prototypes, and away we go!
Either way is fine, though.
> (BTW, I don't think open() can return EINTR. A grep through the Linux
> section 2 manpages returns 'accept chdir chmod chown chroot close connect
> dup execve fcntl mknod msgop nanosleep pause poll read readv recv select
> semop send sigaction sigpause stat truncate unlink ustat utime wait
> wait4 write')
Maybe, but would you want to chance it? I've observed readdir()
returning EINTR on Solaris, which doesn't seem to be in the list.
> Wouldn't it be an idea to start working in this direction? Wrapping the system
> calls is just dumb typing work, I'm sure that the 20-or-so people that are on
> the Sqeak SF project developer list - or at least the subset with an interest
> in Linux/Unix - could do that in a couple of days.
:) It's not *that* bad I don't think -- more like a few hours, I would
hope. But... I've always had something more interesting to work on,
whenever I find a few hours to tinker with Squeak!
More information about the Squeak-dev