Someone wrote in [personal profile] mjg59,
mjg59: "For an HFS+ filesystem, the inode of the bootloader is written to a specific offset in the filesystem superblock and the firmware simply finds that inode and executes it. And this appears to be all that older Macs support." Not entirely true. On HFS+ inodes are actually special files in "\0\0\0\0HFS+ Private Data" (the joy of forcing non-POSIX filesystem into POSIX world). What's written in superblock is catalog node id and converting it to actual extents involves btree lookup, so I wouldn't say it's simple.



(Read 31 comments)

Post a comment in response:

From:
Anonymous
OpenID
Identity URL: 
User
Account name:
Password:
If you don't have an account you can create one now.
Subject:
HTML doesn't work in the subject.

Message:

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org


 
Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.