Mike McCarty wrote:
> Jan Willem Stumpel wrote:
>
>> Bart Oldeman wrote:
>>
>>
>>> Anyway. another way to work around it is to change $_mapping.
>>> If you set it to "mapashm" or "mapfile" then dosemu should work
>>> again.
>>
>>
>> Thanks a lot. This worked.
>
>
> GREAT! But, why did it fail in the first place?
The immediate reason has been pointed out by Bart. A change in the
Debian initscripts package. The latest version in which dosemu
worked by default is initscripts_2.86.ds1-15_i386.deb. Last
Saturday, this was replaced by initscripts_2.86.ds1-20_i386.deb.
So the breakage seems to be Debian-specific (for now).
One of the "initscripts" is /etc/init.d/mountdevsubfs.sh, which
contains line like
(version 15, does not break dosemu)
SHM_OPT=
[ "${SHM_SIZE:=$TMPFS_SIZE}" ] && SHM_OPT="-osize=$SHM_SIZE"
domount tmpfs shmfs /dev/shm $SHM_OPT
("improved" version 20, breaks dosemu)
SHM_OPT=
[ "${SHM_SIZE:=$TMPFS_SIZE}" ] && SHM_OPT=",size=$SHM_SIZE"
domount tmpfs shmfs /dev/shm -onoexec,nosuid,nodev$SHM_OPT
This must have been done for security reasons, although I have no
clue about (the severity of) the security issues which are at
stake here.
I do not know why the Debian maintainer of dosemu himself did not
tweak to this breakage. Or maybe he did, and the Debian version of
dosemu now has a different $_mapping default. Haven't checked this
yet. Though a Debian user, I've been compiling my own dosemu from
source for years, not liking Debian's dosemu package (see my
"dosemu for dummies" page).
Regards, Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
