Thanks for your bug-report, but you should have checked the web page
more
frequently. The current release is 0.05 and 0.06 will be released within
the next days
> 1) Right now, a /proc/mergemem file is created with a (dummy) read operation,
> an open (and close) operation and a write operation that accepts a certain
> struct, whose members may change as a result. The return value of write()
> is used to indicate success or failure.
>
> Instead of this, it *really should* be a char device driver, with just three
> operations: open, close and ioctl. The ioctl operation is just right for
> this sort of stuff. The driver can then accept two kinds of ioctl requests:
> checksum and mergemem.
In the CVS it's already a character device with ioctls.
It will appear in 0.06
[...]
> To conclude, this can really be a useful tool, but right now, it's
> more like an uncut diamond :^). As promised, I'll look deeper into it
> during the next couple of days and see what exactly happens.
>
> Marnix Coppens
I will look into all issues you described, may I ask you to look also to
have
a look at a more recent version of mergemem ?
0.05 is current, 0.06 will appear tomorrow or on sunday.
Philipp Reisner
------------------------------------------------------------------------
Want to try something new? Are you a Linux hacker?
Volunteer in testing mergemem!
(Get it from http://www.mondoshawan.ml.org/mergemem)
-----
Philipp Reisner E-Mail mailto:e9525415@student.tuwien.ac.at
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu