You might find this thread useful if it is just a case
of messed up firmware:
http://sourceforge.net/mailarchive/message.php?msg_id=2970511
The gist of it is that sometimes DOS utilities work
when all else fails.
ben
--- Ivan Matveich <[EMAIL PROTECTED]> wrote:
> On 11/2/06, Dan Williams <[EMAI
]> wrote:
> Benjamin Reed wrote:
> > In the case of lseek() and read(), you can use
> > pread().
>
> What is the meaning of the offset parameter of
> pread() for TCP or UDP etc?
>
> rick jones
>
-
To unsubscribe from this list: send the line "unsubscribe net
You are using the wrong examples, which may be why you
don't understand the problem Mark identified.
--- Christopher Friesen <[EMAIL PROTECTED]> wrote:
> There have always been possible issues with
> concurrent access to
> sockets/fds.
>
> Or consider calling lseek() from one task, while
> doing
David et al, I think you may be missing the point.
David S. Miller wrote:
> I don't understand why the desire is so high to
> ensure that individual threads get "atomic" writes,
> you can't even ensure that in the general case.
I think Mark's point isn't about "atomic" writes;
instead, he was po
