j
: Next unread message k
: Previous unread message j a
: Jump to all threads
j l
: Jump to MailingList overview
On Oct 9, 2012, at 1:11 PM, Mark Cave-Ayland wrote:
On 09/10/12 03:31, Programmingkid wrote:
I'm not familiar with how file systems work, but maybe you can make sense of this output. This is what I see when I enabled the debug macro.
Hmmm. According to that, I'd guess that it's found a filesystem it recognises, but then when it repeats the same seek at found: then it fails the second time around?
I'm afraid you'll need to poke around a bit more/adding debugging DPRINTF statements to figure out exactly what's happening.
BTW you should try and keep on the list wherever possible, since there may be some people with Apple partition knowledge on there who could help out.
Ok. I will CC our info later to the list. We can find out the name of each partition, so can't we just select the partition that is named APPLE_HFS, or APPLE_HFSX?
On 09/10/12 19:04, Programmingkid wrote:
Ok. I will CC our info later to the list. We can find out the name of each partition, so can't we just select the partition that is named APPLE_HFS, or APPLE_HFSX?
Given that Apple have lots of partition types which can contain a variety of filesystems (see http://en.wikipedia.org/wiki/Apple_Partition_Map), I suspect it will be a combination of partition flags. Otherwise how would we know which partition to boot from if there were more than one HFS partition present?
ATB,
Mark.
On Oct 9, 2012, at 2:56 PM, Mark Cave-Ayland wrote:
On 09/10/12 19:04, Programmingkid wrote:
Ok. I will CC our info later to the list. We can find out the name of each partition, so can't we just select the partition that is named APPLE_HFS, or APPLE_HFSX?
Given that Apple have lots of partition types which can contain a variety of filesystems (see http://en.wikipedia.org/wiki/Apple_Partition_Map), I suspect it will be a combination of partition flags. Otherwise how would we know which partition to boot from if there were more than one HFS partition present?
ATB,
Mark.
Good point. I didn't think of that. Do you think the "boot" word might fail because of this problem? Or would specifying a partition allow it to work?
On 09/10/12 20:13, Programmingkid wrote:
Good point. I didn't think of that. Do you think the "boot" word might fail because of this problem? Or would specifying a partition allow it to work?
If you're passing a partition id into the boot command, i.e. boot cd:9 then that should be using exactly the same volume resolution mechanism as dir cd:9,. So it could be that either the argument passing from the boot word is not working, or something else further down the boot process is failing.
ATB,
Mark.