Puppy is supposed to be able to handle a 'zdrv.sfs' placed inside the initramfs, however I looked at the 'init' script and yes, there is a logic fault. The main 'puppy.sfs' gets loaded ok, but not the 'zdrv.sfs'.
If you used Woof to build a Puppy with only a main .sfs, no zdrv.sfs, then it would be ok.
Anyway, I have fixed the 'init' script, it should now load the zdrv.sfs.
Regarding id-strings appended to 'vmlinuz' and 'puppy.sfs' (or, if use a traditional name such as wary_094.sfs then id-string is not required), this is documented in earlier blog posts:
Steve also asked a question about how the init script determines the boot partition. There are (?) some unusual boot situations where you might not have 'vmlinuz' in the boot partition. Or what you want Puppy to think is the boot partition. I can't really think of such a situation off hand, but yes, any file named 'vmlinuz' with the id-string appended to the end (no carriage-return) would fool the init script into thinking that is the boot partition (and sub-directory).
Comments:Posted on 2 Nov 2010, 2:08 by happypuppy
Newest WebM decoder gains massive speedup - up to 40% faster (!)
WebM decoding gets much faster with the newest build from git:
Posted on 2 Nov 2010, 15:17 by steve p