How to Install and Uninstall dosemu Package on openSUSE Leap

Last updated: May 17,2024

1. Install "dosemu" package

Please follow the step by step instructions below to install dosemu on openSUSE Leap

$ sudo zypper refresh $ sudo zypper install dosemu

2. Uninstall "dosemu" package

In this section, we are going to explain the necessary steps to uninstall dosemu on openSUSE Leap:

$ sudo zypper remove dosemu

3. Information about the dosemu package on openSUSE Leap

Information for package dosemu:
-------------------------------
Repository : Main Repository
Name : dosemu
Version : 1.4.0.1.r2065-bp155.2.11
Arch : x86_64
Vendor : openSUSE
Installed Size : 5.0 MiB
Installed : No
Status : not installed
Source package : dosemu-1.4.0.1.r2065-bp155.2.11.src
Upstream URL : http://www.dosemu.org
Summary : The DOS Emulator
Description :
This package allows MS-DOS programs to be run in Linux. A virtual
machine (the DOS box) provides the necessary BIOS functions and
emulates most of the chip devices (for example: timer, interrupt, and
keyboard controller).
Documentation can be found in /usr/share/doc/packages/dosemu, the man
page, and in the sources.
Starting with version 1.0.2, DOSEMU configuration files are no longer
in /etc but in the user's HOME directory in ~/dosemu. DOSEMU no longer
has the SUID bit set, so if you need access to hardware that requires
root privileges, you must run DOSEMU as root.
If you rely on the old configuration scheme, you can get it back by
using dosemu.bin instead of dosemu (dos and xdos have been renamed to
dosemu and xdosemu).
The parameter $_hogthreshold in ~/dosemu/conf/dosemu.conf defines how
often an idling DOSEMU should return the CPU to Linux and its default
value (1) means "all power to Linux." The higher this value is, the
more CPU power is dedicated to DOSEMU. The value (0) disables this
feature completely, hence: "all power to DOSEMU." If that is not fast
enough, you (running as UID root) can get maximum performance with
nice -19 dos -D-a 2>/dev/null
Do not be surprised if other Linux processes then run very sluggishly.
On sensitive systems, you should never offer an suid-root DOSEMU as
world readable. Even if the '$_secure' option in dosemu.conf is set, it
is still possible that some DPMI clients (most likely Dos4gw based
ones) may succeed in accessing the whole user space (including DOSEMU
code) and thus gain root access. A comfortable solution is to have two
copies of the DOSEMU binary, a non-suid-root one for world access and a
suid-root one (protected by file permissions) only available to trusted
users.