| Summary: | Files on read-only cdrom should automatically gain write permissions when copied to a user location with r/w permissions | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | klaus thorn <klaus> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | a.samirh78, guilhermeafortunado, kdelibs-bugs, nate, nicolasg |
| Priority: | NOR | Keywords: | junior-jobs, usability |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | RedHat Enterprise Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
klaus thorn
2004-08-10 18:04:14 UTC
well, if you copy a read only file from somewhere else, it's still read only even if you apply a mask I think he means "with the users umask INSTEAD OF with the permissions of the source file" we'll see how many think like you. As the cdrom files are really read only and the same happens on any operating system I know of, I think this is a wish I don't want you to change operating system standart procedure but enable ordinary users to overwrite their own files without calling for help.
There already is this cautious "File already exists" dialogue, so when they klick on "Overwrite" it should also override the missing write permission. Which it did not.
So maybe the topic of the bug report changed from cdrom-related to override permission settings. But nevertheless it seems like a bug to me since konqueror stops the intuitive flow of the working process without need (bad "Usability"). It's like a small crash from a user's point of view. I hope it becomes obvious when you try to not use all your knowlege about the operating system and file system.
And see my perspective: as an administrator I have no means of helping my users: I can't waste system ressources for looking whether they copied files from cds in the last minute again and again and start an automatism to set the write permissions.
Yes I can teach them about file permissions and how to change them with konqueror but it is far better if they need not to know it. ("You want to use a CD under KDE?! Oh man what an ambitious task. You should better first visit my Linux course.")
On Thursday 12 August 2004 00:00, klaus thorn wrote:
> ("You want to use a CD under KDE?! Oh man what an ambitious task. You should better first visit my Linux course.")
Windows sets the readonly flag on files copied from a CD-ROM too - at least it did when I last
tested it, which was probably Windows-95 or 98.
The rest of your mail has a point though. I agree that it would be nicer to
give write permissions to the user, but this requires detecting that we are
copying from a readonly filesystem (to differenciate with copying a confidential
file around), so it's not a very obvious problem to fix...
Looks like this needs extending get_mount_info in kio/global.cpp, which requires
different code for Linux, AIX and Solaris. So it's doable, but the timing is
bad (3.3 is about to go out). Let's come back to this in a few weeks.
I am not sure if we should implement this bug/wish. It is now nearly one year old and there is still not a single vote for it, not even a CC. Have a nice day! *** Bug 272096 has been marked as a duplicate of this bug. *** This is a bug. As I reported in the - marked as duplicate - bug 272096. It only happens for optical media ( if I copy from /usr, from /var , etc., I can write the copied file ). In the same system, Nautilus does not present this behavior, the command line utilities also do not and Windows certainly does not too. In fact, I only stumbled upon this problem because a - soon too be - former Windows user could not edit the pictures she copied from a dvd she owns. It baffled her because this is standard issue on Windows. So please, do not name this strange behavior as a wish, it is a bug and a very annoying one, that requires knowledge and one too many steps to accomplish a trivial thing. Is this still an issue? (I think in generl optical media usage has eroded over the years). Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |