On Thu, Aug 14, 2014 at 7:24 PM, Ulrich <my.gr...@mailbox.org> wrote: > Am 14.08.2014 um 12:52 schrieb Mateusz Viste <mate...@viste.fr>: > >> Now the question is where to put any 3rd party apps that are still >> supposed to be callable from anywhere in the directories tree? One >> option could be to create another "BIN-like" directory for these > > No, I think creating another BIN directory like /usr/bin in GNU/Linux, where > we'd put all third-party executables, would complicate things. The next step > would be to put configuration files in /ETC.
<chuckle> As it happens, that's precisely what I did. Of course, I had a Unix machine at home before I got my first MS-DOS PC, and I spent some time setting up the PC to be as much like the Unix box as possible. Midway through, I discovered a commercial package called the MKS Toolkit, that offered DOS versions of every Unix command that made sense in the single-user, single-tasking environment like DOS. The killer feature for me was a complete implementation of the Unix Korn shell (my preferred shell under Unix) that included everything save asynchronous background processes. Install in fullest *nix compatibility mode, and you had to poke around to figure out you *weren't* on a Unix machine. Under FreeDOS, base FreeDOS stuff in FDOS/bin stays there. Other stuff goes in \bin or \usr\bin. Config files go in \etc. Major packages like AsEasyAs and the like go in sub-directories under \opt, and are run by batch files. I have DOS versions of the standard Unix utilities, so I can type ls at a command line instead of dir and not have the system go "Huh?" I don't recommend it as standard behavior for an installer, but I understand why people might like that organization. ______ Dennis https://plus.google.com/u/0/105128793974319004519 ------------------------------------------------------------------------------ _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
