freenode/#mezzano - IRC Chatlog
Search
17:07:15
fittestbits
froggey - I'd like to add a disk partition to use as a file system. I see how the current image is put together - 2 boot partitions and the lisp system partition.
17:09:14
fittestbits
Before or after the lisp partition? After would require a change to the cold-generator.lisp to write the partition info.
17:10:01
fittestbits
And, I guess a change to copy the file partition onto the image after the lisp system is written.
17:10:40
fittestbits
If I put it before the lisp partition (make the lisp partition #4 instead of #3), then the copy of the file partition would be handled like the boot partitions.
17:11:33
fittestbits
So, the only change to cold-generator.lisp, would be the partition table offset for writing the size/end of the lisp partition.
17:12:38
fittestbits
ebrasca - I've been working on a "tagged" filesystem and it's reaching a point where I'd like to try writing to a real partition instead a memory array.
17:13:28
fittestbits
I'm not exactly sure how you would hook up your fat32 code to the partition though.
17:14:58
fittestbits
One of the things I've started thinking about is bootstrapping the file system vs mounting an existing file system, and how to preserve the contents across lisp system rebuilds.
17:17:23
fittestbits
By hdb do you mean a second drive on the VM as opposed to an additional partition on hda?
17:21:32
fittestbits
Thanks, I'll take a look at your fat32 code - maybe that's a better way to start. Eventually, I'd like to run mezzano on bare metal which will require multiple partitions ...
18:07:15
froggey
I think adding a second disk drive like ebrasca suggests would be the best approach
18:08:29
froggey
the current disk image format is only designed for running in a vm, for installing on real hardware you'd want to do the partitioning & bootloader install yourself
18:09:21
froggey
the cold generator can produce a bare lisp image suitable for copying onto an existing partition
18:31:49
fittestbits
froggey - I see. Thanks. So on bare HW, the approach would be to generate just a lisp image and copy that onto the disk in the appropriate place leaving the other partitions unchanged.
18:53:07
froggey
it's a dump of memory, but not linear. there's a table that maps from virtual addresses to disk blocks
21:46:53
fittestbits
ebrasca - were you using the whole disk as the fat32 file system instead of using just a partition?
22:20:44
froggey
fittestbits: I don't know what ebrasca did, but raw disks & partitions are both exposed in the same way through the disk api