so I'm satisfied with the simple "it depends" consensus perspective. There isn't enough room here for should/shouldn't reasons and debates about (in)visibility, et.al. Sure, OS X (and ever other OS) has capabilities that are abused and not being used advantageously enough. Oh, that And They Said the Mac Was Intuitive article about a guy deleting /usr thinking it was a duplicate of /Users just came to mind. ACLs would have been another possibility. But they shouldn't do that.I picked file (in)visibility as one example of how to make parts of the system less vulnerable to disruptive changes because Apple's happens to do it. Oh, and btw, everything is present in the OS to allow these apps to hide some files from the user if their developers wanted to. Look how easy it is to remove a Finder (Spotlight) comments by using UNIX commands instead of Finder to manage files. This topic suggests many questions/ideas to me than don't necessarily have quick and obvious answers/responses (if any), which probably makes it better for interactive forum discussion (given enough interest) than getting into it too deeply here.Įverything is present in the OS for these apps to behave correctly even if the user renames their files/folders: reference to these files/folders should be kept by the apps as aliases, not paths.If it were practical for all "these apps" to reference files/folders that way why isn't it being done? Seems to me one misbehaving app could spoil the party. rather than Finder or some other file manager.įor instance, would it be (un)reasonable for certain user files/folders to be (un)hidden from "file manager" interaction, similar to Apple's policy of select system files/folders being hidden from Finder by default (which highly irritates some people while others are blissfully oblivious to it)? I'm curious how you'd categorize (and handle, as much as possible) the general issue of someone understandably (and mistakenly) believing their data is irretrievably missing after they've unwittingly renamed any folders (or individual files, for that matter) primarily accessed and managed with specific apps like iTunes, iPhoto, Mail, etc. At worst it seems there'd only be possibility of some minor, obscure inconvenience to restricting that, not widespread negative side effects. This is a major (and inexcusable) bug in OS X.Whatever you want to call it, I can't think of any good reason why it should be possible for anyone to rename their own home folder while logged in normally. All was good again!īut what a bummer that this is possible! I wonder how many people had this happen and had to give up living. On the next reboot, she had a brand new user account, with all her stuff apparently gone! I helped her to put things back by simply renaming the new user folder (which appeared in her correct short user name) to '123,' then renaming the 'good' folder with her short user name and re-logging in. She must have inadvertently clicked the trackpad while typing on her MacBook, and overtyped the home folder name - which is indeed possible, without so much as a warning! I didn't realise this was possible, but it happened to a friend.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |