Ok, so this one got me thinking - and maybe that's my problem.
Anyway, on both my CF and SD cards, I get the message "Operation not permitted", when trying to do an "ln -s". Did some searches and the only meaningful article I found was a post by gdog. Someone mentioned to him that vfat drives can't store or has limited store for permissions and such.
So, not knowing nearly enough about the internals, I guess I could buy that.
However, here's my question. I can "ln -s" to my hearts content when it involves any directories created by the OS itself. So for example, my QtPalmtop directory, Documents, etc etc on my SD or CF card. No problem, everything links just fine. I've even moved several of the more large binaries and libraries to my SD card and created links no problem.
However, I obviously can't, when it comes to directories I've created (using mkdir).
Ok, so now really the question: What does the OS do differently when these directories are created, that's done different from doing a(n) mkdir?
It seems odd (read unfare ), that the OS can create directories and files on my SD and/or CF card that allows perm changes and linking abilities and I can't.
So does anyone know what it's doing? Is there a way to do this from the command line? Almost seems like there's got to be a way if the OS can do it. Is there a list somewhere of what commands the busybox binary supports/is looking for? I'm thinking beyond the links created as defaults.
I _really_ don't want to have to move everything off of my SD or CF and reformat it for ext2. I just recently upgraded and have everything setup extremely well for what I want to/am doing and don't really want to hassle with that.
So.... there's obviously a way. Does anyone know the answer or possibly point me in a direction?
Many thanks.
- Michael
