Dear all,
ultimately, I would like to be able to put Digikam in a read-only mode, such that it is guaranteed, that my original files remain untouched. To single exception would be deleting files. I assume that raws (and jpgs, if no raws are taken in the first place) are only touched to write metadata to them, if configured so. I have configured to metadata to be read and written to XML sidecar only. Does this setting lead to untouched originals already? From a more general point of view, I would like to know if Digikam opens files r/w per se, or are files opened r/o and r/w is only used for operation which need these permission. Thanks, Wolfgang _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users signature.asc (836 bytes) Download Attachment |
wenn dir deine Bilder wichtig sind mach vorher ein Backup, echtes ro
gibt es nicht auf der Festplatte. Johannes Am 09.07.2015 22:32, schrieb Wolfgang Mader: > Dear all, > > ultimately, I would like to be able to put Digikam in a read-only mode, such > that it is guaranteed, that my original files remain untouched. To single > exception would be deleting files. > > I assume that raws (and jpgs, if no raws are taken in the first place) are > only touched to write metadata to them, if configured so. I have configured to > metadata to be read and written to XML sidecar only. Does this setting lead to > untouched originals already? > > From a more general point of view, I would like to know if Digikam opens files > r/w per se, or are files opened r/o and r/w is only used for operation which > need these permission. > > Thanks, > Wolfgang > > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Thursday 09 July 2015 22:51:53 Johannes Kapune wrote:
> wenn dir deine Bilder wichtig sind mach vorher ein Backup, echtes ro > gibt es nicht auf der Festplatte. > > Johannes Well, of course, there are backups, but still one can try to be careful with the working copy the data. > > Am 09.07.2015 22:32, schrieb Wolfgang Mader: > > Dear all, > > > > ultimately, I would like to be able to put Digikam in a read-only mode, > > such that it is guaranteed, that my original files remain untouched. To > > single exception would be deleting files. > > > > I assume that raws (and jpgs, if no raws are taken in the first place) are > > only touched to write metadata to them, if configured so. I have > > configured to metadata to be read and written to XML sidecar only. Does > > this setting lead to untouched originals already? > > > > From a more general point of view, I would like to know if Digikam opens > > files> > > r/w per se, or are files opened r/o and r/w is only used for operation > > which need these permission. > > > > Thanks, > > Wolfgang > > > > > > > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users signature.asc (836 bytes) Download Attachment |
In reply to this post by Wolfgang Mader
Am 09.07.2015 um 22:32 schrieb Wolfgang Mader:
> Dear all, > > ultimately, I would like to be able to put Digikam in a read-only mode, such > that it is guaranteed, that my original files remain untouched. To single > exception would be deleting files. I simply set all files to "read only" before I even even load them into digikam. cu Peter _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Thursday 09 July 2015 23:44:37 Peter Mc Donough wrote:
> Am 09.07.2015 um 22:32 schrieb Wolfgang Mader: > > Dear all, > > > > ultimately, I would like to be able to put Digikam in a read-only mode, > > such that it is guaranteed, that my original files remain untouched. To > > single exception would be deleting files. > > I simply set all files to "read only" before I even even load them into > digikam. > think I could work around this limitation. Best, Wolfgang > cu > Peter > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users signature.asc (836 bytes) Download Attachment |
Am 09.07.2015 um 23:48 schrieb Wolfgang Mader:
> On Thursday 09 July 2015 23:44:37 Peter Mc Donough wrote: >> Am 09.07.2015 um 22:32 schrieb Wolfgang Mader: >>> Dear all, >>> >>> ultimately, I would like to be able to put Digikam in a read-only mode, >>> such that it is guaranteed, that my original files remain untouched. To >>> single exception would be deleting files. >> >> I simply set all files to "read only" before I even even load them into >> digikam. >> > > Good idea. You loose the ability to remove and rename images, though. But I > think I could work around this limitation. Did you try? I can rename an -r--r--r-- with digikam and opensuse. I didn't try moving. cu Peter _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
If you can rename it, it's not really read-only is it?
Losing the ability to rename is not a loss if the goal is zero modifications. The original file name is part of the original raw image. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
May be considered a semantic question. In *nix (remembering we have users of Redmonds filesystems as well) the filename is in the directory (inode), not the file itself. So changing the name doesn't touch the file or its contents. Moving it to another filesystem is another matter altogether. Of more immediate concern to us here is that directory attributes allow you to not only rename but delete the file(s). You have the option on (some ?) Linux filesystems to make a file immutable - even root can't modify (or delete/rename) it if you do that .... ;-) A decent backup strategy might be easier to live with.
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hold on while I check what file system the camera uses ...
On Thu, Jul 9, 2015 at 7:24 PM, <[hidden email]> wrote: > May be considered a semantic question. > In *nix (remembering we have users of Redmonds filesystems as well) the > filename is in the directory (inode), not the file itself. So changing the > name doesn't touch the file or its contents. Moving it to another filesystem > is another matter altogether. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Am 10.07.2015 um 03:46 schrieb Alan Pater:
> Hold on while I check what file system the camera uses ... > It doesn't matter. Digikam runs on the computer, and that filesystem is the point. cu Peter _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by snark2004-first@yahoo.com.au
On Friday 10 July 2015 00:24:29 [hidden email] wrote:
> May be considered a semantic question.In *nix (remembering we have users of > Redmonds filesystems as well) the filename is in the directory (inode), not > the file itself. So changing the name doesn't touch the file or its > contents. Hmm, I would have guessed that renaming is not possible, but I tried it on ext4 and it works. Thanks for the explanation. You never stop learning. > Moving it to another filesystem is another matter altogether. Of > more immediate concern to us here is that directory attributes allow you to > not only rename but delete the file(s). You have the option on (some ?) > Linux filesystems to make a file immutable - even root can't modify (or > delete/rename) it if you do that .... ;-)A decent backup strategy might be > easier to live with. At last for me, the backup strategy is in place. Thanks for all the replies. Best, Wolfgang > > > > From: Alan Pater <[hidden email]> > To: digiKam - Home Manage your photographs as a professional with the power > of open source <[hidden email]> Sent: Friday, 10 July 2015, 9:02 > Subject: Re: [Digikam-users] Put Digikam in read-only mode > > If you can rename it, it's not really read-only is it? > > Losing the ability to rename is not a loss if the goal is zero > modifications. The original file name is part of the original raw > > > image. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users signature.asc (836 bytes) Download Attachment |
Free forum by Nabble | Edit this page |