ChironFS 1.0RC5 Available for download

2 views
Skip to first unread message

Vuco

unread,
Sep 10, 2007, 12:15:11 AM9/10/07
to chironfs-news
This is the fifth release candidate of the Chiron FS code
base. There is no known bug right now. If you find any
bugs, please report them asap, with as many details as you
can: what you were doing, what you have installed in the
system, etc.

Major bug fixes included in ChironFS 1.0RC5 are:

o Fixed bug #3 reported at http://code.google.com/p/chironfs/issues/detail?id=3
it was a problem with mknod, which can't be called when using
sshfs. Instead
we open and close the file. Thanks to Alexandre Fernandes for
reporting this
bug.
o Fixed bug #4 reported at http://code.google.com/p/chironfs/issues/detail?id=4
there was a mismatch in readdir function when testing if the
replica is
disabled. I used the wrong index variable. Thanks to Alexandre
Fernandes for
reporting this bug.

Luis Otavio de Colla Furquim

Vuco

unread,
Sep 12, 2007, 1:43:16 AM9/12/07
to chironfs-news
Release Notes for ChironFS 1.0RC6
September 12, 2007

This is the sixth release candidate of the Chiron FS code base. There


is no known bug right now. If you find any bugs, please report them
asap, with as many details as you can: what you were doing, what you
have installed in the system, etc.

Major bug fixes included in ChironFS 1.0RC6 are:

* Fixed a bug with fsync reported both by Oleg Bartunov by e-mail
"(...) postgresql 8.2.4 doesn't works. initdb worked fine, but
starting fails (...) PANIC: could not fsync control file: No such file
or directory (...)" and by William Maddler "(...) I try to save a file
from Vim. (...) 'test' E667: Fsync failed (...) File seems to be saved
anyhow. I have no problems using nano or echoing to a file.". It was a
wrong return value of the function giving to the application a false
negative.

Changes

Since ChironFS 1.0RC5

* Fixed a bug with fsync reported both by Oleg Bartunov by e-mail
"(...) postgresql 8.2.4 doesn't works. initdb worked fine, but
starting fails (...) PANIC: could not fsync control file: No such file
or directory (...)" and by William Maddler "(...) I try to save a file
from Vim. (...) 'test' E667: Fsync failed (...) File seems to be saved
anyhow. I have no problems using nano or echoing to a file.". It was a
wrong return value of the function giving to the application a false
negative.

* Fixed bug #5 The man page wasn't being copied to the man
directory when installing from the source tarball. I needed to redo
all the autoconf/automake/autoheader stuff just to discover that I had
to put one line at Makefile.am. Anyway, I needed to change the .spec
file and my script to build all the packages too.

Reply all
Reply to author
Forward
0 new messages