Re: Mounting a sparse bundle as read only?
On 29 Mar 2015, at 13:05 , Matt Penna matthew.pe...@gmail.com wrote: Is there a need to mount the sparse image at all? If the contents within the image have not changed, then the image file should (I think) remain unchanged, as well, and thus Time Machine will not back it up unless/until it changes. It will be backed up initially, but will always be ignored for each subsequent backup. Is this not adequate for what you need? Or simply lock the dmg file. -- Noble dragons don't have friends. The nearest they can get to the idea is an enemy who is still alive. --Guards! Guards! ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Mounting a sparse bundle as read only?
On 2015-03-28, at 12:36 AM, @lbutlr krem...@kreme.com wrote: On Mar 27, 2015, at 21:33, Michael keybou...@gmail.com wrote: Is there a way to mount a sparse bundle as read only? keybounceMBP:~ michael$ mount -o ro /dev/disk3s2 mount: /dev/disk3s2: unknown special file or file system. keybounceMBP:~ michael$ mount -o ro /Volumes/Isolated\ old\ stuff/ mount: /Volumes/Isolated old stuff/: unknown special file or file system. keybounceMBP:~ michael$ Unmount the image first, then hdiutil attach -readonly /path/to/image.dmg (I think that’s right, double check the man page, it’s been a while since I used hdiutil_ So what works is simply disk=0s5; diskutil umount disk$disk ; diskutil mount readOnly disk$disk Then, changing that first bit (with ^5^6, or ^0s5^2s2) lets you apply that read-only to any partition that you don't want updated. Good? No. Every read-only partition gets a deep scan on every backup. I even made sure it was read-write, backup could complete successfully, and then read-only. Still gets deep scans. The good news: Now I know how to force a deep scan. The bad news: I don't know how to have a read-only archive that does not need to be updated (I don't want it to be updated) and still just backup is a no-op because it is read-only and not changing. -- All I know is that using the strap makes me feel like a hot woman in sunglasses. :-) ~jeffcarlson ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk --- Entertaining minecraft videos http://YouTube.com/keybounce ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Mounting a sparse bundle as read only?
Maybe I’m misunderstanding the big picture here, but Time Machine allows you to specify files and volumes that are not to be backed up; and, although I’ve never tried it, I would try setting discretionary read-only permissions on the bundle and/or the interior volume to prevent any accidental modification of the contents. On Mar 29, 2015, at 6:57 AM, Michael keybou...@gmail.com wrote: On 2015-03-28, at 12:36 AM, @lbutlr krem...@kreme.com wrote: On Mar 27, 2015, at 21:33, Michael keybou...@gmail.com wrote: Is there a way to mount a sparse bundle as read only? keybounceMBP:~ michael$ mount -o ro /dev/disk3s2 mount: /dev/disk3s2: unknown special file or file system. keybounceMBP:~ michael$ mount -o ro /Volumes/Isolated\ old\ stuff/ mount: /Volumes/Isolated old stuff/: unknown special file or file system. keybounceMBP:~ michael$ Unmount the image first, then hdiutil attach -readonly /path/to/image.dmg (I think that’s right, double check the man page, it’s been a while since I used hdiutil_ So what works is simply disk=0s5; diskutil umount disk$disk ; diskutil mount readOnly disk$disk Then, changing that first bit (with ^5^6, or ^0s5^2s2) lets you apply that read-only to any partition that you don't want updated. Good? No. Every read-only partition gets a deep scan on every backup. I even made sure it was read-write, backup could complete successfully, and then read-only. Still gets deep scans. The good news: Now I know how to force a deep scan. The bad news: I don't know how to have a read-only archive that does not need to be updated (I don't want it to be updated) and still just backup is a no-op because it is read-only and not changing. -- All I know is that using the strap makes me feel like a hot woman in sunglasses. :-) ~jeffcarlson ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk --- Entertaining minecraft videos http://YouTube.com/keybounce ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Mounting a sparse bundle as read only?
On 2015-03-29, at 7:07 AM, Macs R We macs...@macsrwe.com wrote: Maybe I’m misunderstanding the big picture here, but Time Machine allows you to specify files and volumes that are not to be backed up; and, although I’ve never tried it, I would try setting discretionary read-only permissions on the bundle and/or the interior volume to prevent any accidental modification of the contents. The big picture, roughly: I have some partitions that are historical data. I don't want them to ever change. But I do want them in the backup. Attempting to mount those partitions as read only, to prevent them from changing, messes up Time Machine's ability to just say these have not changed. On Mar 29, 2015, at 6:57 AM, Michael keybou...@gmail.com wrote: On 2015-03-28, at 12:36 AM, @lbutlr krem...@kreme.com wrote: On Mar 27, 2015, at 21:33, Michael keybou...@gmail.com wrote: Is there a way to mount a sparse bundle as read only? keybounceMBP:~ michael$ mount -o ro /dev/disk3s2 mount: /dev/disk3s2: unknown special file or file system. keybounceMBP:~ michael$ mount -o ro /Volumes/Isolated\ old\ stuff/ mount: /Volumes/Isolated old stuff/: unknown special file or file system. keybounceMBP:~ michael$ Unmount the image first, then hdiutil attach -readonly /path/to/image.dmg (I think that’s right, double check the man page, it’s been a while since I used hdiutil_ So what works is simply disk=0s5; diskutil umount disk$disk ; diskutil mount readOnly disk$disk Then, changing that first bit (with ^5^6, or ^0s5^2s2) lets you apply that read-only to any partition that you don't want updated. Good? No. Every read-only partition gets a deep scan on every backup. I even made sure it was read-write, backup could complete successfully, and then read-only. Still gets deep scans. The good news: Now I know how to force a deep scan. The bad news: I don't know how to have a read-only archive that does not need to be updated (I don't want it to be updated) and still just backup is a no-op because it is read-only and not changing. -- All I know is that using the strap makes me feel like a hot woman in sunglasses. :-) ~jeffcarlson ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk --- Entertaining minecraft videos http://YouTube.com/keybounce ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk --- Entertaining minecraft videos http://YouTube.com/keybounce ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Mounting a sparse bundle as read only?
On Mar 29, 2015, at 1:55 PM, Michael keybou...@gmail.com wrote: On 2015-03-29, at 7:07 AM, Macs R We macs...@macsrwe.com wrote: Maybe I’m misunderstanding the big picture here, but Time Machine allows you to specify files and volumes that are not to be backed up; and, although I’ve never tried it, I would try setting discretionary read-only permissions on the bundle and/or the interior volume to prevent any accidental modification of the contents. The big picture, roughly: I have some partitions that are historical data. I don't want them to ever change. But I do want them in the backup. Attempting to mount those partitions as read only, to prevent them from changing, messes up Time Machine's ability to just say these have not changed. Is there a need to mount the sparse image at all? If the contents within the image have not changed, then the image file should (I think) remain unchanged, as well, and thus Time Machine will not back it up unless/until it changes. It will be backed up initially, but will always be ignored for each subsequent backup. Is this not adequate for what you need? Matt ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Mounting a sparse bundle as read only?
On Mar 27, 2015, at 21:33, Michael keybou...@gmail.com wrote: Is there a way to mount a sparse bundle as read only? keybounceMBP:~ michael$ mount -o ro /dev/disk3s2 mount: /dev/disk3s2: unknown special file or file system. keybounceMBP:~ michael$ mount -o ro /Volumes/Isolated\ old\ stuff/ mount: /Volumes/Isolated old stuff/: unknown special file or file system. keybounceMBP:~ michael$ Unmount the image first, then hdiutil attach -readonly /path/to/image.dmg (I think that’s right, double check the man page, it’s been a while since I used hdiutil_ -- All I know is that using the strap makes me feel like a hot woman in sunglasses. :-) ~jeffcarlson ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Mounting a sparse bundle as read only?
Is there a way to mount a sparse bundle as read only? keybounceMBP:~ michael$ mount -o ro /dev/disk3s2 mount: /dev/disk3s2: unknown special file or file system. keybounceMBP:~ michael$ mount -o ro /Volumes/Isolated\ old\ stuff/ mount: /Volumes/Isolated old stuff/: unknown special file or file system. keybounceMBP:~ michael$ --- Entertaining minecraft videos http://YouTube.com/keybounce ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
