Opened 11 years ago
Last modified 8 years ago
#10057 assigned enhancement
Better error message for copying to read-only folder
Reported by: | Kev | Owned by: | nobody |
---|---|---|---|
Priority: | low | Milestone: | Unscheduled |
Component: | Applications/Tracker | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
On hrev46164, I see that /boot/common/bin is now read-only. However, I was a bit confused at first when I tried to copy a file to it, because the error message implied it wasn't just the folder, but the whole volume: "You can't move or copy items to read-only volumes."
Change History (5)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Priority: | normal → low |
---|
Oh, I had no idea. Well, that makes sense. Thanks for the explanation :)
comment:3 by , 10 years ago
Platform: | x86 → All |
---|---|
Summary: | better error message for copying to read-only folder → Better error message for copying to read-only folder |
Type: | bug → enhancement |
Version: | R1/Package Management → R1/Development |
comment:4 by , 10 years ago
Milestone: | R1 → Unscheduled |
---|
Moving Tracker enhancement tickets out of R1 milestone -- Tracker's source code comes from BeOS R5, so it already has all the features it did on R5.
comment:5 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Note:
See TracTickets
for help on using tickets.
The error message is actually correct: /boot/system, /boot/common and /boot/home/config are now packagefs mount points, and the packagefs is a read-only filesystem. The only exception is certain folders such as /packages and /non-packaged which it allows to "shine through" from the underlying BFS. As such, when Tracker gets the copy error back from the OS, it is in fact told that a copy to a read-only FS was attempted, and not just a folder.
It'd take a bit of work to specially handle that in the case of a packagefs volume.