On Mon, Oct 21, 2013 at 4:36 PM, Matthew Ahrens <[email protected]> wrote: > On Mon, Oct 21, 2013 at 11:19 AM, Raphael S Carvalho > <[email protected]> wrote: >> >> On Mon, Oct 21, 2013 at 1:56 PM, Matthew Ahrens <[email protected]> >> wrote: >> > On Sun, Oct 20, 2013 at 11:58 PM, Raphael S Carvalho >> > <[email protected]> wrote: >> >> >> >> I send the below mail to Brian Behlendorf, but everyone is welcome to >> >> help >> >> me =) >> >> I will write a read-only ZFS driver, and I'm looking for a >> >> specification that focus on the on-disk structure of a ZFS partition. >> > >> > >> > There's a link to the (outdated) ZFS on disk spec on the OpenZFS >> > website: >> > http://www.open-zfs.org/wiki/Developer_resources >> > >> > What platform will you write your read-only driver for? >> >> x86 > > > I guess I meant what operating system? What I was trying to get at is: why > are you writing a read-only ZFS, rather than using one of the existing > ports, or porting the existing code? It's great that you are, I'm just > curious what the use case is. > > --matt
Ah ok, sorry. My platform is Linux, and ZFS on Linux seems to be the right place to get started. The read-only driver is for Syslinux, by the way, it's a bootloader and its VFS layer has some peculiarities. Yes, I could port existing code, but by writing it myself, I would gain experience and learn more about the on-disk structure of ZFS. Regards, Raphael S. Carvalho _______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
