public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Willem Stumpel <jstumpel@planet.nl>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.2.0 binary install
Date: Fri, 23 Jan 2004 22:03:53 +0100	[thread overview]
Message-ID: <40118C39.1000809@my.home> (raw)
In-Reply-To: <Pine.LNX.4.21.0401230841400.20732-100000@www2.jubileegroup.co.uk>

Ged Haywood wrote:

> Actually I dislike the verbosity,
My point was that I think *dummies* like the verbosity. If you are
a dummy, then of course I am mistaken.

> but 'v' option or not, the tar manpage on my boxes says: [..]
Linux as a whole (not only dosemu) suffers from incredibly bad
documentation. xfzv works, and has worked for years, in any
permutation.

> Sounds like time to send in a documentation patch. I tell you
> what.  You write it, I'll test it.  Deal?
You never (as you said) even tried the binary install. Some
tester! But I did. Let's do it the other way round: you make it
work (including the font part), then I write the doc. Deal?

Seriously: I think the binary install should do exactly the same
that the (excellent) source install does; i.e. it should put
exactly the same files in exactly the same locations (/usr/local)
that are used by ./configure, make, [become root] make install. It
should just free the dummy user from the compilation step, for
which he/she most probably lacks the tools, and would be
confronted with (to her/him) incomprehensible error messages
because of that. It should (like the source install) also be
independent of freedos, because dosemu itself is independent of
it. Like the source install, it should ask which directory is the
'C drive'. If user/dummy does not know, it should be pointed out
that some form of DOS is needed, and installation of freedos offered.

> PS: Do you always send UTF-8?
In principle, yes.. but in Mozilla, apostrophes often behave
weirdly, don't quite understand why. ASCII is supposed to be valid
UTF-8. 'Send'? '73'? Radio?

Regards, Jan




  reply	other threads:[~2004-01-23 21:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 19:27 1.2.0 binary install Jan Willem Stumpel
2004-01-23  8:59 ` Ged Haywood
2004-01-23 21:03   ` Jan Willem Stumpel [this message]
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=40118C39.1000809@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