heres what i did on two different machines -
both had vanilla 2.6.23 kernels from kernel.org, running debian etch,
all updates.
first patched with truecrypt driver. second machne loaded with LUKS
and kernel crypto enabled.
both machines create 2GB encrypted file and mounted under a directory
after formatting with mkfs.vfat.
copy files, do diffs etc and test em. both are fine reading/writing
files to encrypted space, mount and unmount fine.
i then load the jdk on both and simple java read write file program.
works great.
then i do a new File("test.txt").exists() - test.txt doesnt actually exist.
truecrypt machine return false as expected. the linux kernel LUKS
crypto machine returns true.
also moved from 32 to 64 bits -- same result. tried with different
jdks from 1.4 to 1.6 latest. same result.i dont get it. and i dont even know how to begin to test it. is this a kernel bug ? app bug ? driver bug ? jdk bug ? vfat bug ? anyone help diagnose it ? -Z- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
