freenode/#mezzano - IRC Chatlog
Search
13:20:19
fittestbits
froggey: I'm trying to setup a double boot system with Linux and Mezzano. I spent some time yesterday looking in to this.
13:20:58
fittestbits
My current plan is to use grub to boot linux and chain boot from grub to kboot to boot mezzano. Does that sound reasonable to you?
13:21:59
fittestbits
When I create a new mezzano image, I would just dd it into the mezzano partition - no need to rebuild the kboot partition.
13:24:37
fittestbits
Also, I was looking through the image-manip code - it seems to compress the image. Would this step still be required even if I have enough space image as generated by the Makefile?
13:30:05
froggey
kboot.bin is multiboot compliant, so it can be loaded directly using grub's multiboot command. no need for a separate kboot partition, though you can chainload if you want
13:31:11
froggey
and the flattening step is optional. it effectively defragments the image & reduces it to the smallest possible size. important for a live-cd, not so much for an installation
13:33:59
froggey
but the boot partition needs to have a filesystem kboot supports. only ext2/3/4 or fat, iirc
13:34:21
fittestbits
OK - and mezzano pages in place, right? So I want the mezzano partition to be large so that I have a large virtual memory?
13:36:08
froggey
the image size is taken from the partition. putting a 1GB image on a 4GB partition will do the right thing & use all 4GB, no need to update anything manually
13:36:53
fittestbits
Great - so I leave the configuration in the Makefile and build programs alone - just dd the image I create onto my partition.
13:38:00
froggey
you'll have to remove the old bootloader partitions from the image, but that's just a case of passing the appropriate start offset to dd
13:39:40
fittestbits
Oh, right, the mezzano.image file is a disk image with 3 partitions - I just want the mezzano image in partition #3.
13:40:42
froggey
partition 3 currently always starts at offset 4MB, whatever the size of tools/disk-header.bin is
13:44:59
fittestbits
Right - I noticed that the live-cd has a different layout - I guess because it's generated using mkisofs. BTW I ended up using xorrisofs instead of mkisofs because mkisofs is not installed on my machine and it wasn't available in the repositories I use. xorrisofs works just fine, too.