Iâ€™ve found the problem with openssh-portable : It seem that openssh-portable havenâ€™t the same default value as the FreeBSD sshd implementation. It needs the line â€œPasswordAuthentication yesâ€ on the sshd_config file.
And Iâ€™ve added some messages about umouting drive that are used by swap file or iSCSI target and other little fix and prevent to format â€œused in a software raid driveâ€ disk.
Now the code seem ready for 0.684b 😉
User documentation is updated about the last features added: Only one choice for UFS (screen shot updates), and permit to use an USB key for storing configuration when using FreeNAS CDROM.
Iâ€™ve tried the just created FreeNAS-amd64 release CDROM, but my QEMU crash when I boot the CDROMâ€¦ there should be a bug somewhere on the make.sh with the amd64 release
Successful booting my software modified XBOX with the FreeBSD release (xbox-6stable-20060821.iso) .But Iâ€™ve just seen that the XBOX have only 64MB of RAMâ€¦ And FreenNAS need a minium of 96MB
For solving this 64MB problem I think that I should add a new install process for hard drive: It should no more use the method as flash device (using a RAM drive), but being installed directly on the hard drive (this will permit to simplify user modification of FreeNAS too). But this task is complex and will not be planned for the 0.684b. pfSense seem to use this method: I should check their code. This install method will permit to create a real SWAP partition too (permit to solve the â€˜not enough RAMâ€™ for fsck problem).
Iâ€™ve meet a problem since Iâ€™ve replace mini_httpd with lighttpd (there is a long time) : On the exec.php page the output of some commands (help option or error message) are no more display, but are send to the error.log of lighttpdâ€¦ Perhaps this problem is solved on the pfSense project.
Trackback from your site.