I've decided to remove some confusion from the HAMMER utility, and also remove some of the master id code from the filesystem, which was designed for multi-master mode but really added confusion to the whole master-slave setup since we don't support multi-master mode in this release. PFS's will now only be master or slave, there will be no master id (0-15) setting and there will not be a no-mirror mode. A single whole-mount master id or no-mirror mode can be ...

It should. But I guess one has to set the correct font manually first. Sascha -- http://yoyodyne.ath.cx

That will definitely confused NFS. kill -HUP wouldn't work in that case because mountd will still think that you didn't change any of the exports. -Matt

done. -- Robert Luciani Chalmers University of Technology, SWE Department of Computer Science and Engineering http://www.rluciani.com/rluciani@gmail.com.asc

Both of these are the same problem. Definitely a bug... I think it's just that I am not storing the correct value for the st_size field of the PFS softlink. PFS softlinks are special, HAMMER expands them in place to a full transaction id + PFS format. So the readlink() returns a string with a different size then stat shows in st_size. NFS is probably depending on st_size being correct. However there is a secondary issue here which you have to be aware of. ...

Hi. Do you have some known limitation(or bugs) related to NFS-exporting of HAMMER filesystem? I've been playing with /etc/exports so as I can upgrade my router to 2.0, and found something strange: - can't NFS-mount an exported directory inside a HAMMER filesystem, only root directory can be NFS-mounted (no errors from mountd though) - can't NFS-mount an exported pseudofs (Permission denied), or NFS-mount a pseudofs inside an exported HAMMER filesystem (again, no errors from ...

And if you're booting a 2.0 system, please test pkg_radd, too.

Perhaps the version should be part of the path: http://pkgbox.dragonflybsd.org/2.0/All/ -- Erik Wikström

I think we should hold off the release until packages are built and have propagated to all mirrors. This might take several days, though. Packages are large and connectivity is low. cheers simon

This message tells you that the required package could not be found in /usr/release/packages, and not that it is not installed. Do make installer fetch. Sascha -- http://yoyodyne.ath.cx

Only two of the package mirrors have even started to update, so it's going to be a few days until the new build updates, and then more days until all the files are copied out. pkgbox has a full set of packages - a good chunk of them are built on 1.13, so there will be a warning at install, but that's it. Building from source (which I think is somewhat more common with pkgsrc) is already an option in any case. I don't think there's a need to wait.