Sorry, I don't have that book. I only have TCP/IP illustrated Part 1.
> at hand and I can't remember page number) it will tell you which
> particular flavour (AT&T SVR3 or something similar) did that. I definitely
> (but vaguely, 5-6 years ago or so) remember situations where negative
> offsets off /dev/kmem were valid and useful.
Tigran,
I can immagine 2G - 4G offsets being functional as offsets into
"/dev/kmem".
However, "lseek" behaviour is then undefined. I mean, Linux has taken
the approach to disable (normal) files larger than 2G for this reason,
just to prevent lseek from having to return negative numbers.
Whenever you're dealing with an application that is legitimately
messing around with the 2G-4G area of a /dev/kmem file, it better be
very careful. Which officially means: "lseek doesn't return valid
values". On Linux at least the errno value will be set to preposterous
values, whenever you enter the "negative" area of "kmem".
Roger.
-- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* "I didn't say it was your fault. I said I was going to blame it on you."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/