btrfs VS ntfs-3g

> I'd gladly throw my credit card at it

https://github.com/maharmstone/btrfs?tab=readme-ov-file#dona...

Can this be used? I knew ReactOS would use it natively.

https://github.com/maharmstone/btrfs

I loose out on BTRFS snapshotting and subvolumes then. And if you look at winbtrefs it’s more than a hobbiest project. It has quite active development progress constantly https://github.com/maharmstone/btrfs

I've installed the WinBtrfs driver on Windows, which supports read/write support for Btrfs partitions.

Install WinBTRFS so Windows can read the file BTRFS file system.

I don’t know if that tool allows to write but this GitHub page https://github.com/maharmstone/btrfs seems mature enough. I am still unsure to trust it because I could bork my SSD and files

https://github.com/maharmstone/btrfs scroll down to mappings and that *should help with sharing things between both OSes.

I have also found this repository (https://github.com/tuxera/ntfs-3g) which seems to be a fork of the NTFS-3G repository from Tuxera (https://github.com/tuxera/ntfs-3g) but it doesn't provide any instructions on how to install NTFS-3G on Bliss OS without compiling it yourself from what I understand.

Can you access any folders on your Windows drive? If not, you could maybe try reinstalling ntfs-3g. I believe this is responsible reading from/writing to nfts partitions. It should be installed on most modern distros, but maybe it's not installed on yours.

So if you like ntfs transparent file compression, ensure you have ntfs-3g installed. Make an ntfs partition with folders, set the compression flag on the folder of your choice per these notes https://github.com/tuxera/ntfs-3g/wiki/Using-Transparently-Compressed-Files write your logs you wanted to compress to it and it is a compressed folder.

pigeon@pigeon:~$ ntfs-3g ntfs-3g: No device is specified. ntfs-3g 2022.5.17 integrated FUSE 28 - Third Generation NTFS Driver Configuration type 7, XATTRS are on, POSIX ACLS are on Copyright (C) 2005-2007 Yura Pakhuchiy Copyright (C) 2006-2009 Szabolcs Szakacsits Copyright (C) 2007-2021 Jean-Pierre Andre Copyright (C) 2009-2020 Erik Larsson Usage: ntfs-3g [-o option[,...]] Options: ro (read-only mount), windows_names, uid=, gid=, umask=, fmask=, dmask=, streams_interface=. Please see the details in the manual (type: man ntfs-3g). Example: ntfs-3g /dev/sda1 /mnt/windows Plugin path: /usr/lib/x86_64-linux-gnu/ntfs-3g News, support and information: https://github.com/tuxera/ntfs-3g/

For more info, here is their wiki https://github.com/tuxera/ntfs-3g/wiki

You should typically have no issue reading from the NTFS disk with a Mac but writing to is a separate matter. The driver you were using may not be compatible with Ventura. Here are a couple paid options: Paragon NTFS, along with NTFS for Mac. There are also a couple open-source options with limited support but should be otherwise functional: NTFS-3G or macFUSE.

You need ntfs-3g to read/write a NTFS drive. It shouldn't corrupt your data no matter what but may create some Linux-only files which may prevent the Windows machine from booting up. Idk how Windows 7 handle this. Windows 10 should ignore them though.

If it's on their repositories, that would be easy. If not, you could compile from source.

Unprivileged user can not mount NTFS block devices using the external FUSE library. Either mount the volume as root, or rebuild NTFS-3G with integrated FUSE support and make it setuid root. Please see more information at https://github.com/tuxera/ntfs-3g/wiki/NTFS-3G-FAQ

https://github.com/tuxera/ntfs-3g probably it's the only way to get a read/write permission for NTFS drivers.