First, I zeroed completely the drive before creating the UDF filesystem with:
dd if=/dev/zero of=/dev/sdx bs=512
This is to avoid any leftover superblocks or other metadata which could confuse the operating systems' filesystem type detection (at least zeroing the first sector should be needed, to obliterate the partition table; the first few sectors are not used by UDF, and a leftover partition table could really confuse things). You could also use the count=1 switch on the dd command, in order to more-quickly zero just the first 512 bytes of the drive (where the MBR usually is located within), though this was not tested.
To create the file system, the command I used was:
mkudffs --media-type=hd --blocksize=512 /dev/sdx
mkudffs command will become available on Debian-based Linux distros (such as Ubuntu) after installing a udftools package:
sudo apt-get install udftools
The default blocksize for mkudffs is 2048, which is wrong for a USB flash drive (which uses 512-byte sectors). Since the block size is used to find the filesystem metadata, using a wrong block size can make it not be recognized as a UDF filesystem (since the anchor will not be where the filesystem driver is expecting). Note that the mkudffs man page is wrong; 512 is a valid value for the block size (and the code explicitly accepts it).
I also used the whole drive instead of a partition; this should be more compatible.
The result of my testing so far:
- Linux with the most recent kernel (2.6.31, from Ubuntu 9.10): works.
- Linux with an older kernel: needs the
bs=512 option to mount, because it incorrectly used 2048 instead of the device sector size (fixed in commit 1197e4d).
- Windows Vista: works.
- A brand-new Mac: works.
- Windows XP: can read fine, but gives "access denied" when trying to write; also seems to think the disk is full.
While I have not so far tried to create a file larger than 4G in it, I see no reason why it would not work.
Given that it worked perfectly on all recent operating systems (only having to mount manually on Linux, which will not be needed anymore as soon as Ubuntu 9.10 and Fedora 12 are out), and worked read-only in Windows XP (which was a surprise to me; I was expecting it to not recognize the filesystem at all), using UDF instead of FAT32 or NTFS in big USB flash drives seems a good idea.
Best Answer
Mac OS X's built-in support for NTFS is read-only. You can drag things off of that volume and onto other (non-NTFS) volumes on your Mac, but you can't delete things from that drive. I would think copy/paste would work, but not cut/paste.
There are third-party NTFS read/write solutions for Mac OS X if you need the ability to delete things off of NTFS volume.
If you need to create a volume (drive partition) that can be used equally well on both Mac OS X and Windows, go with FAT32. Windows can't even read the Mac's native HFS family of volume formats without third-party software.