Ext4Fsd VS ntfs-3g

Whilst that's true out-of-the-box, there are several third-party drivers and apps to read Linux filesysrems in Windows, like WinBtrfs, Ext4Fsd, Paragon File Systems Link etc.

I found this for ext2,3,4 too, I have tested personally https://github.com/bobranten/Ext4Fsd

There's the once-well-known ext2fsd, but it has become abandonware for ~5 years, and it causes lots of trouble on newer Windows versions. Bo Branten took a fork of it and fixed some of its bugs two years ago, but he has yet to add any missing features like journaling or ACL.

by default only the filesystem isn't recognized, the partitions will still show up as a drive letter (except for partitions that are hidden by id or that windows can't recognize), though when you try to access them windows will of course ask you to format. if you install an unofficial kernel driver like winbtrfs or ext4fsd then the partition & filesystem can be fully recognized

In a pinch, you could use Ext4Fsd for windows at https://github.com/bobranten/Ext4Fsd

Maybe this? https://github.com/bobranten/Ext4Fsd

There actually is a way to run btrfs and ext4 on Windows, but I probably wouldn't recommend them as they likely won't have the same speed and stability as a natively supported file system format.

There is Ext4Fsd, but it's not very good.

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.