hdiutil notes: Difference between revisions
(categorize) |
m (re-categorize) |
||
| Line 21: | Line 21: | ||
Currently the only way I found around this is to manually copy the files in Finder. Maybe there's another command-line tool to preserve this data. Either way though, it means the disk image needs to be manually created with the right size. | Currently the only way I found around this is to manually copy the files in Finder. Maybe there's another command-line tool to preserve this data. Either way though, it means the disk image needs to be manually created with the right size. | ||
[[Category: | [[Category:macOS]] | ||
Revision as of 06:26, 20 January 2021
Notes and other random things related to the macOS hdiutil command.
Create a loop device
Similar to losetup for Linux, this allows setting up a loop device for any file. Usually hdiutil tries to determine how to attach the file based on the file extension and contents.
hdiutil attach -imagekey diskimage-class=CRawDiskImage -nomount myfile.bin
Create a RAM drive
Create a RAM drive. The value is the amount of 512-byte sectors, so 8388608 * 512 = 4294967296 or 4.0 GiB.
The drive is not pre-formatted, therefore -nomount is required, or else hdiutil will newly-created drive will be scanned for partitions, find none because it's completely blank, and cancel attaching.
hdiutil attach -nomount ram://8388608
After attaching it can be formatted with any tool, such as diskutil, Disk Utility, or newfs_*.
create -srcfolder doesn't preserve creation time
Still does this as of Big Sur. Creation time is reset to modified time. This isn't really an issue unless you're like me and want to preserve as much info as possible.
Currently the only way I found around this is to manually copy the files in Finder. Maybe there's another command-line tool to preserve this data. Either way though, it means the disk image needs to be manually created with the right size.
