However, there is absolutely no difficulty in getting NTFS write capability in MacOS - you install the ntfs-3g driver, more of which in a moment.Īs a point of information, OS X 10.6 does include NTFS read/write capability however, the write feature is disabled by default, and users who have enabled it have reported that it's buggy. If you choose hfs+ it *ought* to set this correctly for you but as the disc already has an ms-dos partition table, Disk Utility might get this wrong.Īpple have bigger priorities than developing NTFS write capability. If I remember correctly (in Ubuntu atm) there's an 'advanced' button in the partitioning section where you can choose from one of 3 or four partition table types. One more point - if you reformat the drive in the Mac Disk Utility for hfs+, make sure it gets the partition table right. :wink: You can change this in the Mac System Preferences later if you need. Disable caching = slow enable caching = not quite so slow. The only difficult bit is a question you get asked when installing ntfs-3g. Two packages to download, two packages to double-click on. Installing the ntfs-3g driver is really easy in MacOS. You'll get a completely unallocated disc - no partitions.ĭid you read through that thread I linked? I go into more details of one disadvantage with hfs+ - that of potential permissions problems when swapping files between Ubuntu and MacOS. One more question: Deleting the partition table will delete all data right? That's kind of something I wanted to avoid, but if it doesn't work otherwise it is a possibility. I posted a link for ntfs-3g in MacOS in post #6., and there's more discussion of the pros and cons of choosing a filesystem for read-write in both MacOS and Linux. Use an Apple OS to create an Apple filesystem. You could probably format it in Gparted if you create a new partition table of the correct sort first, but it's better to use a Mac. Ubuntu/Linux can read-write to the non-journalled version of hfs+, but can only read the journalled version. If you want a hfs+ filesystem read-write on both MacOS and Ubuntu, use the Mac Disk Utility and specify the non-journalled version of hfs+. An Apple filesystem on a Microsoft partition table: that's the misbegotten offspring of two versions of Satan! :-s :wink: Apple uses the (far superior) GUID partition table. The reason the hfs+ formatted drive, formatted in Gparted is unusable in MacOS is that you've got an MS-DOS partition table. However, there is absolutely no difficulty in getting NTFS write capability in MacOS - you install the ntfs-3g driver, more of which in a moment. Apple have bigger priorities than developing NTFS write capability. 99% of Mac users have no need of using NTFS so read-only is more than good enough. NTFS is the proprietary filesystem developed by Microsoft. Write changes with 'w' and everything should work. Start fdisk on the drive and change the partition label with the 't' command to 'af'. Since I have no clue about macs I don't know about any error messages that might have appeared in any log file. Now when I gave the drive back to my friend, she couldn't mount the new file system. The correct Id in fdisk should be af though. In gparted the later partition is shown to be hfs+. I resized the existing partition and added an hfs+ one.ĭisk /dev/sdb: 1000.2 GB, 1000204886016 bytesĢ55 heads, 63 sectors/track, 121601 cylinders What I read is that hfs+ is the current standard, so I installed hfsprogs to use it with gparted for partitioning. So she gave me the drive to format it to some mac file system. If my friends mounts it on her Mac she only has read access, which is sort of stupid. It's not free, but it is highly useful for a vast number of other purposes, so if you'd like to get the other features it provides, you can kill two birds with one app, as it were.I have an external harddrive that is formatted in ntfs. AppCleaner is free and gets the job done perfectly.Īlternatively, the automation app, Hazel, automatically finds related files when you delete an app and asks if you'd like to remove those as well. Since all these apps mainly do is hunt down these stray plist files, paying for an app like AppZapper is a little ridiculous. (Leaving them also preserves you application preferences if you later decide to reinstall the app.)Īpplications like AppCleaner are for purists who want to truly remove every last bit of an app when they uninstall it (nothing against purists, though - I fall in that camp). These are tiny text files and usually inconsequential if left behind when you remove an app. The only exception to that is plist files - essentially just application preferences. The vast majority of apps on the Mac are self-contained, which is why there's no built-in uninstall method in Mac OS X.
0 Comments
Leave a Reply. |