Access Permissions issues (+Causing conflicts with AbiWord, partition access and more)

SliTaz Forum » English Support » Packages

Access Permissions issues (+Causing conflicts with AbiWord, partition access and more)

(5 posts) (3 voices)

Started 1 year ago by actua11
Latest reply from Filou
This topic is not resolved

Tags:

No tags yet.

actua11

offline
Member

Forgive this confused question but I'll be as short as I can..

Basically .. Is there a way to give full folder access to a user, similar to root access?

---

So for my issue, My thought is to right click a folder /properties/permissions, and change access to 'anyone'... and while the dialog box shows it is changing the permissions, they do not actually apply.. even when logged in as root.

As a result of this, access to my other partitions to change content on sda2, sda3.. is limited to root access.

Also, there seems to be an (unrelated?) issue with some programs, such as with abiword, where .docx files are corrupted on open as user (tux) but.. open fine when logged in as root. This occurs when the file is on another partition or saved locally at tux/home/desktop for example.

I can't think what access conflict could be interfering specially with .docx, but not .doc files, but as with the folder/partition access issue, opening up full access to the 'user' could be a quick fix.. just I can't seem to make the access changes 'stick'.

I can just login as root now as needed, but any help to solve any of this would be greatly appreciated

Posted 1 year ago #
gibor

offline
Moderator

You can change the permissions from the command line:
userid and groupid /path/of/folder
on terminal as root then
chown -R user:group path/of/folder

Posted 1 year ago #
actua11

offline
Member

Thank you for the reply gibor, it is very much appriciated.

Sadly this did not help to solve the issues, but I have looked further

So I have 3 further partitions sda2(Android-x86)..sda3(Windows7) and sda5(Extended FAT32 partition). For sda2/3, things work perfectly, it is just the FAT32 sda4 causing issues (I tried reformat to ext4 just in case, but it did not help)

For these partitions I am auto-mounting on boot using local.sh ... however when I remove sda5 from this, and instead mount by clicking on it in the PCManFM gui ...it works perfectly. sda2/3 work fine by local.sh.....but sda4, somehow does not. I can't figure why?

Also for AbiWord ..it seems plugins are only loaded when logged in as root. I have tried to change permissions on the plugins/plugin directory, and anything related to the AbiWord install, but.. no success. Perhaps it is a bug in AbiWord itself?

(Logging in as root is a temporary fix for all this, though, when logged in as root, so applications such as Gens/GS don't allow use when logged in as root ... is there maybe a way to bypass an application checking what user is logged in, or is this hardcoded to application itself?

Posted 1 year ago #
gibor

offline
Moderator

Fat/ntfs partitions do not have user permissions. It is assigned to them by the mount operation (udev rules).

You could try running the partition mount in autostart session with sudo. Maybe it retains user rights instead of root as local.sh.

Other important thing check the permissions of the mount point, and if needed, unmount it and change them from the command line.
Udev creates it automatically with its own rules, while in your case, it seems to be done manually.

Posted 1 year ago #
Filou

offline
Moderator

Especially concerning the mounting of partitions, the permissions are only one aspect, but often not the decisive ones...

Maybe you should have a look at the following topics, depending on how you want the partitions to be mounted:

1.) /etc/fstab contains information about the partitions to be mounted at Boot time as well as permissions (google for fstab or man fstab for further information)
2.) /etc/udev/rules.d defines how pluggable media will be handled. You may influence permission rules within udev.
3.) if you intend to automatically mount and unmount partitions only when needed, the 'automount' capabilities provided by the kernel with rules in /etc/auto.master and others could be helpful.

I suggest you try to get a deeper understanding of those in order to address your issue as best fitting to your needs...

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.