tag:blogger.com,1999:blog-1565531981620090589.post5800632296230643808..comments2007-03-21T20:31:55.644+01:00Olivierhttp://www.blogger.com/profile/08901361095735842069noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1565531981620090589.post-30322445788899367522007-03-21T20:31:00.000+01:002007-03-21T20:31:00.000+01:00Yes, I think that using the FreeBSD 6.2-RELEASE, and using only freebsd-update for updating it will simplify our bug hunting process.<BR/>I start the downloading of these ISO:<BR/>ftp://ftp2.fr.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2Olivierhttp://www.blogger.com/profile/08901361095735842069noreply@blogger.comtag:blogger.com,1999:blog-1565531981620090589.post-24851788167358708552007-03-21T20:14:00.000+01:002007-03-21T20:14:00.000+01:00I think we should think about how to generate the FreeNAS OS itself. In my opinion it is not good to use the latest CVS code for kernel + userland, instead we should use the latest stable release (e.g. FreeBSD6.2 + portsnap for the ports used in FreeNAS + freebsd-update. So we use a stable base OS for FreeNAS.Volkerhttp://www.blogger.com/profile/13879543395931531922noreply@blogger.comtag:blogger.com,1999:blog-1565531981620090589.post-70245382219756476442007-03-21T19:32:00.000+01:002007-03-21T19:32:00.000+01:00We should wait that this port works again before release the 0.684b.<BR/>And actually there are lot's of activity on the FreeBSD 6.2 CVS.<BR/>About FreeBSD CSV, is someone know how to read the actual CVS comments of the developers ? Because I don't found the up-to-date CVS (6.2) here: http://www.freebsd.org/cgi/cvsweb.cgi/#dirlistOlivierhttp://www.blogger.com/profile/08901361095735842069noreply@blogger.com