From: Robert Komar <rkomar@telus.net>
To: linux-msdos@vger.kernel.org
Subject: Re: The first dosemu-1.2.0 release candidate is available!
Date: Tue, 30 Sep 2003 09:15:26 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0309300827460.367@robpc2.home.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0309301558110.4180-100000@enm-bo-lt.localdomain>
On Tue, 30 Sep 2003, Bart Oldeman wrote:
> On Tue, 30 Sep 2003, Ralph Alvy wrote:
>
> > Ralph Alvy wrote:
> > > Here's what I get after unpacking and running the 1.1.99.1 binary:
> > >
> > > ---
> > >
> > > [ralvy@localhost dosemu]$ ./xdosemu
> > > ./xdosemu: line 1: readlink: command not found
> > > ./xdosemu: line 285: cd: /../Xfonts: No such file or directory
> > >
> > > You do not have the DOSEMU vga font installed and are running
> > > remote X. You need to install the vga font on your _local_ Xserver.
> > > Look at the readme for details. For now we start with an fixed font,
> > > which does not display all national characters correctly.
> > > ... be warned
> > >
> > > ./xdosemu: line 375: /../bin/dosemu.bin: No such file or directory
> > > ./xdosemu: line 375: exec: /../bin/dosemu.bin: cannot execute: No such
> > > file or directory
> >
> > Shouldn't the script execute
> >
> > cd ./Xfonts
> >
> > instead of
> >
> > cd /../Xfonts
> >
> > And the same for
> >
> > cd /../bin
>
> no, the problem is that you don't have "readlink". But fortunately we can
> read a link using "ls" and, that combined with "sed" gives us a the poor
> man's readlink:
>
> BOOT_DIR_PATH=`ls -l $HOME/.dosemu/drives/c | sed 's/.* \([^ ]*\)$/\1/'`/..
> (line 245 of the script).
> Please try this instead of my previous workaround.
Hi,
this doesn't look like it will work if there is a space somewhere in
the path. If awk is available on every system, then how about this:
BOOT_DIR_PATH=`ls -l $HOME/.dosemu/drives/c | awk -F"-> " '{ print $2 }'`/..
It uses "-> " as the field separator instead of the space. On my system,
the last '/' isn't required (the contents of the link already have a
trailing slash), but I guess it doesn't hurt to leave it there.
Another option would be for dosemu to roll its own version of readlink
based on readlink(2). Something like:
#include <unistd.h>
#include <stdio.h>
int main(int argc, char** argv)
{
char buf[BUFSIZ];
if ((argc == 2) && (readlink(argv[1], buf, BUFSIZ) != -1))
printf("%s\n", buf);
return 0;
}
Cheers,
Rob Komar
next prev parent reply other threads:[~2003-09-30 16:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 22:21 The first dosemu-1.2.0 release candidate is available! Bart Oldeman
2003-09-30 12:21 ` A. Alper ATICI
2003-09-30 12:50 ` Bart Oldeman
2003-09-30 19:20 ` A. Alper ATICI
2003-09-30 19:35 ` Bart Oldeman
2003-09-30 13:50 ` Ralph Alvy
2003-09-30 14:35 ` Ralph Alvy
2003-09-30 15:02 ` Bart Oldeman
2003-09-30 16:15 ` Robert Komar [this message]
2003-09-30 17:13 ` Bart Oldeman
2003-09-30 17:57 ` Robert Komar
2003-10-01 7:21 ` Sylvain Petreolle
2003-10-01 3:17 ` Ralph Alvy
2003-10-01 10:50 ` Bart Oldeman
2003-10-01 21:30 ` Ralph Alvy
2003-09-30 14:37 ` Bart Oldeman
2003-10-01 14:12 ` A. Alper ATICI
2003-10-01 14:42 ` Bart Oldeman
2003-10-01 15:27 ` Ged Haywood
2003-10-01 19:56 ` Bart Oldeman
2003-10-02 22:10 ` Ralph Alvy
2003-10-02 23:33 ` Bart Oldeman
2003-10-03 0:06 ` Ralph Alvy
2003-10-03 1:38 ` Ralph Alvy
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=Pine.LNX.4.58.0309300827460.367@robpc2.home.org \
--to=rkomar@telus.net \
--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