Sergey Kish <[email protected]> once said:
> Today I've implemented same on go. It also falls but it may be my
> fault
>
> error: read /dev/draw/new: unknown id for draw image
You're giving bad data to devdraw. The Go code on the gist
is sending
long(id) 'n' long(id) byte(namelen) string(name)
but that first long will cause the write to fail. Also,
you should really check the errors from any system call
instead of discarding them. The error from the read is
a red herring in this case (but still expected because
the named image allocation failed).
Now for the Python and Ruby code, I really have no idea.
I would check to see if their standard library requires
that you flush after writes.
Hope that helps.
Anthony
