0.684b is very close

Written by admin on .

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.

Comments (5)

  • Volker

    |

    A harddrive installation makes a plugin interface implementation easier, otherwise it will be more complex to update a harddrive installation.

    Reply

  • James

    |

    I agree. Depending on how things go, it might be nice to have a CF friendly writable installation as well (ie, isn’t constantly writing/rewriting things), so that plugins could be installed there as well, but the flash won’t get abused.

    Is anything of a plugin interface started? I might play with that a bit, if not. I’ve started trying to get jetdirect printing working (via p910nd). I’ve not yet had sucess, but I’ve got some ideas remaining.

    Reply

  • Bill

    |

    I don’t think we fixed the error.log bug either – I did notice it in pfSense a while back, but never really clued in that it was a bug *doh*. Thanks for reminding me :)

    Reply

  • Olivier

    |

    Bill…. The same Bill as the “project Leads & Visionaries” on the pfSense team !?

    Reply

  • Eddie

    |

    So, is the method for installing FreeNAS on an Xbox included in the current release, and if so how do you install it. I’m very interested in this possibility as I have an old Xbox and modchips are very cheap.
    Thanks.

    Reply

Leave a comment