From: Jan Willem Stumpel <jstumpel@planet.nl>
To: linux-msdos@vger.kernel.org
Subject: 1.2.0 binary install
Date: Thu, 22 Jan 2004 20:27:53 +0100 [thread overview]
Message-ID: <40102439.3090302@my.home> (raw)
The install from source works beautifully. I love dosemu; I think
the developers are great people, very helpful and responsive. This
surely must be one of the best projects in the free software world.
But I would like to have dosemu available to dummies, a.k.a.
ordinary users.
I tried out the binary install. First, very thoroughly, I removed
all previous installations of dosemu, freedos, and the dosemu fonts.
Then I downloaded from www.dosemu.org
dosemu-1.2.0-bin.tgz
dosemu-freedos-b9-bin.tgz
A) I did what README.bindist says.
$mkdir mydos
$cd mydos
$tar -zxf dosemu-freedos-bin.tgz
tar (child): dosemu-freedos-bin.tgz: Cannot open: No such file or
directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
Oops. The tarball should have been moved into ~/mydos first. This
is obvious, but not obvious to dummies.
B)
$cd
$cd mydos
$mv ../dose*z .
Again we follow the instructions in README.bindist:
$tar -zxf dosemu-freedos-bin.tgz
tar (child): dosemu-freedos-bin.tgz: Cannot open: No such file or
directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
Ahh.. the name of the file is different. Why, BTW? We should
rename it, according to the dosemu.org homepage, when we compile
from source. But we are using the binary distribution!
C) Third attempt
$tar -zxf dosemu-freedos-b9-bin.tgz
$tar -zxf dosemu-1.2.0-bin.tgz
This works. BTW why -zxf instead of vzxf? The v option gives some
reassuring feedback to users.
$ cd mydos
$ ./xdosemu
ERROR: X: Unable to open font "vga"ERROR: , trying "vga"...
ERROR: X: Unable to open font "vga"ERROR: , trying "9x15"...
And an x-dosemu window opens using an X terminal font. The binary
install can´t do the xset trick for including Xfonts in the font
path.
The same, of course, happens if you do NOT create a subdir called
mydos. The dosemu-bin and dosemu-freedos packages can also just be
unpacked from ~ (where the Ordinary User normally downloads it),
with all the stuff ending up in ~/dosemu. So why mydos?
Of course these problems are trivial for reasonably sophisticated
users. But many ordinary users just give up. Can´t we *at the very
least* provide some instructions which, if followed to the letter,
make the software work? Isn´t this worth some effort?
Regards, Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2004-01-22 19:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 19:27 Jan Willem Stumpel [this message]
2004-01-23 8:59 ` 1.2.0 binary install Ged Haywood
2004-01-23 21:03 ` Jan Willem Stumpel
2004-01-23 14:07 ` norseman
2004-01-23 22:38 ` Bart Oldeman
2004-01-23 15:45 ` norseman
2004-01-24 0:34 ` Bart Oldeman
2004-01-24 12:24 ` norseman
2004-01-24 23:16 ` Justin Zygmont
2004-01-24 18:00 ` norseman
2004-01-25 0:05 ` Bart Oldeman
2004-01-23 21:57 ` Bart Oldeman
2004-01-23 14:40 ` norseman
2004-01-23 23:08 ` Bart Oldeman
2004-01-23 16:30 ` norseman
2004-01-24 0:48 ` Bart Oldeman
2004-01-24 13:16 ` Ged Haywood
2004-01-24 12:48 ` Appology to Bart norseman
2004-01-24 15:16 ` 1.2.0 binary install Jan Willem Stumpel
2004-01-23 22:12 ` Ged Haywood
2004-01-23 22:15 ` Justin Zygmont
2004-01-23 15:01 ` norseman
[not found] <Pine.LNX.4.44.0401231719490.31850-100000@solarflow.dyndns.org>
2004-01-23 14:50 ` norseman
[not found] <40128B80.8060503@my.home>
2004-01-24 17:38 ` Bart Oldeman
2004-01-24 18:29 ` Jan Willem Stumpel
2004-01-24 19:08 ` Bart Oldeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40102439.3090302@my.home \
--to=jstumpel@planet.nl \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox