![]() |
how does Busybox remember file/directory name case?
If I try this:
touch foo mv foo foobar mv foobar Foo the file I end up with is foo, not Foo. How, or, more importantly, why does Busybox seem to remember the original capitalization for foo, and why does it impose it? |
Re: how does Busybox remember file/directory name case?
Are you doing this on the MyDocs partition?
That is a Windows FAT32-formatted partition (so that it can be exported to any computer you connect the device to) and does not support case-sensitivity. |
Re: how does Busybox remember file/directory name case?
@chill
Yes? I remember such weird behaviour on Windows using Win Explorer itself. But not on device using term/sh/busybox itself. |
Re: how does Busybox remember file/directory name case?
Just tried it.
Code:
~ $ touch foo |
Re: how does Busybox remember file/directory name case?
Just tried it again. And ...
... oops. Tested it on N9. And there everything works as it should (also on MyDocs). Will have to check on my N900 later ..... -- Yes, it is like chill said. On MyDocs on Fremantle case sensitivity acts weird. |
Re: how does Busybox remember file/directory name case?
Quote:
Code:
/media/mmc1 $ touch fOo |
Re: how does Busybox remember file/directory name case?
@Pichlo tested in /home/user represented by ~ in the terminal prompt for the location/folder. /media/mmc1 is also vfat formatted. You could evaluate the file systems with the command
Code:
mount |
Re: how does Busybox remember file/directory name case?
I tested both in /home/user and in /home/user/MyDocs. I only published the former as the latter matched chill's experience.
I suspect some kind of caching issue. I do not believe it is busybox's fault, I assume it has more to do with the kernel and its FAT/FAT32 support. My first guess would be that the FS somehow caches the names. It might be interesting to figure out if there is a timeout or another way to reset it. I tried very briefly cd to another folder and back before the last mv but it did not make a difference. I also tried closing and reopening the terminal and that did not make a difference either, confirming my suspicion that busybox is probably innocent. |
All times are GMT. The time now is 04:45. |
vBulletin® Version 3.8.8