You are not logged in.
Hallo,
I have divided my hard disk into 4 partitions
1st one is root directory
2nd one is where I store my data
Now I mount this disk with fstab: UUID=7DF8-380C /mnt/storage exfat async,suid,gid=1003,umask=007
I belong to the group externalstorage
So I can actually do everything.
premisson:
drwxrwx--- 1 root externalstorage 131072 Jan 1 1970 storage/
when i:
git clone https://github.com/helix-editor/helix.gitCloning into 'helix'...
error: chmod on /mnt/storage/tools/file_editter/helix/.git/config.lock failed: Operation not permitted
fatal: could not set 'core.filemode' to 'false'
thanks, if someone can tell me how to solve it
Last edited by testware (2024-11-09 19:40:58)
Offline
exfat does not support linux permissions.
Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.
Offline
Ok, but how can this information help me?
Do you have any idea how I can install it with git clone?
I have the permissions according to ls when I enter ls.
Last edited by testware (2024-11-09 12:37:23)
Offline
Do it somewhere else like your home directory, which I presume is a linux-friendly file system (ext3/4, btrfs, etc).
Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.
Offline
So ls does not show me the correct file permissions?
How can I see the correct permissions?
edit:
it confuses me, I can read, created, execute files only with git clone it does not work
and cargo build does not work either
Last edited by testware (2024-11-09 12:53:06)
Offline
error: chmod on /mnt/storage/tools/file_editter/helix/.git/config.lock failed: Operation not permitted
fatal: could not set 'core.filemode' to 'false'
chmod can't operate on exfat filesystems and cargo build is likely to face similar issues.
You'll have to choose another filesystem for the data partition.
Last edited by Lone_Wolf (2024-11-09 14:36:12)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
format your exfat fs to ext4 or ext3 or brtfs etc,it won't work on exfat
std::cout << "I use Arch BTW" << endl;
Offline
Ok, I understand that it won't work on exfat.
But I expected you to explain to me why it doesn't work and maybe there are ways around it, and not just say for the third time that it doesn't work.
format your exfat fs to ext4 or ext3 or brtfs etc,it won't work on exfat
My main file system is ext4.
I want to keep my exFAT because it seems to be compatible with everything without any problems.
Last edited by testware (2024-11-09 18:57:30)
Offline
I want to keep my exFAT because it seems to be compatible with everything without any problems.
Except git
The problem is git depends upon the ability to set and read permissions. exFAT has no concept of permissions.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
You can try to run your clone with filemode set to false so permissions are not trusted:
git -c core.fileMode=false clone ...
cd ...
git config core.fileMode false
Even if that works, there may be other applications that will have problems.
Last edited by progandy (2024-11-09 19:36:03)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Everyone is repeatedly telling you what the problem is, you just don't want to hear it…
So here's some details you probably don't understand:
exFAT is FAT. It's not even a real filesystem let alone a posix one.
https://en.wikipedia.org/wiki/File_Allocation_Table
https://man.archlinux.org/man/core/man-pages/chmod.2.en and https://man.archlinux.org/man/chown.2.en will fail w/ an error and that error stops everything that checks for it.
Würg-a-rounds:
--------------------
Since we recently had this, you can use https://aur.archlinux.org/packages/bindfs to hide the errors, https://bindfs.org/docs/bindfs.1.html#sect5
This is however dumb. There're more limitations to FAT than just the permissions, you eg. also don't get sym- or hardlinks
=> Use a real filesystem.
In doubt create an image file and add an ext4 filesystem there that you can then mount as loop device.
https://wiki.archlinux.org/title/Sparse_file
Edit:
Even if that works, there may be other applications that will have problems.
and cargo build does not work either
Last edited by seth (2024-11-09 19:40:07)
Offline
You can try to run your clone with filemode set to false so permissions are not trusted:
git -c core.fileMode=false clone ... cd ... git config core.fileMode false
It looks as though the chmod on config.lock is unconditional https://github.com/git/git/blob/v2.47.0/config.c#L3339
Offline
If you mount the FS with the UID of your user set, then chmod might not return an error, but I have not tested that.
https://man.archlinux.org/man/core/man- … 2.en#EPERM
EPERM The effective UID does not match the owner of the file,
and the process is not privileged (Linux: it does not have
the CAP_FOWNER capability).
Last edited by progandy (2024-11-09 19:48:58)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline