Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filenames #4

Open
aloofschipperke opened this issue Oct 14, 2018 · 5 comments
Open

Filenames #4

aloofschipperke opened this issue Oct 14, 2018 · 5 comments

Comments

@aloofschipperke
Copy link
Collaborator

The four-component filename from ITS provided many interesting features for DDT.

Device and sname can be mapped directly. Fn1 fn2 not so much.

One option is to not implement fn2 -- device:dir;fn

Opinions?

@aloofschipperke
Copy link
Collaborator Author

I haven't implemented ITS-type filename parsing, but I'm preparing for it.
The code uses system calls such as openat(), which use a directory file descriptor, This maps nicely to "sname;".

No use of "dev:" yet,

@aloofschipperke
Copy link
Collaborator Author

The latest update includes filename parsing.
dev: dir; filename
Various arrangements of this should work.
The only dev: is currently dsk:, which is /.
The directory portion is parsed, but not supported yet.

@aloofschipperke
Copy link
Collaborator Author

aloofschipperke commented Dec 9, 2018

Some special filenames. Showing as two-name filenames, so not yet listing them in a checklist.

.file. (dir)
.m.f.d. (file)
..new. (dir) (typo here. correct one is ..new. (udir)
< as fn1 or fn2
> as fn1 or fn2

@eswenson1
Copy link

Are you sure the ..new. FN2 isn't (udir), rather than (dir)?

@aloofschipperke
Copy link
Collaborator Author

oof, yes.
Noting it above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants