On Fri, Sep 21, 2007 at 06:23:07PM +1200, Avinash Malik wrote:
> Quoting Bill Stouder-Studenmund <wrstuden@xxxxxxxxxx>:
> > It's not really "fs_commit". It's "journal format commit" where the
> > journal formats are closely related to specific other fs implementations.
> > We won't really have an "ext3fs_commit" but we will have a "jbd_commit"
> > for a journal that is layed out how ext3fs/jbd expect.
> Just to make my understanding clear before I get into coding it, this is what
> understand from the above statement:
> The commit functionality will still be implemented as a function in the
> file-system, and there will be host of commit functions one for each
> Journal-type, depending upon how many journaling type each file-system wants
> support. The ufs_trans_attr structure containing the gj_commit function
> will point to the appropriate journal commit function (which is implemented in
> the file-system) and this gets initialized as it is being done right now
Don't worry about where exatly the commit function is implemented. Chances
are it won't actually be in the file system itself, but it will be in a
library. The important thing is that the file system(s) will know how to
In fact it will most likely be in a library as multiple file systems may
want the same journal routine, and we'll only have one version of it. As
Adam noted, multiple Linux file systems use jbd, so they'll all want to
> I don't know if this is the right place to ask this question but, normally I
> Freebsd and I installed NETBSD-3.1 to start-coding, everything went normally
> until it came to networking when I dhclient rtk0, I get an IP but no netmask
> all it remain at 0xfff..000. It is a real hassel using freebsd to import the
> packages on disk and then booting into NETBSD to start coding. Any help with
> regards to this is appreciated. I tried static IPing the interface, it does
> same thing, command "ifconfig rtk0 down ; ifconfig rtk0 10.1.1.4 netmask
> 255.0.0.0" goes through but netmask does not get assigned at all remains same
> to 0xff..000.
Get one of the NetBSD 4.0 release candidate builds. Then start following
current and look at switching to it (-current can be rough at times when
there is temporary breakage). The journaling will make it into 5.0 at the
earliest, and the kernel is VERY different from 4.0 and exceptionally
different from 3.X.