Hi! Thx for the fast response. > On Sun, 11 Jan 2004, James B. Hiller wrote: > > > Been running 1.0.2.1 for quite awhile and it's been doing great for me. > > > > Recently went into the 2.6 kernels, starting with 2.6.0. Things were > > fine with that one, and with the first 2.6.1 release candidate > > (specifically, 2.6.1-rc1-mm1). I had to go to that one to start > > resolving some ide cd burning issues I was having. > > "mapshm" is broken. Use the workaround > $_mapping = "mapfile" > in dosemu.conf > > Or alternatively the kernel patch below.
Ok. Tried the dosemu.conf change, but it didn't do the trick. But the kernel patch did. This was with 2.6.1-mm2. I didn't try it with -mm1, but I suspect it would be just fine. > Problem is that the case where new_len==0 was a security hole. Linus went > one step further and also disallowed old_len==0. This is not a security > hole, but deals with a somewhat tricky (and apart for source code > undocumented) interface that DOSEMU happens to use. Hopefully Linus or > Andrew Morton can revert it and apply this patch. Is it something you've sent in? > As long as you don't use DPMI the workaround is enough for 1.0.2.1. Didn't have DPMI turned on in dosemu.conf (it's set to (off)), so unless it's getting set on elsewhere that I wouldn't know about, seems to be something more than this. Just curious - would you recommend going to 1.1.99? I've got the tar sitting here, just in case. thx, jbh - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
