Puppy Linux Discussion Forum

Amaponian wrote: ↑Mon Aug 08, 2022 7:44 pm

Does NTFS go well with Linux? No problems with that?
Using NTSF would solve another problem I haven't said: Windows is totally blind with ext4 partitions, but many Linux users could prefer that. I also prefer that, but once it happened to me that Windows reported a partition as unallocated space and I formatted it... (big mistake).

So I think I'm going to take the NTSF recommendation but just for the common drive.

Thanks Mr. @wizard for all your help and wonderful recomendations.

Have you moved the post? If the common drive is where your Linux main file sytem resides I wouldn't do that. The NTFS-3G driver, which is still prevalent in puppy land, I think, is noticeably slower than ext4. It works but just more slowly.

step wrote: ↑Tue Aug 09, 2022 11:52 am

Have you moved the post?

No, I've just added a missing word to the title which may have changed its url.

step wrote: ↑Tue Aug 09, 2022 11:52 am

If the common drive is where your Linux main file sytem resides I wouldn't do that.

The common drive is the data drive, which currently is fat32.

step wrote: ↑Tue Aug 09, 2022 11:52 am

The NTFS-3G driver, which is still prevalent in puppy land, I think, is noticeably slower than ext4. It works but just more slowly.

That worries me a little. Is it slower than fat32?

Thanks for trying to help.

williwaw wrote: ↑Mon Aug 08, 2022 11:52 pm

Amaponian wrote: ↑Mon Aug 08, 2022 4:44 pm

ubuntu is installed in a ext4 partition. ext4 partition is not recognized by Windows so I cannot use it to put there a common data.

another way around could be to try something here https://itsubuntu.com/mount-linux-partitions-windows/

I would be inclined to use something like this only if the files were to be accessed by windows read only. some more research would be prudent before giving windows write access

Thank you for that useful information, but I don't really want Windows to have access to my Linux partitions, only to the common drive.

Burunduk wrote: ↑Mon Aug 08, 2022 7:59 pm

Another possible solution is to mount a drive in a way that allows the user spot to write to it. But this makes the whole drive accessible to spot.

• Use the blkid or lsblk -f command to find out the drive UUID (a label also can be used instead of UUID).

• Unmount the drive if it's already mounted

• Create a directory where you want your drive to be mounted. (For example, mkdir /mnt/my-drive)

• Run mount -o rw,uid=spot,gid=spot -t vfat UUID=xxxx-xxxx /mnt/my-drive to mount the drive. (Replace UUID=xxxx-xxxx with an actual id or use LABEL=my_data) After this any file or directory in the drive will "belong" to spot:spot (until you unmount it)

• The drive can be unmounted in a usual way by clicking the corner of its desktop icon.

You could put the command into a script:

Code: Select all

#!/bin/bash

drive_id=xxxx-xxxx
mount_dir=/mnt/my-data-drive

mkdir -p "$mount_dir"

mount -o rw,uid=spot,gid=spot -t vfat UUID="$drive_id" "$mount_dir"

or add a /etc/fstab entry.

Thank you. I'm going to test this, but, by now, I prefer to keep security on and keep using spot. Just adding a boot script that moves all files on spot to my common drive. That solution was proposed by Wizard here.