View Single Post
Old 06-22-2024, 08:20 PM   #5
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,741
Karma: 30237526
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by Quoth View Post
ext32? Do you mean exFAT? The older MS non-NT is FAT32 (win9x).

Anyway: NT (Windows) needs NTFS. Linux ext4, Apple which ever FS the installed MacOS is using.

exFAT and FAT32 are only useful to copy between different OSes.

Also I'd reformat any new drive to avoid supply chain malware, shovel-ware and ensure the file system matchs the OS in use if it's not for "sneaker net" use.


Yes, it should be NTFS for your OS and application.
↑ ↑ ↑ ✔

Calibre will use hardlinks (inode copies) & delete for mainstream operations involving folder/file moves on native filesystems… which is fast.

Because FAT devices don't support hardlinks calibre has to use file/folder copy & delete… which is slow. I don't know what calibre does on exFAT… not even sure exFAT even supports hardlinks.

I know exFAT doesn't support symbolic links… which I do make use of, including in the the context of calibre.

I would use NTFS.

BR
BetterRed is offline   Reply With Quote