How do you set the preference to auto-mount certain volumes, while others are blocked at login?

[ghost]

Thanks for this Aaron! I've read the README, still can't figure out how to make sure some volumes mount (mainly..main boot volume), while others are set to block. What does 'Attach' do?

[aburgh]

At the moment, there isn't a way to have the app respond differently for specific volumes. It is one of my top feature TODOs, but I haven't spent time on it lately. With respect to the boot volume, even if you have Disk Arbitrator (DA) auto-launched, it isn't launched until well after the system has booted, so it cannot have any affect on the boot volume. Its usefulness is for flash drives, external drives, and other media attached or inserted during normal use.

"Attach" is for disk images. When you double-click a disk image, it is first attached, then it is mounted. Attaching creates virtual disk object in the kernel and corresponding /dev/disk entries, which is analogous to plugging in a flash drive or external hard drive. The app was conceived as a forensic tool, where there is a need to control the mounting process (either blocking it or ensuring the volume is read-only). The primary reason DA has the attach feature is due to a side effect of blocking mounts. If you double-click a disk image, the system attaches it, then tries to mount it, and DA blocks the mount. Since the mount was unsuccessful, the system detaches the disk image with no option to leave it attached and unmounted. DA's attach feature was added to bypass this side effect.

[ghost]

Thank you

[kainjow]

Question appears answered, closing.