Cannot change permissions by remount of NTFS?

[miltonx]

This question arises after I tried the pfix=nocopy boot option.

My frugal install is on an NTFS partition (sda2), and after booting puppy, sda2 is still mounted at /initrd/mnt/dev_save and cannot be unmounted because of the "pfix=nocopy" option. Since all my working documents are also located in sda2, I tried to click an HTML file from there, and the problem is that chrome is running as spot and cannot access the HTML files on sda2. (I do not want to run chrome as root user, since running it as spot has been a long time practice in puppy world.)

Code: Select all

root@live:~# findmnt /dev/sda2
TARGET    SOURCE    FSTYPE  OPTIONS
/mnt/sda2 /dev/sda2 fuseblk rw,noatime,user_id=0,group_id=0,default_permissions,blksize=4096
root@live:~# 

The above command shows that the NTFS partition was mounted with the "default_permissions" option, which makes it unaccessible by spot user.

Since sda2 cannot be unmounted, is there any way to use the "mount -o remount,..." command to make this partition accessible to spot user? I tried "mount -o remount,alllow_other /dev/sda2 /initrd/mnt/dev_save". Does not work.

[Wiz57]

Spot is restricted to accessing only files in its own directory. What I do is copy anything I want to access via say chromium running as spot is
copy the file to the Spot directory. You can make seperate diectories under spot for different file types. I normally run Palemoon as my
default browser...so to "sync" bookmarks I export my Palemoon bookmarks to HTML, then use my file manager (PCManFM or Rox) to copy
that HTML file to the Spot directory. Then I can "import" the HTML file into chromium. As for files stored on my NTFS partition I do the same.
Wiz

[mistfire]

You are using ntfs-3g. Try swap the kernel with newer kernel with NTFS3 kernel module support. and mount it using "-t ntfs3" parameter

[miltonx]

You are using ntfs-3g. Try swap the kernel with newer kernel with NTFS3 kernel module support. and mount it using "-t ntfs3" parameter

I tried the latest puppyBookworm64 10.0.7 and the ntfs is still on ntfs-3g after booting, although its kernel DOES support ntfs3. I unpacked the iso's initrd.gz, read the init file and confrimed that the ntfs partition was mounted by ntfs-3g during intrd stage. Looks like the WOOF-CE maintainers could upgrade their build script to apply ntfs3.

Anyway, your comment is very helpful in that I found ntfs3 to be more updated, faster, and capable of mounting one ntfs partition to multiple points.

[mistfire]

You are using ntfs-3g. Try swap the kernel with newer kernel with NTFS3 kernel module support. and mount it using "-t ntfs3" parameter

I tried the latest puppyBookworm64 10.0.7 and the ntfs is still on ntfs-3g after booting, although its kernel DOES support ntfs3. I unpacked the iso's initrd.gz, read the init file and confrimed that the ntfs partition was mounted by ntfs-3g during intrd stage. Looks like the WOOF-CE maintainers could upgrade their build script to apply ntfs3.

Anyway, your comment is very helpful in that I found ntfs3 to be more updated, faster, and capable of mounting one ntfs partition to multiple points.

Actually, there is are pull requests on woof-ce about adding NTFS3 support but still not merged to main tree. I wonder if there is other Puppy derivatives or remasters aside from QuickPup64 and ManjaroPup64 that has builtin NTFS3 support right from the initrd to main puppy sfs