muta...@gmail.com
2021-04-25 18:43:51 UTC
I was thinking that an application doing
fopen("fred.txt", "r");
will access the local file known by the OS,
but ":fred.txt" will go one level up, whoever
that is. And "::fred.txt" will go two levels up,
etc.
You may go ":::dd:fred" because that level up
is an MVS mainframe.
An application is not expected to hardcode any
of these names. The user or some other method
will inform that.
Speaking of which.
I was thinking fopen of ":harddisks" would return
(via fgets()) a list of hard disks, perhaps ":0x81"
etc, which can then be opened as raw devices,
suitable for fdisk to be implemented.
BFN. Paul.
fopen("fred.txt", "r");
will access the local file known by the OS,
but ":fred.txt" will go one level up, whoever
that is. And "::fred.txt" will go two levels up,
etc.
You may go ":::dd:fred" because that level up
is an MVS mainframe.
An application is not expected to hardcode any
of these names. The user or some other method
will inform that.
Speaking of which.
I was thinking fopen of ":harddisks" would return
(via fgets()) a list of hard disks, perhaps ":0x81"
etc, which can then be opened as raw devices,
suitable for fdisk to be implemented.
BFN. Paul.