Accessing ext4 partition with writable access without fstab entry
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Accessing ext4 partition with writable access without fstab entry
I have Slackware14 full install (KDE), updated and otherwise working well. I recently tried to access an "ext4" formatted data partition by clicking on it in the left side partition list of Dolphin file manager. Dolphin asked me for password and then opened the partition. However, the partition is opening in read-only mode and I cannot create or edit any files there. How can I solve this problem without adding any entry to fstab (i.e. how to configure so that it mounts with writable access if clicked in file manager)? Thanks for your help.
what partition do you want to access? your fstab only list root partition
I have clarified in my earlier posts that I am mounting the partition by clicking on it in the file manager Dolphin when I need to access it. I do not want to make any fstab entry since the slackware14 installation is on an external disk which I may move to another computer with different hard disk structure.
Following parts of file /usr/share/polkit-1/actions/org.freedesktop.udisks.policy deal with 'mount':
Code:
<action id="org.freedesktop.udisks.filesystem-mount">
<description>Mount a device</description>
<description xml:lang="da">Montér en enhed</description>
<message>Authentication is required to mount the device</message>
<message xml:lang="da">Autorisering er påkrævet for at montere et fil system</message>
<defaults>
<allow_any>no</allow_any>
<allow_inactive>no</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>
<action id="org.freedesktop.udisks.filesystem-mount-system-internal">
<description>Mount a system-internal device</description>
<description xml:lang="da">Montér en intern enhed</description>
<message>Authentication is required to mount the device</message>
<message xml:lang="da">Autorisering er påkrævet for at montere et fil system</message>
<defaults>
<allow_any>no</allow_any>
<allow_inactive>no</allow_inactive>
<allow_active>auth_admin_keep</allow_active>
</defaults>
</action>
In the filesystem-mount-system-internal part, should I change both 'no' to 'yes'?
When I look at the hack required to make a disk mountable by a user and I see all that XML junk, somehow I feel Linux lost the plot. I'd still go with the fstab method as it's far simpler and will survive an upgrade. When you upgrade to the next version of Slack are you going to remember this obscure method and ridiculous file path and name?
I copied /usr/share/polkit-1/actions/org.freedesktop.udisks.policy and udisks2.policy files from another installed distribution (where mounting was as needed) and it worked well. I know this is not the best solution but it works.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.