X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f Date: 23 Sep 2003 14:29:26 +0200 Message-Id: From: Eli Zaretskii To: "bdeck" CC: djgpp AT delorie DOT com In-reply-to: (bdeck@lycos.co.uk) Subject: Re: MOUNT.EXE References: <7ce56313 DOT 0309220111 DOT 61b9da4a AT posting DOT google DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: "bdeck" > Newsgroups: comp.os.msdos.djgpp,comp.os.msdos.apps > Date: Tue, 23 Sep 2003 13:00:09 +0200 > > > > No... the whole idea behind mount doesn't exist in MS-DOS. > > Very interesting... I have always wondered what it would take to make the > virtual directory table on DJGPP ("i.e. /dev/env/DJDIR, /dev/d, /dev/c, > /dev/com1, etc...) extensible. They _are_ extensible; see the node "File System Extensions" in the DJGPP library's reference docs. However, such extensions are private to the program that uses them. You cannot easily have a program like `mount' mount some pseudo-device and have that device visible in another program, unless you leave some record to that effect on disk or something. > Perhaps a mock 'mount' and 'umount' > executable could add additional devices and physical directories (even > commands) to the DJGPP.ENV.... It would be a very bad idea IMHO to rewrite DJGPP.ENV to support this kind of feature. It's better to record the info on some other file.