aboutsummaryrefslogtreecommitdiff
path: root/system/virtualxt/README
diff options
context:
space:
mode:
Diffstat (limited to 'system/virtualxt/README')
-rw-r--r--system/virtualxt/README36
1 files changed, 16 insertions, 20 deletions
diff --git a/system/virtualxt/README b/system/virtualxt/README
index 3c5be46b1ef00..113ecf586e6ba 100644
--- a/system/virtualxt/README
+++ b/system/virtualxt/README
@@ -16,12 +16,13 @@ by a comma.
For example:
-EXCLUDE_MODULES=fdc,network ./virtualxt.SlackBuild
+EXCLUDE_MODULES=serial,network,covox ./virtualxt.SlackBuild
The following modules cannot be excluded:
adlib
arstech_isa
+bios
cga
ch36x_isa
chipset
@@ -31,43 +32,38 @@ ems
joystick
mouse
rifs
-serial_dbg
+rtc
+uart
The virtualxt binary is built with an SDL2 frontend and meant to be run
by a non-root user. The user will need to be added to the "users"
group because the binary will open the provided boot images in read-
-write mode and "users" has write access to those images.
+write mode, and "users" has write access to those images.
For example:
usermod -aG users bob
-The user's current working directory must be the same directory where
-the virtualxt binary is installed. Because of this requirement, the
-binary cannot be installed to a traditional location (e.g. /usr/bin/).
+Either the LD_LIBRARY_PATH or LD_PRELOAD variable must be configured
+to point to /usr/lib64/virtualxt. For bash users, this can be
+accomplished as follows:
-A wrapper script, virtualxt-wrapper.sh, has been provided so that the
-user does not have to change to the directory where the virtualxt
-binary is installed. This wrapper script may be found in
-/usr/share/virtualxt/ and copied to a traditional location for
-storing binaries.
+export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/virtualxt
+echo "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/virtualxt" \
+ >> ~/.bashrc
-For example:
+...or...
-cp /usr/share/virtualxt/virtualxt-wrapper.sh \
- /usr/bin/virtualxt-wrapper.sh
-chmod +x /usr/bin/virtualxt-wrapper.sh
+LD_PRELOAD=/usr/lib64/virtualxt/libvxt.so virtualxt
-The wrapper script may then be executed as if the user's current
-working directory is actually the directory where the virtualxt binary
-is installed.
+The path to the boot image must be specified when running virtualxt.
For example:
-virtualxt-wrapper.sh -a boot/freedos.img
+virtualxt -a /usr/share/virtualxt/boot/freedos.img
If after upgrading from a previous version of virtualxt the console
fails to start, then you may need to generate a new config file as
follows:
-virtualxt-wrapper.sh --clean
+virtualxt --clean