• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

MakefileH A D14-Apr-2019473 2414

READMEH A D14-Apr-20191.3 KiB4330

bosmeta.cH A D14-Apr-20196.8 KiB338233

bosmeta.hH A D14-Apr-20191.8 KiB7541

ctype.cH A D14-Apr-20193.5 KiB10350

dosdir.cH A D14-Apr-20194.5 KiB237182

dosdir.hH A D14-Apr-20191.8 KiB5030

dosfile.cH A D14-Apr-20195.5 KiB288193

dosfile.hH A D14-Apr-2019823 2811

dosfsfn.cH A D14-Apr-20199.1 KiB462288

emu_tos.hH A D14-Apr-20192.8 KiB12475

list.hH A D14-Apr-20195.5 KiB19452

main.cH A D14-Apr-20191.8 KiB11369

mdglue.SH A D14-Apr-20198.7 KiB514395

metados.hH A D14-Apr-20195.5 KiB189136

mintfake.hH A D14-Apr-20191.3 KiB6438

utility.cH A D14-Apr-201926.1 KiB1,2801,042

utility.hH A D14-Apr-20192.4 KiB10453

README

1BetaDOS x:\dev filesystem driver
2================================
3
4The dev.dos is a driver that creates the u:\dev folder known from the
5FreeMiNT and MagiC environment. The motivation is to create identical
6environment by which any HW dependent access is encapsulated. That
7approach is present in UNIX-like environments and is present in
8FreeMiNT as its fundamental concept.
9
10The aim is to make developers provide special driver for any HW (or
11NF which is considered to be OS only acces feature) they create. Such
12driver would make it possible to create an equivalent on another
13machine with the same interface and would automaticaly impose some
14level of reusability. So for TOS environments one would create BetaDOS
15.BOS device driver and for FreeMiNT .XDD device driver.
16
17This dev.dos driver automatically scans any .BOS driver loaded by
18BetaDOS and creates appropriate x:\dev\bos folder entry for each.
19It also asks the particular .BOS driver for an information whether
20it should also be placed into the x:\dev under its name.
21(FIXME: provide another ioctl() to provide better name?).
22
23Just install it to the bdconfig.sys e.g. as:
24...
25*BOS, \auto\nfstderr.bos, E
26
27*DOS, c:\auto\dev.dos, X:2
28...
29
30And you will get:
31
32X:\dev\bos\E
33X:\dev\nfstderr
34
35Ehere the nfstderr is actually like a hardlink to the bos\E entry.
36
37More documentation to come on this topic.
38
39Best Regards
40
41STanda
42
43