Hi, 2012/4/24 Vladimir 'φ-coder/phcoder' Serbinenko <phco...@gmail.com>: > On 23.04.2012 18:03, Bean wrote: >> Hi, >> >> 2012/4/23 Vladimir 'φ-coder/phcoder' Serbinenko <phco...@gmail.com>: >>> Have you tried with ntfs-3g? >>> Also if the problem is with only one directory, it's better if it stays >>> the way it is. The only quirk associated with false assumption about >>> case-sensitivity is the need to reference the name in correct case which >>> should be done anyway. If you wrongly assume case insensitivity some >>> files may become inaccessible with is more serious. >>> OS may forbid some file names without it being FS limitation (conversely >>> OS may fail to enforce FS limitation like an old trick with ".." in the >>> root directory) >>> >> I did some testing and found more serious issue, it seems directories >> like Windows, Users has disappeared. I need more testing to find the >> problem. > "disappeared" as in "no longer visible in GRUB"? Do you have a way to > recreate. If so we could add it to (unreleased) FS tests.
Actually there is no problem. Windows 7 stores boot files in one partition and system files in another, so you won't find Windows directory in the boot partition. I constantly forget about it. BTW, I think i understand how this flag works. If the file is installed by Windows and not writable, it has a TrustedInstaller security descriptor and namespace is set to 0, for example C:\Windows\notepad.exe. If the file is modified, there is no TrustedInstaller descriptor and namespace is set to 1, such as C:\Windows\win.ini. It seems this flag is not used for unix namespace anymore. -- Best wishes Bean _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
