[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MirageOS-devel] Mirage-WWW porting status



I've been making good progress on porting Mirage/WWW to the 1.0 libraries. The 
main website now compiles with 1.0 and crunch, with this (now-merged) pull 
request:
https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up the old 
website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block device 
instead of the static crunch filesystem.  This required a few minor changes to 
libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally read/write 
FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: 
https://github.com/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; 
https://github.com/mirage/mirage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug somewhere in 
the FAT directory traversal, so the resulting website doesn't actually read the 
files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module too, and 
we'll have a pass-through to the filesystem to make it easier to develop code 
without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.