"François Revol" <revol@xxxxxxx> wrote: > I just got the FileMapDisk code to work in the bootloader. > This means it can find an specific image file in partitions, and use > it > in turn as a disk/partition to boot from. > The boot menu will show another entry for it. > It currently doesn't go far, as the kernel will not find the boot > partition because it doesn't have a driver for it. > Next steps are FAT and ISO9660 support to be able to use images from > them, getting them to give the block_runs of the file in question to > pass it as boot_item, and write an fmap driver that uses them to > access block_runs are BFS specific - I would think that whatever the file map needs would be a better solution (ie. off_t rather than allocation_group/start/length). > blocks directly on the underlying partition (reentering a filesystem > is > both inefficient and dangerous) as Be did with the fmap driver. How could that be dangerous? And the inefficiency just means one more layer which wouldn't be that bad (if it has to go there, it'll need to load stuff from a slow CD anyway). And then, I think an attribute layer for iso9660 would be the better solution for CD booting, at least, so that the user can see the files on the disk. The fs layering is already in place, all what's missing is an example implementation :-) Bye, Axel.