Supported entry types #1

Closed
opened 2022-11-21 19:33:16 +00:00 by apio · 1 comment
Owner

MTAR_BLKDEV and MTAR_CHRDEV are only supported because we say so. This is kind of wrong, since they are not supported in any means. We do not store any kind of device number anywhere. Thus, they should probably be removed from the list of supported entry types, I guess.

MTAR_BLKDEV and MTAR_CHRDEV are only supported because we say so. This is kind of wrong, since they are not supported in any means. We do not store any kind of device number anywhere. Thus, they should probably be removed from the list of supported entry types, I guess.
apio added the
invalid
label 2022-11-21 19:33:16 +00:00
apio self-assigned this 2022-11-21 19:33:16 +00:00
apio closed this issue 2022-11-30 10:21:03 +00:00
Author
Owner

Supported now, along with symlinks, hard links and FIFOs. API.md#minitar_file_type

Supported now, along with symlinks, hard links and FIFOs. [API.md#minitar_file_type](https://git.cloudapio.eu/apio/minitar/src/branch/main/docs/API.md#minitar_file_type)
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: apio/minitar#1
No description provided.