Re: FreeBSD 5 support

Hi,

After posting this message, I realized that all of the events listed as 
having a problem, are those that utilze a sys_generic function. Taking a 
quick look into that function I noticed a problem that was causing 
filename lookups to (gracefully) fail. This has now been fixed.

This means that I will be posting a 2.0.1-pre1 version this week. I was 
hoping that after so many months of testing, the 2.0.0 version would be 
able to last a while before fixes would need to be made. Well, it has 
been 3 days since its release and I already have an important fix for 
FreeBSD. Oh well. :-)

John Ogness


John Ogness wrote:
> Hi,
> 
> I have merged the 2.0 branch into the head branch in CVS. This should 
> make it easier for people to check out the code (since they do not have 
> to worry about which branch they need to check out).
> 
> This weekend I sat down and implemented the FreeBSD 5 extension. It 
> wasn't too much work, mainly just changes in structures and function 
> names (and going through the FreeBSD 5 source code).
> 
> It appears to be working as well as the FreeBSD 4 extension. With 
> FreeBSD there are still some issues that I need to resolve (for both 4 
> and 5). Here is the list:
> 
> 1. exec/unlink/rmdir cannot resolve relative pathnames
> 2. exec cannot resolve full pathnames in a chroot environment
> 
> I need to look at why namei() fails in these situations.
> 
> I am not going to post an official pre-release with this new extension. 
> If you have FreeBSD 5, you can get the code from anonymous CVS with:
> 
> env CVS_RSH="ssh" cvs -z3 \
> -d:ext:[email protected]:/cvsroot/dazuko co dazuko
> 
> John Ogness

-- 
Dazuko Maintainer