On Mon, 11 Oct 2004, Christian SIMON wrote: > > Hi all, > > Excuse me for this off-topic post. > I know this is not a place devoted for this kind of problems, but > after reading various mailing in MacOSX world for 3 years, > I am quite confident I will find here the more relevant answers, and above > all, I understand the langage used here. > > I have lost everything in my home directory on a PBG4, 10.2.8 > All other directories, including other users are unchanged. > > I guess that what happend is very close to what's is described in > http://docs.info.apple.com/article.html?artnum=107854 > > Some app (I think about a Palm sync soft I was precisely using when > things happened) has probably tried to create a new file with the name > my home directory had: /Users/simon . Without asking permission, since > I am the owner of it... and admin of the computer... Now, /Users/simon is > empty, both from Finder, and from Terminal with ls. > Only /Users/simon and previous users folders are visible > (no new stuff or renamed folder...) > > But df tells me files are still here. I hope this is true (still 82% > occupied). The laptop is now sleeping. I hope the situation is stable > (I hope df results are not because of a cache or buffer issue). > There is a system 'unlink' command, and I believe this can be used to remove directories as well as files. Most shell-level commands would not allow you to remove a directory without removing its contents, but perhaps this new utility that you've used was not so careful.
If the 'df' shows the files are still there, probably an 'fsck' of the drive would recover them. These files would end up in a 'lost+found' subdirectory of the mount point (probably / for you). Hopefully they'd all be in one directory, or perhaps only the files and directories in your home directory would be in lost+found, and you'd have to pick names for them. After moving appropriately, though, you'll be back to pre-incident status. Unfortunately 'fsck'ing root (/) is not always easy to do. The system will fsck it at boot if it thinks it's necessary, and it does tricky stuff like mounting it read-only (to get the 'fsck' exectable, etc.), then runs the 'fsck', and re-mounts read/write. I don't know how to do this by hand (if it's even possible). There may be a way to convince the system to do it at boot if it doens't otherwise think it has to, but I don't know how. The Disk Utility may have a way around this for the root partition, but I have not ever tried. All in all, if you can put your powerbook into firewire mode (command-T at power-up?) and connect it to another 10.2.8 system, a lot of this will be much easier. Good luck! Wayne ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
