https://www.truenas.com/blog/disable-openssh-portable/ Fri, 16 Feb 2024 17:53:23 +0000 hourly 1 https://wordpress.org/?v=6.4.4 https://www.truenas.com/blog/disable-openssh-portable/#comment-4792 Wed, 21 Mar 2007 19:31:00 +0000 http://www.freenas.org/whats-new/2007/03/disable-openssh-portable.html#comment-4792 Yes, I think that using the FreeBSD 6.2-RELEASE, and using only freebsd-update for updating it will simplify our bug hunting process.
I start the downloading of these ISO:
ftp://ftp2.fr.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2

]]> https://www.truenas.com/blog/disable-openssh-portable/#comment-4791 Wed, 21 Mar 2007 19:14:00 +0000 http://www.freenas.org/whats-new/2007/03/disable-openssh-portable.html#comment-4791 I 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.

]]> https://www.truenas.com/blog/disable-openssh-portable/#comment-4790 Wed, 21 Mar 2007 18:32:00 +0000 http://www.freenas.org/whats-new/2007/03/disable-openssh-portable.html#comment-4790 We should wait that this port works again before release the 0.684b.
And actually there are lot’s of activity on the FreeBSD 6.2 CVS.
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/#dirlist

]]>