From: Ivan Baldo <ibaldo@adinet.com.uy>
To: Gregor Horvath <horli@fsfe.org>,
linux-msdos <linux-msdos@vger.kernel.org>
Subject: Re: drives/* dir symbolic link names mapped to drive letters?
Date: Tue, 05 Nov 2013 12:34:32 -0200 [thread overview]
Message-ID: <527901F8.8010302@adinet.com.uy> (raw)
In-Reply-To: <20131103105508.67f826a4@valun>
Try adding a symlink for d, maybe pointing to /tmp if you want,
then I think your e and f drives would match.
It seems DOSEmu just traverses that directory in order and assigns
the driver letters disregarding the name of the symlink or directory there.
Bye.
El 03/11/13 07:55, Gregor Horvath escribió:
> Hello,
>
> I have a old dos installation with 3 discs as images, and created
> symlink to those images in the drives directory.
> I named the symlinks c,e,f and I want to be those the drives letters in
> dos.
> However this does not work. The drives are mapped to c,d,e.
>
> from boot.log:
>
> device: /home/gregor/.dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive
> C:
> device: /home/gregor/.dosemu/drives/e type 4 h: -1 s: -1 t: -1 drive
> D:
> device: /home/gregor/.dosemu/drives/f type 4 h: -1 s: -1 t: -1 drive
> E:
>
> Is this a bug or is it not meant that the symlink name gets mapped to
> the drive letter?
> How can I get the correct mapping?
>
> greg
>
--
Ivan Baldo - ibaldo@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: ibaldo@codigolibre.net - http://go.to/ibaldo
--
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
prev parent reply other threads:[~2013-11-05 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 9:55 drives/* dir symbolic link names mapped to drive letters? Gregor Horvath
2013-11-05 14:34 ` Ivan Baldo [this message]
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=527901F8.8010302@adinet.com.uy \
--to=ibaldo@adinet.com.uy \
--cc=horli@fsfe.org \
--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