-
Notifications
You must be signed in to change notification settings - Fork 30
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
Request:udf info tool #4
Comments
For this information you can use blkid tool from util-linux package. |
Forgot about this. Having trouble with that but thanks for the advice. |
I think a udfinfo would still be a good idea, if for no other reason than for copying disks. In order to make an image of a disk, it is sometimes necessary (depending on the DVD drive) to know how many blocks to read. |
Original request was for UDF id and label. Both information can be retrieved by blkid, hence I closed this request. Your request is for utility which report number of blocks of UDF disk just for ability to read UDF image from optical disk? Then you probably want udfdump utility which would copy/dump UDF disk image. That is really something different as described in this (now closed) ticket. |
@kickerofelves @themaddoctor Now I implemented a new tool called udfinfo which prints various information about UDF disk, including UDF identifiers, label, uuid and also count of free/used disk blocks. This tool is suitable for using by external applications or scripts and now in master branch, introduced in commit 48d996a and would be part of the udftools 2.0. So I hope it would help you (if you are still interested in it). |
Thank you. Will try it. |
udftools 2.0 with udfinfo was already released https://github.com/pali/udftools/releases/tag/2.0 |
We need something like isoinfo for udf. I used isoinfo in scripts to retrieve the volume id/label. Although I can set the label using mkudffs I don't see a way to retrieve this information post-burn. If there is (as non-root), let me know.
Thanks
The text was updated successfully, but these errors were encountered: