On Wed, Jul 26, 2017 at 04:00:43PM -0400, Christopher Clements wrote:
Wouldn't this work? (no error checking of course XD)off_t lseek(int fd, off_t offset, int whence); ssize_t write(int fd, const void *buf, size_t count); ssize_t pwrite(int fd, const void *buf, size_t count, off_t offset) { lseek(fd, offset, SEEK_SET); return write(fd, buf, count); }
On Wed, Jul 26, 2017 at 03:36:42PM +0200, Didier Kryn wrote:
I may be wrong here. What I actually remember is that, in the parameters received by the driver, there is an offset were to write to or read from. Therefore the current location is managed at a higher level, which may well be in the VFS and not in the libc. Sorry for that inacuracy.
Oh, maybe it won't. -- This email has NOT been checked for viruses by Avast antivirus software. http://0xc9.net Of course, there is _absolutely nothing_ stopping me from saying it _has_. Use common sense and most of your "security" becomes redundant. GPG Key: 0xF4CB50441726610D5AE0
signature.asc
Description: Digital signature
_______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
